Exchange Information Store

Try using eseutil(should have been installed with SP3) to check the integrity of the information store. If corrupt, run again using the fix switch. You must then delete the log files for the IS to run. This might not be the problem, but it's worth a shot.

You need to run isinteg -patch from the Exchange bin directory. This run an integrity check against the IS. Then try to start the IS. (Event relies on IS to start)

The Event log should give further information about why the Information Store is not starting. Typically, an error code of -1011 indicates a need to run isinteg -patch as the second answer indicated.

I do these restores more often than I would like and one of the other problems I run into is if the databases and log files are not in the same relative positions as they were on the server from which the backup was taken.

As the first answer correctly noted, there is a database repair tool called eseutil.exe.
But be very careful how you use it - Microsoft recommends that it only be used as a last resort and for good reason.

If you have the information from the Event log, I can probably supply further suggestions.

paul

answer 2 is correct. you must run the isinteg -patch in order to use the information store after a restore from backup. basically, it's a consistency adjuster that recreates all the associations. the is service won't start unless you do this.

Instead of using the eseutil go to the exchange admin highlight the server and go to the properties, select advanced and then click on the consistency adjuster from the gui.

This question was auto closed due to inactivity