Microsoft KB Archive/822449

= Error c1041724 Occurs When You Try to Mount a Database on an Exchange 2003 Server =

Article ID: 822449

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition

-





SYMPTOMS
When you try to mount a database on an Exchange 2003 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



CAUSE
This problem may occur if the following conditions are true:  The eseutil /p command has been run on the database that you are trying to mount.

-and-

 The Eseutil log files have not been removed.



RESOLUTION
To resolve this problem, follow these steps:  Determine if the eseutil /p command was run on the database. To do so:  Click Start, and then click Run. In the Open box, type cmd, and then click OK.</li> Locate the C:\Program files\ExchSrvr\Bin folder, and then type the following commands.

Note These commands assume that you are running Exchange 2003 from drive C in the Program Files\ExchSrvr\Bin folder and that the .edb files are in the Program Files\ExchSrvr\Mdbdata folder.

eseutil /mh &quot;C:\program files\exchsrvr\mdbdata\pub1.edb&quot;

-and-

eseutil /mh &quot;C:\program files\exchsrvr\mdbdata\priv1.edb&quot;

</li> View the output.

If the repair count attribute in the output is 0 (zero), the eseutil /p command was not run on the database. If the repair count attribute in the output is a number other than 0 (zero), the eseutil /p command was run on the database.</li></ol> </li> Check the consistency (state) of the information store databases to determine if you have to remove the Eseutil log files. To do so, view the output from the command you ran in step 1.  The database is consistent if the output lists the database state as Clean Shutdown. All the log files have been committed to the information store.</li> The database is not consistent if the output lists the database state as Dirty Shutdown. This state may occur as a result of corruption or it may occur if the log files have not been committed to the information store yet. To determine if this state occurs because the log files have not been committed to the information store, wait a few minutes, and then run the command again.</li></ul> </li> If the database state is listed as Clean Shutdown, remove all the log files from the Mdbdata folder. Put these files in a backup folder.</li> Mount the information store. To do so: <ol style="list-style-type: lower-alpha;"> Start Exchange System Manager. To do so, click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.</li> Double-click  , right-click Mailbox Store, and then click Mount Store.</li></ol> </li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

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

170091 XADM: Location of the Eseutil Utility

317014 XADM: Exchange 2000 Server Eseutil Command Line Switches

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

Additional query words: c1041724, eseutil, command

Keywords: kberrmsg kbprb KB822449

-

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

© Microsoft Corporation. All rights reserved.