The information in this article applies to:
SYMPTOMS
CAUSE
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. RESOLUTIONA supported feature that modifies the product's default behavior is now available from Microsoft, but has not been fully regression tested and should be applied only to systems having a specific need for it. If you are not severely affected by the lack of this feature, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this feature.
http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of this feature should have the following file attributes or later: Component: ESE
This hotfix has been posted to the following Internet location as Psp2esei.exe: ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.5/PostSP2/ESE-fix/Psp2esei.zip STATUSMicrosoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. Additional query words: freeze frozen hanging ESE98 ESE97 100% spike
Keywords : exc55 |
Last Reviewed: November 30, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |