0
Waiting for information

Remote command locks machine until times out

Poynter 1 year ago updated by Eric Davis (SDT) 12 months ago 3

When sending a remote command, it completely locks up (the command does seem to run) until it times out and is killed. 

ConnectWise Control Version:
10
Server Affected:
Host Client Affected:
Guest Client Affected:
Waiting for information

Could you clarify what you mean by locking up? Does the web UI become unresponsive?


Also, does this happen for any command? If the specific command is just slow, you can increase the timeout. (See the "Advanced command options" in this document: https://docs.connectwise.com/ConnectWise_Control_Documentation/Get_started/Host_page/Run_a_command_from_the_Host_page)

Please see example below. Happens randomly. 



Engineer

01-24 13:40:57

slmgr.vbs /ato


User

01-24 13:44:22

The process cannot access the file 'C:\windows\TEMP\ScreenConnect\6.9.21027.6898\e06cbbd8-21b9-4fbe-9515-4c04acf943d1run.cmd' because it is being used by another process.

Do you have some kind of antivirus software on the machine? That's what immediately comes to mind when I think of what might grab newly-created temp files.

It might be best to contact support so a tech can take a look at it.