• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

All Exchange 5.5 services fail to start

Cannot start any of the Exchange services. I keep getting an error of 1068 . The dependency service or group failed to start. At first the server crashed a couple of times. Bios and ram conflict, however this corrupted the information stores. It would not start up, so I disabled all the services for exchange so I wouldn't keep getting error msgs. I am back to using MS Mail. Is there any hope to this situation?

Thanks in advance to any that can help.

Greg
0
comeaug
Asked:
comeaug
  • 8
  • 7
1 Solution
 
David WilhoitSenior Consultant, ExchangeCommented:
Tell me about your setup:

Have the services started previously?
what is the exchange service account, and are all the services starting with it? If the MSExchangeSA isn't starting, it's probably the service account, but I can't tell yet, need more info.

0
 
comeaugAuthor Commented:
When the server was first installed (24months ago)everything worked well. Of course. However soon after I started to add users to the Exchange mail the server crashed a couple of times. Ram and Bios conflict. I downloaded a bios flash to fix the ram conflict under Dell's sugestion, Soon after the Information Stores failed to start. THe Exchange service account name is
fra1_wpp1 the server name is wppr_server. None of the services for Exchange will start right now.
0
 
comeaugAuthor Commented:
I changed the administrator password in the services for all of Exchange services. Then click start, some have started. They are as follows:
Exchange connectivity controller
Exchange directory
Exchange directory synchronization
Exchange message transfer agent
Exchange system attendant

When I try Information stores it returns an error 1011
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
David WilhoitSenior Consultant, ExchangeCommented:
1011, or -1011? If -1011, run from the command line, "isinteg -patch), then start the stores again.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
Oh, your services should start in this order, if manually done:

system attendant
directory service
information store
MTA
IMC
Event service

0
 
comeaugAuthor Commented:
Ok I have done exactly what you have suggested including the proper start up of services, however when trying to start IS it comes up with an error 1011 no dash.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
Was your Exchange server reinstalled at5 some point? If so, is it using the same Org Site and server name as before? they would need to be an exact match.

What events show up in the applog? I know about the 1068, that's a dependency error. Start the IS, and then look at the log for the errors. Please post here :)

don't worry, it can be fixed.
0
 
comeaugAuthor Commented:
No this is the original  install. We did have another server that we are still using. It was named wppr_server until the new one a arrived. The new one is now named wppr_server and the old one with ms mail is named wppr_serverb. As for the events log they are as follows
-MS ExchangeIS (684) the database engine 05.2653..0011 started.
-Information Store with unlimited storage capacity enabled.
-Repeated again
-Initializing the POP3 external interface
-Initializing the NNTP external interface
-Initializing the IMAP4 external interface
-Attempting to start the MS IS service
-The information store was restored from an offline backup. Run ISINTEG -patch before starting the IS
-Unable to start the IS. Error 0x3f3
-POP3 has stopped
-NNTP has stopped
--IMAP4 has stopped
-MS ExchangeIS (684) The database engine has stopped.
0
 
comeaugAuthor Commented:
No this is the original  install. We did have another server that we are still using. It was named wppr_server until the new one a arrived. The new one is now named wppr_server and the old one with ms mail is named wppr_serverb. As for the events log they are as follows
-MS ExchangeIS (684) the database engine 05.2653..0011 started.
-Information Store with unlimited storage capacity enabled.
-Repeated again
-Initializing the POP3 external interface
-Initializing the NNTP external interface
-Initializing the IMAP4 external interface
-Attempting to start the MS IS service
-The information store was restored from an offline backup. Run ISINTEG -patch before starting the IS
-Unable to start the IS. Error 0x3f3
-POP3 has stopped
-NNTP has stopped
--IMAP4 has stopped
-MS ExchangeIS (684) The database engine has stopped.
0
 
David WilhoitSenior Consultant, ExchangeCommented:
http://support.microsoft.com/default.aspx?scid=kb;en-us;149238

Ok, so I was off :) you still need to run isinteg -patch. The database will start.
0
 
comeaugAuthor Commented:
Hey you did it! All services started. I'm not sure how many points I have to give you but you certainly did a great job.

Thanks
Greg
0
 
David WilhoitSenior Consultant, ExchangeCommented:
Thank you sir, glad you're up and running again!

David
0
 
comeaugAuthor Commented:
Hey David I have trouble again. Need some points?

Greg
0
 
David WilhoitSenior Consultant, ExchangeCommented:
sure dude, what's up? sorry it took so long....

D
0
 
comeaugAuthor Commented:
I posted the question on the site.  Have a look into it. If not reply back and I will give all the dtails.

Thanks for replying
Greg
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 8
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now