Microsoft KB Archive/284205

= XADM: Error c1041724 When You Try to Mount Exchange 2000 Server Databases =

PSS ID Number: 284205

Article Last Modified on 11/24/2003

-

The information in this article applies to:


 * Microsoft Exchange 2000 Server

-



This article was previously published under Q284205



SYMPTOMS
When you try to mount a database on a server that is running Exchange 2000 Server, you may receive the following error message:

An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both.

ID no: c1041724

Exchange System Manager

Additionally, the application log descriptions point to a missing log file.



CAUSE
This error can occur if the eseutil /p command-line command is run on the databases in question and if the log files are not removed. To determine if the eseutil /p command-line command was run, follow these steps:  Run the following command-line command on the database in question:

c:\program files\exchsrvr\bin\eseutil /mh

 Read the repair count attribute.  If the repair count attribute is 0 (zero), the eseutil /p command-line command was not run. If the repair count attribute is a number other than 0, the eseutil /p command-line command was run on the database. 



RESOLUTION
To resolve this problem, follow these steps:  Run the following command-line commands to check the consistency (state) of the public and the private databases:

c:\program files\exchsrvr\bin>eseutil /mh &quot;drive:\program files\exchsrvr\mdbdata\priv1.edb&quot;

-and-

c:\program files\exchsrvr\bin>eseutil /mh &quot;drive:\program files\exchsrvr\mdbdata\pub1.edb&quot;

NOTE: This example assumes that you are running the programs from drive C in the \Program Files\ExchSrvr\Bin folder, and that the .edb files are in the \Program Files\ExchSrvr\Mdbdata folder.</li> Review the results of the consistency check.  If a database is consistent (state = clean shutdown), all of the log files have been committed to the information store.</li> If the database is not consistent (state = dirty shutdown), the database may not be corrupted; the log files may not have been committed to the database yet.</li></ul> </li> If the state reports clean shutdown, remove all of the log files from all of the mdbdata directories to a backup directory.</li> Mount the databases.</li></ol>

<div class="moreinformation_section">

MORE INFORMATION
For additional information about disaster recovery and related issues and utilities, click the article numbers below to view the articles in the Microsoft Knowledge Base:

192185 XADM: How to Defragment with the Eseutil Utility (Eseutil.exe)

170091 XADM: Location of the Eseutil Utility

244525 XADM: How to Run Eseutil on a Computer Without Exchange Server

317014 XADM: Exchange 2000 Server Eseutil Command Line Switches

254132 XADM: Eseutil /d Defragments the Database and the Streaming File

255224 XADM: Usage Error: Invalid Argument When Running Eseutil with Spaces in PATH

297336 XADM: How to Use the Eseutil Utility to Checksum a Streaming File

256352 XADM: Online Defragmentation Does Not Reduce Size of .edb Files

261947 XADM: How to Determine if Hard Repair (Eseutil /p) Has Been Run on a Database

Additional query words: c1041724 Eseutil exch2kp2w switch

Keywords: kberrmsg kbprb KB284205

Technology: kbExchange2000Search kbExchange2000Serv kbExchange2000ServSearch kbExchangeSearch

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.