Windows utilities such as JIT debugger or Windows Error Reporting can keep a dying(dead) processes environment alive. |
The error in the netprobe log:
<Thu Sep 06 09:54:46> INFO: Current path: C:\Perl64\site\bin;C:\Perl64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;E:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\;E:\Program Files\Microsoft SQL Server\100\Tools\Binn\;E:\Program Files\Microsoft SQL Server\100\DTS\Binn\;E:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\;E:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\;C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\PrivateAssemblies\
<Thu Sep 06 09:54:46> INFO: CONMGR Details: tryListen(); nListenPort = 55514; 0; -856; port 55514 is currently in use;
<Thu Sep 06 09:54:46> INFO: CONMGR-WINDOWS WinErr: 0
<Thu Sep 06 09:54:46> FATAL: NETOBJECTS ConManager : non recoverable error, ing
Attempted to check which process has the port blocked
C:\Users\Administrator>netstat -ano | find "55514"
TCP 0.0.0.0:55514 0.0.0.0:0 LISTENING 1304
TCP 192.168.2.28:55514 192.168.2.24:13095 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:31143 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:31761 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:34942 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:39557 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:48130 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:48383 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:49111 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:49364 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:51336 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:56228 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:56481 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:57944 CLOSE_WAIT 1304
TCP 192.168.2.28:55514 192.168.2.24:58197 CLOSE_WAIT 1304
Okay, I will kill this because its my port and no one else's:
C:\Users\Administrator>taskkill /F /PID 1304ERROR: The process "1304" not found.
After logging onto this development server it was noted that vs jitdebugger had captured a netprobe process as it was being stopped. Acknowledging the jitdebugger prompt released the trapped processes environment and allowed the process to be restarted.
Comments
0 comments
Please sign in to leave a comment.