Article ID: 214684
Article Last Modified on 10/27/2006
APPLIES TO
- Microsoft Exchange Server 5.5 Standard Edition
This article was previously published under Q214684
SYMPTOMS
An improperly handled rollback operation by the Exchange Server DB Engine causes corruption in the database. This corruption may lead the Microsoft Exchange Server information store to terminate unexpectedly and display an access violation error message. If the correct Windows NT and Exchange Server debug symbols are installed, the resulting Dr. Watson log may display a stack dump similar to the following:
FramePtr RetAddr Param1 Param2 Param3 Function Name
3f9ceb48 6feaf887 3f9ceb58 133f48b0 00000000 ESE!ErrNDSeek+0xb({...})
3f9ceb6c 6feb0010 10816f40 fffffed4 3f9cebf4 ESE!BTISeekSeparatorKey+0x48
3f9ceb80 6feaf954 3f9cebf4 00000201 10816f40 ESE!ErrBTISelectSplit+0xba
3f9cebc4 6fea45a8 00000001 00000000 10816180 ESE!ErrBTISplit+0xbd
3f9cec84 6fea4fe9 3f9ced34 00000001 00000000 ESE!ErrBTInsert+0x3e8({...}, {...})
3f9ceca0 6feb653e 3f9ced34 00000001 00000000 ESE!ErrDIRInsert+0x27({...}, {...})
10816180 04560e80 1081de80 0fdabad0 1081de80 ESE!ErrRECSeparateLV+0x1c6
CAUSE
When the underlying Exchange Server database engine tries to roll back the creation of a long value (LV) tree on a table opened with exclusive access, the database is corrupted, and the rollback is only partially successful. This corruption will cause the information store process to terminate.
RESOLUTION
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:
191014 XGEN: How to Obtain the latest Exchange Server 5.5 Service Pack
Component: Exchange Database Engine
The English version of this fix should have the following file attributes or later:
| File name | Version |
|---|---|
| Ese.dll | 5.5.2522 |
This hotfix has been posted to the following Internet location as Psp2esei.exe (x86) and Psp2esea.exe (Alpha):
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5. This problem was first corrected in Exchange Server 5.5 Service Pack 3.
Keywords: kbbug kbfix kbqfe KB214684
