Article ID: 236426 - View products that this article applies to.
This article was previously published under Q236426
This article has been archived. It is offered "as is" and will no longer be updated.
ESE (Jet) hangs because all threads are waiting to acquire a resource that is owned by another thread. The decision used by threads as to which resources to acquire is based in part on a timestamp, and the timestamp comparison is being performed incorrectly. This incorrect comparison can cause the owning thread not to release the lock on the resource and leave all threads waiting.
The symptoms noted above are usually dependent on system uptime. Although this problem is not reproducible, documented cases encountered this problem on Exchange Server computers running for 30 days or more.
To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
191014The English version of this feature should have the following file attributes or later:
(https://support.microsoft.com/kb/191014/EN-US/ )XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
Collapse this tableExpand this table
This hotfix has been posted to the following Internet location as Psp2esei.exe:
Microsoft has confirmed that this is a problem in Microsoft Exchange Serverversion 5.5. This problem was first corrected in Microsoft Exchange Server version 5.5 Service Pack 3.
Article ID: 236426 - Last Review: 21 October 2013 - Revision: 4.2