Let me first start out by saying im fairly new to this so any and all help will be appreciated. We are running Exchange 2003 SP2 with an operating system of Windows Server 2003 Enterprise R2. The problem I am having is when i try to start system attendant, it tells me that it started then stopped, and gives an example of another service that does that when it has nothing to do. Then I try to start the Exchange Information store, MTA Stacks, Event, and all of those service come back with an error 1068, dependency group failed to start. I am looking for any solutions that will help me get this running. Reminding you that I am new to this, if there is any information you would like that I am missing on here, please let me know that as well. Thank you all so much and I look forward to any and all replies.

Why was the service in a stopped condition? Was anything changed or installed on the server just prior?

Nothing was changed at all. we had a BSOD and when i corrected it, i can no longer get the services to start.

http://support.microsoft.com/kb/821907

This talks about Exchange 2007 and 2010, im working with 2003. Same processes???

How to Troubleshoot Exchange Server 2003 System Attendant When It Does Not Start http://support.microsoft.com/kb/821907

Thank you, checking it now

no, did not work, still can not start the service or the dependencies

did you enable diagnostic logging as described in the article? try to start the service again and see if any new/ different events are in the event logs.

What errors are throwing in the event log? Mark Morowczynski|MCT| MCSE 2003:Messaging, Security|MCITP:EMA 2K7,EDA Win 7,ES,SA,EA|MCTS:Windows Mobile Admin|Security+|http://almostdailytech.com

Hi Navy Check the services applet and see what other services have not started like IIS . Also check the event viewer for any Exchange related errors that may have occured before the on posted here. most importantly check that you can still mount the information store. If you cannot mount it then your database is corrupt and the error message that you are reporting is honestly the least of your concerns. In the bigger picture, you could be sitting with a corrupt exchange server. if the problem with IIS try to start it and then start the rest of services if it has the same problem and couldn't start so you should uninstall the IIS service and reinstall it back again , after doing so if the problem still you should make a recovery for Exchange using the disataser recovery switch "<drive>:\Setup\I386\Setup.exe /DisasterRecovery" from the installation CD . for more information about the Recovering a Failed Exchange 2003 Member Server Using the Disaster Recovery Switch check the link below http://www.msexchange.org/tutorials/Recovering-Failed-Exchange-2003-Member-Server-Using-Disaster-Recovery-Switch.html wish this will be helful Regards

Thank you all so far, as I am the only one working on this here, plus having another job to do, I have taken the notes of what you wrote here and will try them, and get back here when i can to either post errors or let you know what it did. Thanks again to all who have contributed so far.

Ahmed, is correct check IIS since if its having problems it can cause these types of issues. I would also look at all the services that are set to automatically startup and see what there status is. Once you have those resolved if the issue persist, it could very well be as Ahmed suggested that you have a corrupt EDB or Log file. There are several ways to resolve this with ESEUTIL and ISINTEG but first ensure that you have a backup of the EDB and LOG files BEFORE YOU DO ANYTHING. After that you can look to repairing the database. Alternatively you could also move the old databases out of the directory they are in (After making a copy) and then start the services. This will create a NEW empty database but it will bring everything up and allow your users to start sending and receiving email again. Then you can use the RSG to recover the missing data in the EDB (after repairing it) This is called dial-tone recovery. You may also want to check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp which can repair and then open the offline EDB without the need to use the RSG. Once repaired and opened DigiScope will allow you to export to PST or migrate the missing data back into the new Production Exchange Store on the fly. Troy Werelius Lucid8