Get The Scoop On What's New
Want to know what Plugins4Automate is doing for ConnectWise Automate? Come check out our blog and find out about new products and updates that we are working on! https://www.plugins4labtech.com/blogs/blog

Error 1067

Supports the detector plugin and any feature or other requests around the plugin.
Post Reply
mathew.wright
Posts: 1
Joined: Thu Oct 10, 2019 3:41 pm

Error 1067

Post by mathew.wright » Fri Oct 11, 2019 5:28 pm

I have been trying to get this to work for weeks. Everytime I run Clear and Attempt LT Agent Service Using ScreenConnect, the following error occurs. I have tried this on over 10 stalled agents, all with the same error. Any help would be appreciated.

Starting Screen Connect connections to XXXXXXXXXX, Sending wakeup call
Lets give the wake up call a few seconds to do it's job
Agent Online time in second (if a negitive number then it is the number of seconds offline) -> 24527
Sending Windows commands to restart the LT Agent
Stopping LTService ->
C:\Windows\system32>net stop ltservice
The Summit I.T. Solutions Inc. Monitoring Service service is not started.

More help is available by typing NET HELPMSG 3521.


Killing LTSVC.exe ->
C:\Windows\system32>taskkill /im LTSVC.exe /f
ERROR: The process "LTSVC.exe" not found.

Starting LTService ->
C:\Windows\system32>net start ltservice
The XXXXXXX. Monitoring Service service is starting.
The XXXXXXX. Monitoring Service service could not be started.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.



All commands completed.

User avatar
Cubert
Posts: 1286
Joined: Tue Dec 29, 2015 7:57 pm
Contact:

Re: Error 1067

Post by Cubert » Tue Oct 15, 2019 3:16 pm

Looks like the plugin did its job, It contacted the agent vis Screenconnect and executed the restart LTagent process. That restart failed at the Windows OS level and not at the plugin or Automate level.

This is the failure point and is part of your problem...

Starting LTService ->
C:\Windows\system32>net start ltservice
The XXXXXXX. Monitoring Service service is starting.
The XXXXXXX. Monitoring Service service could not be started.


A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.



The errors in red are not created by Automate or our plugin. That is the agents own "Windows Service" service getting the command to restart, trying the restart and failing. This is the same as remote controlling the Windows OS, opening up the Services manager and restarting a service and it failing to restart.

No amount of plugin or Automate for that matter is gonna fix that. Its reboot time for the agent as Windows is failing service restarts.

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests