Error starting VNC service

[humbletech99]

I have a machine running VNC, a 2000 pro box I believe, and I am having trouble accessing it.

I have tried restarting the vnc service with a remote mmc to services, but I get the following error:

Could not start the VNC Server Version 4 service on MACHINENAME

Error 1053: The service did not respond to the start or control request in a timely fashion

and then

Unable to query status for service VNC Server Version 4. The remote connection on MACHINENAME has been broken.

The system encountered the following error while reading the list of services on MACHINENAME

Error 6: The handle is invalid.

Then all the services disappear.

I have also tried:

psexec \\machinename cmd
net start winvnc4

which gives the following error

The service is not responding to the control function.

Then I get

Error communicating with PsExec service on soupdragon2
The specified network name is no longer available

Any ideas how I can fix this and get my vnc back short of rebooting? (people are using this with long running processes so I am not in such an easy position to reboot)

 

[mpnut]

What VNC are you using? RealVNC, TightVNC? Also, I've seen something similar when a firewall was added to machine. And, have you updated your Java recently on your machine lately?

 

[humbletech99]

nothing should have been update on this machine.

it is realvnc. There is no firewall on this host, it is 2000 pro.

 

[mpnut]

I know you said "short of rebooting" but that would be my next suggestion. If the PC has not been rebooted in a while, stuff like this commonly happens.

 

[humbletech99]

ok guess I'm stuck on this.

 

[tookawhile]

I had the exact same problem, but had the luxury of being able to reboot, which fixed and it has never done it since.

The machine had no firewall running running or installed.

 

[aftertaf]

you can run inplace upgrades on VNC without rebooting.
Check ultra vnc and tight vnc websites.
they give good info on how to do this.


Aftertaf

Sometimes it just needs a good kicking.

 

[ATLMatt]

I use TightVNC, and can install it without restarting. You could always try stopping the current service and installing Tight and seeing if you can connect to it.