ASP. NET state service error Solution

Two Web servers, Windows 6.0 and IIS 2.0, are installed with. net. They run the same program and load balancing each other.

If an error is displayed when you enter a system function page, the following error occurs:

[Httpexception: unable to send a session Status request to the session Status server. Make sure that ASP. Net state service has been started and the client and server ports are the same. If the server is on a remote computer, check the value of HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ aspnet_state \ Parameters \ allowremoteconnection to ensure that the server accepts remote requests.]

This application uses the aspstate service for session management and is configured in Web. config.
<Sessionstate
Mode = "StateServer"
Stateconnectionstring = "TCPIP = 127.0.0.1: 42424"
Cookieless = "false"
Timeout = "3600"
/>

Generally, it is considered that the aspstate service is not enabled, but other pages are working normally. Check that the service is started. Restarting IIS, aspstate, and server cannot be solved. Check System logs with the following error information:
Event Type: Error
Event Source: ASP. NET 2.0.50727.0
Event Type: None
Event ID: 1074
Date:
Event: 18:36:41
User: N/
COMPUTER: xxxx
Description:
An error occurred in while processing a request in State server. Major callstack: processcompletion --> processreading --> Tracker: Read. Error code: 0x80072747

It seems that the aspstate service is successfully connected, but the service has an error. The search error code is 0x80072747. The prompt is:
Wsaenobufs (0x80072747)
No buffer space available.
An operation on a socket cocould not be performed med because the system lacked sufficient buffer space or because a queue was full.

It seems that the memory management problem is that Google's information is very limited. There are 4-5 identical questions, but there is no answer. There is no clue at all. After thinking for a long time, after a long time, I suddenly thought that the/3 GB switch was enabled in Boot. ini:
Multi (0) disk (0) RDISK (0) Partition (1) \ Windows = "Windows Server 2003, enterprise"/fastdetect/3 GB

Remove/3 GB switch, restart, and restore ~~! It is suspected that the aspstate has a bug in memory management.