Article ID

:

313184

Last Review

:

February 16, 2007

Revision

:

13.2

•

Priv1.edb

•

Priv1.stm

•

Pub1.edb

•

Pub1.stm

•

The Microsoft Exchange Information Store service does not start.

•

You cannot stop the Information Store service, and you also cannot stop dependent services such as Post Office Protocol version 3 (POP3) and Internet Message Access Protocol, Version 4rev1 (IMAP4).

•

The information store stops responding, and the CPU usage level remains at 100 percent.

•

Clients cannot retrieve or send e-mail, even if you stop and then restart the Information Store service.

•

When you try to restore the Exchange 2000 Server and Exchange Server 2003 databases from an offline backup, and then run the Information Store Integrity Checker utility (Isinteg.exe) patch, you may receive the following error message:

Error 4294966746: JET_errDatabaseInconsistent

•

When you try to mount the mailbox store in Exchange System Manager, you receive an error message that is similar to the following:

Unable to Mount the Mailbox Store with error c104173c "The Information Store is Busy"

•

A site connector is not being used.

•

Site replication is disabled (a single site is in use).

•

An offline copy of both the Pub1.edb file and the Priv1.edb file exists.

•

A Key Management server (KM server) is not being used.

•

The server is running Microsoft Small Business Server 2000.

1.

Try to start the Microsoft Exchange Information Store service. Record any error and event IDs that are reported.

2.

Make sure that the Information Store service is stopped before you run the Eseutil.exe program that is mentioned in step 3.

Note If the Information Store service stops responding (hangs) in a starting state, you can stop the service by disabling it and restarting the server. To disable the Information Store service, follow these steps:

3.

Check the consistency of the databases. If a database is consistent, all the log files have been committed to the store. If the database is not consistent, the database may not be corrupted. Instead, the log files may be missing, damaged, or not yet committed to the database. Run the following commands to check the consistency of the public and private databases (these lines have been wrapped for readability).

C:\Program Files\exchsrvr\BIN>eseutil /mh
"drive:\Program Files\exchsrvr\MDBDATA\priv1.edb"

C:\Program Files\exchsrvr\BIN>eseutil /mh
"drive:\Program Files\exchsrvr\MDBDATA\pub1.edb"

Note This example assumes that you are running the programs in the Program Files\ExchSrvr\Bin folder on drive C, and that the .edb files are in the Program Files\ExchSrvr\Mdbdata folder.

If you have performed an upgrade, the database files may be located in the C:\Exchsrvr\Mdbdata folder. If the databases have been optimized, they may be located on another drive.

To verify that the .edb file is consistent, check the output line that is labeled "State." If you want to send the output of this command directly to a text file, you can modify the command line as follows (the following lines have been wrapped for readability).

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\priv1.edb > mypriv.txt

C:\Program Files\exchsrvr\BIN>eseutil /mh
C:\Program Files\exchsrvr\MDBDATA\pub1.edb > mypub.txt

To display the text directly on the screen, add | more to the end of the command.

If the Pub1.edb file and the Priv1.edb file are not located in the Program Files\ExchSrvr\Mdbdata folder on the same drive as the ExchSrvr\Bin folder that you are running the command from, replace the "C:\program files\mdbdata\priv1.edb" portion of the command with the full path of the Priv1.edb file. Make the same changes for Pub1.edb. If both the Pub1.edb file and the Priv1.edb file are consistent, go to step 6.

If one of the databases is inconsistent, try to perform a soft recovery of the files to see if there are copies of the log files stored in the Mdbdata folder.

Note If you do not have the log files, you cannot complete the soft recovery process. Go to step 6. You must also start the Information Store service.

When you perform a soft recovery, any uncommitted log files are committed to the information store database.

To initiate a soft recovery, run the following command.

Open the folder where the database and log files reside, and then type the following at a command prompt. The following line has been wrapped for readability.

C:\Program Files\exchsrvr\MDBDATA>"C:\Program Files\exchsrvr\BIN\eseutil" /r E00

Click Yes to run the repair. The utility displays the following message:

Microsoft (R) Exchange Server(TM) Database Utilities Version 6.0 Copyright (C) Microsoft Corporation 1991-2000. All rights reserved. Initiating RECOVERY mode... Logfile base name: E00 Log Files: (current directory) System files: (current directory) Performing soft recovery...

When the soft recovery is complete, the program displays the message:

Operation completed successfully in x.xxx seconds.

You can use this command to recover the databases if the databases are fully recoverable. To confirm this behavior, repeat this step from the beginning, and then run the eseutil /mh command again. If the state has changed to "Consistent" for both the public information store and the private information store, go to step 5.

4.

If either of the databases is inconsistent, and the eseutil /r command does not return them to a consistent state, use the procedure that is described in this step.

Note When you use the following command, you may lose some Exchange 2000 Server or Exchange Server 2003 data, including the messages that were contained in the log files that were not yet committed to the information store database. The following command is a hard or forcible state recovery command. Microsoft recommends that you use this command only if the public information store or the private information store does not return to a consistent state after you perform the steps described earlier in this article.

At the command prompt, type the following commands (the following lines have been wrapped for readability):

When the procedure is complete, the program displays the message:

Integrity check successful.

Note The .stm files are automatically included in the repair process.

5.

Delete all .log files in the Mdbdata folder, delete the .chk file, and then delete the Temp.edb file (if it exists).

6.

Mount the databases one time, and then immediately dismount them to so that users cannot access them during this procedure.

