My own console .net application stuck in a "ghost" stage. It just shows a window that i can't close. It doesn't show up as a process in the task manager.
when i try to "find windows process" using Process Explorer (from sysinternals) it says there is no process that owns that window or something like that.
The problem is that it doesn't allow me to logout or reboot the server (remotely) because logoff process keeps waiting on that window to close.
shutdown /r /f also is stuck waiting for it.
I can probably have somebody go an reboot the server but i'd like to know if there is a way to close that process, close that session or force logout remotely.
This is windows server 2003, but i had the same issue on XP just a few days ago.
Best Answer
The usual cuprit is that the WCF selfhost service is having problem with multi-session invocation. For you to verify if this is the case, login as administrator on the win2003 machine and run the task manager, then show all the process owned by *all users. See if some WCF selfhost process is still in memory run by other users.
If indeed WCF selfhost multi-session problem is really the problem, tell the WCF selfhost developer to host his WCF service into windows service so that single instance of WCF service will be kept running.