This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario. A Microsoft Exchange Server 2007 mail server works as a proxy for a POP3 mail client. When the Exchange 2007 mail server tries to access a back-end Microsoft Exchange Server 2003 server, some clients cannot connect to the Exchange 2007 mail server. The POP3 service of the Exchange 2007 mail server may intermittently lose the response of the Exchange 2003 back-end server. Additionally, the Exchange 2007 mail server continues to try to respond to the Exchange 2003 back-end server until no more connection threads can be opened.
In this scenario, if a user tries to receive messages by using a POP3 mail client, the POP3 mail client may receive a 10061 error together with a 0x800CCC0E error code. Then, the Microsoft Exchange POP3 service must be restarted. Additionally, the following event is logged on the Exchange 2007 mail server:
Event Type: Warning Event Source: MSExchangePOP3 Event ID: 1009 Description: Number of simultaneous connections made by user <xxx> exceeded maximum (16).
This problem occurs if a deadlock occurs in the Microsoft.Exchange.POP3.exe process. In this situation, a client connection thread and a back-end proxy thread are pending for one another. Therefore, the existing connections are not disposed because the disposed threads are waiting for a resource that is held by the deadlocked threads. Eventually, the Exchange 2007 mail server reaches the connection limit.
Note The TCP/IP socket connections are closed. Only the connection objects and the counters are not disposed. Therefore, you cannot discover this problem by using the netstat command or by using the tcpview command.
To resolve this problem, install Update Rollup 3 for Exchange Server 2007. For more information about Update Rollup 3 for Exchange Server 2007, see the following Exchange Help topic: