I have a SQL 2005 x64 Std Ed instance that allows TCP and Named Pipe connections. After restarting the server or the service, named pipes and TCP connections work. After an indeterminate amount of time, named pipes will stop accepting connections even though TCP connections still work perfectly fine. My only clue that named pipes is not accepting connections is that SQL jobs do not run. After I restart the SQL service, all returns to normal.
I've tried googling up some info but almost everything focuses on troubleshooting the complete lack of named pipes connectivity. I've only seen a couple of other [extremely short] threads describing the same issue without resolution.
For that reason, I won't ask if others have seen similar behavior behavior (it seems unlikely but if you can relate what fix worked for you that would be great!) but instead ask for ideas about how to isolate and troubleshoot.
1. Is it possible to exhaust named pipe connections?
2. Are there tools that show named pipe connections in the same way that tools for viewing TCP connections do?
3. There is nothing in the log file to help diagnose what is going on; is there something I can turn to start logging some info that could be of further assistance in troubleshooting?