We are having an issue with the information store in Exchange 2007 stopping for no apparent reason. The event logs show it was stopped by the System account. This issue occurs when the exchange server loses connectivity, presumably because it loses connectivity with it's partner at a different facility. The Microsoft Exchange Information Store service was successfully sent a stop control.That is the event that is logged....but we didn't send a stop control :/This is a single domain with 4 DC's on x86 2003 Standard and 2 x64 Server 2003 Standard boxes running Exchange 2007. I have turned diagnostic logging for the information store service to maximum, however, it isn't providing any data that leads me to a solution as of yet.Thanks for any help you can provide!

Could you provide the exchange topology? Is the exchange information store service able to restart again? If no, is there any error event in the application log? So you got an information event 7035, please see KB 945078 that described a similar symptom for exchange system attendant service Exchange services will stop gracefully to allow for the installation of some windows update, please refer KB 906602 to check if there’s any installation failure for certain updates on the day that the issue occurred Please run ExBPA against the exchange server for health checkJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

Hi,Did you check IPV6 is enabled in your server?If not enable it and start Information Store Service again Regards from www.windowsadmin.info

The exchange topology is 2 full service mailbox/hub/cas servers, with public folders replicating between them. None of the mail databases are currently using replication, though we did play with SCR some and plan on implementing it in the future.The exchange information store is able to be restarted properly each time, and the event logs show the service stopping properly, but it's executed by the system account. The application event log shows each database being dismounted at the same time. It's a very polite exit, but quite annoying!!We are not using clustering at this point in time, the KB article didn't seem to apply to a standard build.We were not applying any updates, this happens specifically when there is a loss of connectivity to the other site, and it only happens on the 'original' Exchange 2007 box, not the second one that was added.EXBpa reports minor items like needing anti-spam and storage/NIC drivers being old (we're using VMWare ESX 4.x), but nothing of value.

We are running Server 2003, Exchange 2007. I do not typically put IPv6 on Server 2003 - are you suggesting that we should??

Is there any difference between two exchange servers, like rollup version, third-party software (the update of third-party software), or update? There must be certain thing that keeps the service running well on the second exchange server Please increase the diagnostic logging level if IS service on the problematic exchange server, and monitor the events after reproduce the issue again, see if we can find more relevant infoJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com

The only difference between the 2 servers that I am aware of is the newer, 2nd Exchange server, is not running SP2 Rollup 2, it is just at SP2. The servers were built by different people, so it's possible there are some less visible differences.Diagnostic logging is set to expert on IS service, and has revealed nothing of value to me when the issue occurs :/