locked
Windows Server 2008 R2 64-bit runs out of sockets daily (requiring reboot); the hotfix provided at KB 2577795 does not help. RRS feed

  • Question

  • Windows Server 2008 R2 64-bit runs out of sockets daily (requiring reboot); the hotfix provided at KB 2577795 does not help.

    Based on the msdn page at http://msdn.microsoft.com/en-us/library/windows/desktop/bb892100(v=vs.85).aspx, the tools logman.exe and tracerpt.exe allow one to capture socket events.  However, they yield event id codes as shown.  These event codes do not appear to be documented (based on my searches).  Are there alternate logging tools, and/or a list of definitions for these codes?  Event ids: 1000,1001,1002,1003,1004,1017,1018,1023,1024,1030,1032,1035,1036,3001,3003,3006

    These tools did help isolate non-critical processes with relatively higher event counts in this log.  However, even after stopping those, the problem recurs.

    Are there any other steps I can try?  Thank you.


    Wednesday, November 14, 2012 11:49 AM