Article ID: 308097 - Last Review: February 23, 2007 - Revision: 4.4

State server logs Event ID 1072 or Event ID 1076

View products that this article applies to.

This article was previously published under Q308097

SYMPTOMS

If you use the state server mode of Session state in ASP.NET, when either the Web server or the computer that is running state server is under high stress, one of the following events may be logged in the Application Event log on the state server computer:

Event Type: Error
Event Source: ASP.NET 1.0.3306.0
Event Category: None
Event ID: 1072
Date: 9/12/2001
Time: 4:00:25 PM
User: N/A
Computer: ComputerName
Description:
An error occurred in while processing a request in state server. Major callstack: EndOfRequest. Error code: 0x80072746

Note The version of the Microsoft .NET Framework that is mentioned in the previous event message is a pre-release version of the .NET Framework 1.0.

Event Type: Error
Event Source: ASP.NET 1.0.3306.0
Event Category: None
Event ID: 1076
Date: 9/12/2001
Time: 4:02:05 PM
User: N/A
Computer: ComputerName
Description:
The state server has closed an expired TCP/IP connection. The IP address of the client is 127.0.0.1. The expired Read operation began at 09/12/2001 16:02:00.

Note The version of the .NET Framework that is mentioned in the previous event message is a pre-release version of the .NET Framework 1.0.

Event Type: Error
Event Source: ASP.NET 1.1.4322.0
Event Category: None
Event ID: 1078
Date: 10/6/2005
Time: 11:03:47 AM
User: N/A
Computer: ComputerName
The state server has closed an expired TCP/IP connection. The IP address of the client is 127.0.0.1. The expired Read operation began at 10/06/2005 11:03:25.

Back to the top

CAUSE

When you use the state server mode of Session state in ASP.NET, the ASP.NET Web server process in the Web server communicates with the state server by using WinSocket over Transmission Control Protocol/Internet Protocol (TCP/IP). By default, the Web server process sets the time-out value of all send and receive TCP/IP operations to 10 seconds. Similarly, the state server also times out all send and receive TCP/IP operations after 10 seconds.

However, if either the Web server or the state server is under very high CPU utilization (close to 100 percent), a TCP/IP operation can sometimes take more than 10 seconds and thus is cancelled before it has the chance to finish. As a result, one of the above-mentioned events is logged, and the originating client request fails. The state server logs event ID 1072 if the ASP.NET Web server process times out a TCP/IP operation. If the state server times out a TCP/IP operation, the state server logs event ID 1076.

Back to the top

RESOLUTION

To modify the TCP/IP operation time-out value for the ASP.NET Web server process, change the following attribute in the Machine.config file (or specify the following attribute in the Web.config file for any Web application).

        <sessionState 
            stateNetworkTimeout="10"
        />

To modify the TCP/IP operation time-out value for the state server, follow these steps:

Stop the ASP.NET state server service.
Click Start, click Run, type Regedt32.exe, and then click OK to start Registry Editor.
Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aspnet_state\Parameters
Add a DWORD value that is named SocketTimeout. Set a positive integer to represent the new TCP/IP timeout in seconds.
Quit Registry Editor.
Restart the ASP.NET state server service

Users who experience the problems that are mentioned in the "Symptoms" section should use these methods to increase the time-out values on the state server and on all Web servers to 20 seconds.

Note If the state server is not running when you increase the time-out values on the Web server, a client request times out after n seconds, where n equals a new timeout value, instead of the default 10 seconds.

Back to the top