> For some reasons I restarted my Win2K web server (IIS) yesterday, and the
VNC Server (3.3.3r2) no longer worked. It said "Another instance of WinVNC
is already running" after the first login since a Win2K restart. But WinVNC
was *not* running.
How do you know WinVNC was not running?
> Uninstalling and reinstalling VNC (3.3.3r9) didn't help.
>
> Deleting most registries (except LEGACY_WINVNC folders which mysteriously
could not be deleted) and restarting didn't help.
>
> Command-line commands "-remove", "-kill", etc. didn't help.
Ick. You should have used "winvnc -remove" and then used the InstallShield
uninstaller. Deleting registry entries manually is a bad idea.
> And it happened for *both* my web server and my SQL server (also Win2K) at
the same time! How come?!
This sounds as if you have done something like running VNC via a Run
registry setting in your user profile, as well as running it as a service,
or as if someone has changed the servicehelper startup items in the registry
to start winvnc in app mode.
Cheers,
James "Wez" Weatherall
--
"The path to enlightenment is /usr/bin/enlightenment"
Laboratory for Communications Engineering, Cambridge - Tel : 766513
AT&T Labs Cambridge, UK - Tel : 343000
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
