XADM: Random Access Violation in Store.exe (JetMove) (268446)
The information in this article applies to:
- Microsoft Exchange Server 5.5
This article was previously published under Q268446 SYMPTOMS
Exchange Server may randomly stop responding (crash) in Store.exe. This crash generates a Drwtsn32.log file entry that is similar to the following:
Application exception occurred:
App: exe\store.dbg (pid=301)
When: 6/26/2000 @ 1:0:52.767
Exception number: c0000005 (access violation)
WORKAROUND
To work around this issue, run the eseutil /g /{db} /V /X >dbchk.txt command. After Eseutil with the /g switch finishes, search for orphaned long values in the corresponding text files. If there are only orphaned long values, run the eseutil /d command. NOTE: For additional information about how to verify that your Exchange Server databases exhibit orphaned or corrupted long values, click the article numbers below
to view the articles in the Microsoft Knowledge Base:
185271 XADM: Orphaned LV Errors Running ESEUTIL Consistency Checker
181824 XADM: Exchange Database Engine Doesn't Detect Removed Page in B-tree Split Operation
195856 XADM: How to Detect and Remove Long Values in Exchange Server Database
| Modification Type: | Minor | Last Reviewed: | 4/21/2005 |
|---|
| Keywords: | kbprb KB268446 |
|---|
|