Probleme mit Exchange-Informationsspeicher

Wenn s noch nicht läuft mal das probieren.

Solltest Du einen Backup haben spiele diesen zurück.

Hast Du irgendetwas an diesem System gemacht. AD Gruppen? Security einstellungen...?

>

RESOLUTION
To resolve this problem, perform a restore from the last good backup. If a good backup is not available, you must delete and then re-create the .stm file. To do this, follow these steps:
1. Try to restart the Microsoft Exchange Information Store service.
2. View the Application log to see if event ID 9175 is logged.
3.
• If event ID 9175 is logged and if a backup is available, restore from the backup.
• If event ID 9175 is logged and if a backup is not available, copy the content of the Drive:\Program Files\Exchsrvr\MDBDATA directory to a safe location.
4. Verify the consistency of the databases. Include all the private files and all the public files.
5. Run the eseutil /r command to try to return the databases to a consistent state.
6. If the eseutil /r command fails, run the eseutil /p command.

If you receive a "-1206" error, delete the .stm file for the database.
7. Re-create the .stm file. To do this, run the following command:
eseutil /p %programfiles%\exchsrvr\mdbdata\priv1.edb /createstm
Note The path in this command is the default path of the database file. If the database is not in the default path, change the path in the command to the correct path.
8. Mount the databases. Do not start the Microsoft Exchange MTA Stacks service or the Simple Mail Transfer Protocol service.

You do not want to start these services because you have to merge the data to a .pst file. Therefore, you do not want incoming e-mail messages to be delivered to the mailboxes yet.
9. Use the Exmerge.exe tool to merge the data to a .pst file. Then, create a blank database.
10. Restart the Microsoft Exchange System Attendant service and the Microsoft Exchange Information Store service. Then, mount the databases.
11. Run the Exmerge.exe tool again, and then import the .pst files to the new database.
12. Run the following command:
%programfiles%\exchsrvr\Bin isinteg -s servername -fix -test alltests
Note The Isinteg.exe tool runs a test on all areas of each database. This tool reports results and tries to fix any problems that the tool finds.
13. Run the following command:
eseutil /mh %programfiles%\exchsrvr\mdbdata\priv1.edb
Note This command verifies the consistency of the databases. If a database is consistent, the command generates a "state = clean shutdown" message. This state indicates that all the log files have been committed to the Exchange store. If the command generates a "state = dirty shutdown" message, the database is not consistent.
14. Stop and then restart the Microsoft Exchange System Attendant service and the Microsoft Exchange Information Store service to make sure that the current logs are committed.
15. Test the mailboxes to verify that the mailboxes contain the correct data and to verify that correct mail flow is occurring.
16. Start the rest of the Exchange services. Back up the databases as soon as possible.