Stop Msg: 0x0000003F NO_MORE_SYSTEM_PTEs SNA & TCP/IP Sockets (137309)

RESOLUTION

WARNING: Using the Registry Editor incorrectly can cause serious, system- wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of the Registry Editor can be solved. Use this tool at your own risk.

Microsoft has modified the files, SNADMOD.DLL and SNAIP.DLL, so that SNA Server does not queue a new KeepAlive until the previous one has completed. Thus, the connection is aborted after a configurable timeout. The timeout is specified in the following registry parameter:

   HKEY_LOCAL_MACHINE
     \System
       \CurrentControlSet
         \Services
           \Snabase
             \Parameters
               \SnaTcp
                 KeepAliveLimit: REG_DWORD: 0 - 0xFFFFFFFF
				

The KeepAliveLimit specifies how many WatchDogTimeouts SNA Server waits before aborting the connection. The default watchdogtimeout value is 60 seconds, though this is also configurable under:

   Hkey_local_machine
     \System
       \CurrentControlSet
         \Services
           \SnaBase
             \Parameters
               \watchdogtimeout REG_DWORD: <value>
				

If a second keepalive is sent to a client box, SNA Server now logs Event 700 to indicate this (logged only when detailed problem analysis logging is enabled). If the limit is exhausted, then SNA Server logs a 701 event at a high severity to indicate this. The client's IP address is logged in these new events.

The registry value, HardClse, controls how the connection is aborted. If the value is "yes", the connection is reset immediately and no effort is made to close the connection gracefully. The default value is "no". HardClse is found in the following subtree:

   Hkey_local_machine
     \System\CurrentControlSet
       \Services
         \SnaBase
           \Parameters
             \TcpIp
               \HardClse
				

REG_SZ: ("no" -or- "yes")