For the last little while I've been having issues with the information store terminating unexpectedly. It was causing the side effect of volume shadow copies not working, but I realized that that was not the cause, apparently that happens when the database is in a dirty state. I was trying to do some debugging and testing, so I changed the schedule for the assistants to only run Monday AM. For some reason, it ran this morning and crashed the information store again. I double-checked the scheduling and it was still set to run once a week, Monday AM. So for some reason it ran even though it was not supposed to. I did notice that one second after the assistants script ran the store dies: Event Type: Information Event Source: MSExchange Assistants Event Category: Assistants Event ID: 9002 Date: 4/20/2011 Time: 3:42:51 AM User: N/A Computer: SRV01 Description: Service MSExchangeMailSubmission. Stopped processing database First Storage Group/Mailbox Database (c4417171-5e25-4332-85b5-48270925cebd). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. and right afterwards: Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7034 Date: 4/20/2011 Time: 3:42:52 AM User: N/A Computer: SRV01 Description: The Microsoft Exchange Information Store service terminated unexpectedly. It has done this 1 time(s). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Is it possible that the scripts can get corrupted? It apparently is something that happens right at the end of its processing that the database doesn't like. All I can do is guess... All the script does is purge items in the Junk and Deleted Items folder if they are older than one month.

Hi No one knows the situation more than you. Many accidents like script, plug-in software will cause store crashing. You have given your answer and you should test it. You can post your script to http://social.technet.microsoft.com/Forums/en-US/exchangesvrdevelopment/threads maybe they can help you to find reason of crash. Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I am seeing similar issues on an Exchange 2010 database. Were you ever able to identify the problem? What storage vendor were you using? Thanks. John