XADM: Exchange Information Store Access Violation Occurs Because Column ID Is Not Valid

Article translations Article translations
Article ID: 317538 - View products that this article applies to.
This article was previously published under Q317538
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

The information store process may experience an access violation (crash) when it passes an column ID that is not valid to the Extensible Storage Engine (ESE).

If you have installed the proper symbols on the system, the Dr. Watson log or a review of the corresponding User.dmp file produces a call stack similar to the following:
01 520cf354 002cb605 ESE!_ExceptionFail+0x31
02 520cf878 0064b179 ESE!JetSetColumn+0x7c 
03 520cf8bc 00532a7b store!JTAB_BASE__EcSetColumn+0x1a6 
04 520cf950 00536907 store!OMSG__EcFlushProps+0x52d 
05 520cf990 0055069a store!OMSG__EcDoImailProcessing+0xa1 
06 520cf9c0 30af7301 store!EcSetFileHandlePropOp+0x11d 
07 520cfa50 30af706c EXSMTP!CMdbLogon__HrSetMessageContent+0x153
08 520cfc8c 30af4338 EXSMTP!COmsgWrapper__HrSetContent+0xff
09 520cfef4 30af253c EXSMTP!misfnDoLocalDelivery+0x282
0a 520cff10 30af2c29 EXSMTP!Dispatch+0x132
0b 520cff30 30af2b8f EXSMTP!CMdb__DefaultMdbQueueThreadRoutine+0xb1
0c 520cff58 0055eb9e EXSMTP!CMdb__MdbQueueThreadRoutine+0x1ae
0d 520cff6c 61bd1247 store!TI__Invoke+0x83
0e 520cffb4 77e8758a mdbtask!MdbTaskPoolThread+0x22
0f 520cffec 00000000 KERNEL32!SetFilePointer+0x18a
					

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: ESE

Collapse this tableExpand this table
File nameVersion
Ese.dll6.0.5770.46
Eseperf.dll6.0.5770.46
Eseperf.hxx6.0.5770.46
Eseperf.ini6.0.5770.46

STATUS

Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.

Properties

Article ID: 317538 - Last Review: October 24, 2013 - Revision: 1.3
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB317538

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com