Jake Davis
asked on
Exchange 2007 Information Store Service not starting.
I have a Microsoft exchange 2007 server installed on windows server 2008 where the exchange server information store service has begun to fail. It is due to dependency services not starting. The dependency services are related to Microsoft Forefront. I have removed all instances of forefront from the registry in the past and then performed a re installation and gotten the exchange server working again. In this case, removing all instances of forefront from the registry has not helped. I am still getting the error. I have tried to install Exchange 2007 SP 2 as a response to this, and I am receiving an access denied error when it reaches the hub transport service. Any assistance with this would be invaluable.
From reading your question, I can see this server is now required disaster recovery. You should avoid using registry for removing any software. Always use control panel. If you have Database backup or it is on different drive follow this:
http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/Recovering-Exchange-2007-Server-RecoverServer-switch.html
http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/Recovering-Exchange-2007-Server-RecoverServer-switch.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check status of integration between Exchange store and Forefront by FSC Utility, if it integrated this can be disabled. https://technet.microsoft.com/en-us/library/dd639369.aspx follow this article and disable integration then check if services are working or not. Once services are working then un-install FPE properly.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
how big are the Exchange DB files, are logs committed?
have you tried a full re-install of forefront?
what are the specific errors in the system and application logs?
have you checked, repaired and compacted the Exchange DataBases off line(after backup again to be safe)?