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)

[ɹəuəllıʍ ʇɐb]

While reading the messages I thought I was going to suggest to reboot. However, you won't/can't do that, so I'm out of ideas.

Is this happening repeatedly? If so, I would suggest that you upgrade the the latest version of VNC; it may be a bug that has been fixed?

[humbletech99]

I believe it has the latest version of vnc. I think the service thing is just messed up. I may have to reboot after all.