Note You may stop the SMTP service before you mount the databases to prevent new e-mail messages from coming in to the databases. When you run a Hard Repair (eseutil /p), and the repair actually detects and removes database corruption, you should run an offline defragmentation after the repair and before you do anything else.

7.

Stop the Information Store service and run a defragmentation of the private and public store databases. You must run this step if you are low on disk space.

Note You must have free disk space equal to at least 110% of the database size to run eseutil /d. If you do not designate a temporary location for the database file by using the "t" command, the temporary location is automatically set to the Exchsrvr/Bin folder.

At a command prompt, type the following commands (the following lines have been wrapped for readability):

Note If both the private and the public information store databases are large, this step may take some time. If you receive an error message that indicates a lack of disk space when you try to perform this step, copy the Program Files\ExchSrvr\Bin folder to a drive that has more disk space, and then try to run the command from that location. For more information about how to resolve this error message, click the following article number to view the article in the Microsoft Knowledge Base:

192185 (http://support.microsoft.com/kb/192185/) How to defragment with the Eseutil utility (Eseutil.exe

8.

Use Isinteg.exe to fix the Pub1.edb database and the Priv1.edb database. The Isinteg.exe utility runs a test on all areas of each of the databases and reports the results. Isinteg.exe also tries to fix any issues that are encountered.

Note To obtain or confirm the server name, type the following command at a command prompt on the server:

nbtstat -n

You are prompted to select the database to be checked.

Index Status Database-Name Storage Group Name: First Storage Group 1 Offline Mailbox Store (servername) 2 Offline Public Folder Store (servername) Enter a number to select a database or press Return to exit.

You can only check databases that are marked as offline. The Information Store service must be started, but the information store must be dismounted.

When you select a database, you are prompted with the following message to confirm the selection:

"You have selected First Storage Group / Mailbox Store <servername> Continue? (Y/N)" Press <B>Y</B> and <B>Enter</B> to start checking the selected database.

You receive a summary report that indicates the number of tests that were run, the number of warnings, the number of errors found, the number of fixes attempted, and the time it took for the program to run. If there are any warnings, errors, or fixes, run the command again. Repeat this step until there are no warnings, errors, or fixes reported and the report looks similar to the following text:

Test reference table construction result: 0 error(s); 0 warning(s); 0 fix(es); 0 row(s); time: 0h:0m:0s Test Folder Result: 0 error(s); 0 warning(s); 0 fix(es); 101 row(s); time: 0h:0m:0s Now in test 3 (reference count verification)of total 3 tests; 100% complete.

Note In some cases the same warnings, errors, or fixes may be reported every time you run the program. If you receive the same warnings, errors, or fixes three times in a row, move to the next step. The errors may be caused by a corrupted e-mail attachment or something similar that does not prevent you from starting the information store.

If you can start the Information Store service, and the information store is stable, and the same errors and warnings are reported after you have run Isinteg.exe several times, use the ExMerge utility to rebuild the information store by exporting the data into .pst format, and then re-importing it into new or clean database structures. The information about how to use the ExMerge utility is included later in this article.

Note Exchange 2000 Server and Exchange Server 2003 no longer implement the Isinteg utility in conjunction with the -patch option. A patch is performed automatically by Store.exe when the information store starts. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

251409 (http://support.microsoft.com/kb/251409/) Isinteg -patch is no longer required to restore offline backups

9.

Restart the information store.

1.

Make sure that there are no users who are currently accessing e-mail or have their e-mail client programs running.

2.

Run ExMerge by using step one of the two-step merge, and then enter all the users.

3.

When the ExMerge process is complete, stop the Exchange 2000 Server or Exchange Server 2003 Information Store service, locate and open the ExchSrvr\Mdbdata folder, and then rename the Pub1.edb and Priv1.edb files.

Delete all the other files in this folder. Make sure that you do not delete the renamed Pub1.edb and Priv1.edb files until you are sure that the merge was successful.

4.

Restart the Exchange 2000 Server or Exchange Server 2003 Information Store service.

5.

Start Outlook on a client computer, and then send an e-mail message to all the users in the Exchange 2000 Server or Exchange Server 2003 global address book.

Note If you do not complete this step, the second step of the ExMerge two-step merge does not show that there are any available mailboxes to restore.

6.

Run ExMerge using step two of the two-step merge, and then enter all the users.

When this process is complete, the e-mail messages that were in the .pst files are moved to Exchange 2000 Server or Exchange Server 2003 mailboxes.

1.

From a client such as Outlook, copy the public folders to the user's personal folders on the client.

2.

Stop the Information Store service, and then rename the existing Pub1.edb and Pub1.stm files.

3.

To create the new Pub1.edb, mount the public folders database.

4.

Click OK to create the new Pub1.edb.

Note You must reinstate any permissions on the public store. For more information if the new database is not created automatically, click the following article number to view the article in the Microsoft Knowledge Base:

261329 (http://support.microsoft.com/kb/261329/) Information store files are not created automatically at information store startup

5.

From the client, move the folders back into the new public folder structure on the server.

1.

In Exchange System Manager, right-click Mailbox Store.

2.

Click the Database tab.

3.

Click the Customize button.

4.

Repeat steps 1 through 3 for Public Folder Store.

•

Microsoft Exchange Server 2003 Enterprise Edition

•

Microsoft Exchange Server 2003 Standard Edition

•

Microsoft Exchange 2000 Server Standard Edition

•

Microsoft Small Business Server 2000 Standard Edition