myron_in_da_house "at" yahoo.co.uk
Sun Sep 5 20:17:01 2004
There are far and in-between and unfortunately I have not kept a record of the error messages, but it may be worth searching the VNC server code for buffer overruns conditions or out-of-bound array pointers. This is with the release version of VNC 4.
The issue is that while running as a service a dialogue box appears (this is on Windows XP Pro SP-2) stating that there has been a memory access violation and a user response is requested.
Only problem here is until the response is given, the service is seen as active and XP's service manager will not re-start the VNC server after a fail.
Luckily in this case I could go in by remote using a Terminal Services session and use the Process Explorer from SysInternals to force the VNC server down (as the service manager could not stop the service) and then re-start it.
Next time it happens I'll try make a note of the exact error.
This happened during unlocking the console. I got the VNC viewer to do it's CTRL-ALT-DEL think and then when the password was keyed in, then `OK` was clicked, the VNC server terminated.
When I reconnected to the console, after re-starting the service, the desktop had appeared, the console remained unlocked and the memory violation dialogue was showing.
Just reporting the problem. Anyone got an idea for a cure?