XADM: Information Store Crashes Due to Database Corruption Occurring after a Faulty Rollback Operation on a Transaction

ID: Q214684

The information in this article applies to:

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

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Microsoft Exchange Server version 5.5 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

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):
ftp://ftp.microsoft.com/bussys/exchange/exchange-public/fixes/Eng/Exchg5.5/PostSP2/ESE-fix/


NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5.


Keywords          : 
Version           : winnt:5.5
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 3, 1999