Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


stuhlpfarrer
2012-07-23T13:59:57Z
After updating to 6.1.2 the client on my computer hangs after connect. shows 0%.
client works only on server.
what could be done ?

Sponsor
Forum information
Support
2012-07-23T14:12:07Z
1. have you upgraded both client and server?
2. are you using local (ipc) or remote connection?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
stuhlpfarrer
2012-07-23T14:43:34Z
i upgraded both client and server to 6.1.2
local(ipc) works ok, but problem is with remote connection.

Originally Posted by: Support 

1. have you upgraded both client and server?
2. are you using local (ipc) or remote connection?


Support
2012-07-24T08:11:22Z
Try turning on or off the compression of the client connection.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
stuhlpfarrer
2012-07-24T10:13:47Z
tried this, but is the same problem.

Originally Posted by: Support 

Try turning on or off the compression of the client connection.


Support
2012-07-24T11:32:03Z
If you wait, what error do you get?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
stuhlpfarrer
2012-07-24T12:39:30Z
found this in vc server log:

Could not start socket server, please shut down all processes previously started by VisualCron, error details: Only one usage of each socket address (protocol/network address/port) is normally permitted

with tcpview i found out that a process with pid 2680 uses vc port 16444, but this pid is a non-existant process, like a zombie in unix.
<non-existent>:2680 TCP 0.0.0.0:16444 0.0.0.0:0 LISTENING
Support
2012-07-24T13:29:20Z
Yes, kill any child processes that may have been launched by VisualCron and still running. Then start the service again.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
stuhlpfarrer
2012-07-24T14:22:48Z
Thanks for this suggestion, this has worked.
No we can remote connect to VC again.

Originally Posted by: Support 

Yes, kill any child processes that may have been launched by VisualCron and still running. Then start the service again.


Scroll to Top