Problem with Exchange Info Store

[justanothertech]

Hi there,

Just having some major problems with infor store on Exchange 5.5 sp 3. It wouldn't start and the error message is: The Microsoft Exchange Information Store service terminated with service-specific error 4294966786. Any thoughts?

Thanks a lot in advance.

 

[cmeagan656]

http://support.microsoft.com/default.aspx?scid=kb;en-us;327904#kb1

Cheers.

 

[justanothertech]

Thanks much it is definitely a good start. Here is more to those that will search on it in the future:

Stop all Exchange Services ( You may stop the Microsoft Exchange System Attendant. This will stop all the Exchange related services.)

To perform a hard recovery, follow these steps:

d:\eseutil /p “Location of Priv.edb”

d:\eseutil /p “Location of Pub.edb”

2. Delete all .log and .chk files in all the ExchSrvr\Mdbdata folder on the server. Additionally, if the Temp.edb file exists in the ExchSrvr\Mdbdata folder, delete it. ( Please remember to cut-paste these files to another location.) .



3. Defragment the database that you just repaired. To do so:



You must have available hard disk space equal to 110 percent of the size of the database that you want to defragment.

To defragment Priv.edb, type the following command at the command prompt, and then press ENTER:

d:\eseutil /d “Location of priv.edb”



To defragment Pub.edb, type the following command at the command prompt, and then press ENTER:

d:\eseutil /d “Location of Pub.edb”



(Note: If you receive an error message that indicates that there is not sufficient hard disk space to run the command, copy the ExchSrvr\Bin folder to a drive with more space, and then run the command from that location. For additional information about how to resolve this error message, click the following article number to view the article in the Microsoft Knowledge Base: 192185 XADM: How to Defragment with the Eseutil Utility (Eseutil.exe).

http://support.microsoft.com/default.aspx?scid=kb;EN-US;192185

)



4. Use the Isinteg.exe command-line tool to repair Pub.edb and Priv.edb. This utility runs a test on all areas of each of the databases and reports the results. It also tries to fix any issues that it encounters.

To fix Priv.edb, type the following command at a command prompt, and then press ENTER:



c:\exchsrvr\bin>isinteg -pri -fix -test alltests

To fix Pub.edb, type the following command at a command prompt, and then press ENTER:

c:\exchsrvr\bin>isinteg -pub -fix -test alltests

You will 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 tried, 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 two or three times until there are no warnings, errors, or fixes.



(Note : In some situations, the same warnings, errors, or fixes are reported every time you run the program. If you receive the same warnings, errors, or fixes three times in a row, go to the next step. The errors may be caused by a corrupted e-mail attachment or something similar. The repeat errors do not prevent you from starting the information store. If you can start the information store, if it is stable.)


5.Try to start the information store database. If the information store starts, go to step 6 now.

If the information store does not start and you receive an error -1011 then type the following command at the command prompt, and then press ENTER:

d:\exchsrvr\bin>isinteg -patch

( Note: The Microsoft Exchange Directory service must be running when you run this command. This command works for both the public and the private databases.)



6.Check your mail flow.



( eseutil /p : 4-5 G /hr

isinteg -fix : 5 mins /G

eseutil /d : 4-5 G /hr )

Good luck to all.