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

exchange mailbox replication service wont start after the server is rebooted

When the exchange server was rebooted twice in the past 2 weeks, the exchange replication service did not start on its own.  Also there has been times when the server was not rebooted and the service stopped again on its own. I had to start the service. Has anyone seen this and if so, what did you do to resolve it?
0
vmich
Asked:
vmich
  • 6
  • 5
  • 2
  • +1
2 Solutions
 
AmitIT ArchitectCommented:
I guess it is Exchange 2010, what is the service pack and RU level on this server?
0
 
Exchange_GeekCommented:
If a particular service wouldn't start, Exchange would throw up an error in the App log - please mention the details about it.

Also, which Exchange version are you working with?

Any service pack or roll up applied?

If you manually try to start the service - do you get any errors?

How about if you delay the start of the service - does it still not start?

Regards,
Exchange_Geek
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Hope you find something in the App logs at the same time to troubleshoot the issue.

Also is there any AV ... hope its not scanning exchange related files\folders ?

Try to upgrade the server with SP if possible.

- Rancy
0
 
vmichAuthor Commented:
It is exchange 2010 and there are 7 CAS servers, of which this is occuring on 4 of them. It is real spuradic and the last time it happened was about a week ago now.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So does it starts afterwards manually ... maybe you can set the service for delay start :)

- Rancy
0
 
vmichAuthor Commented:
Yes it does start if you manually click on the service once the alert comes in that it has stopped, and restart it..
0
 
vmichAuthor Commented:
So you think by setting the service to delay start, that should fix the issue then?
0
 
vmichAuthor Commented:
One more item I forgot to mention I think is that it happens when the server is running and no reboot has oocured, meaning the service will just stop and then have to be restarted.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So you can change it to "Automatic (Delay Start)" on the properties of the service.

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
One more item I forgot to mention I think is that it happens when the server is running and no reboot has oocured, meaning the service will just stop and then have to be restarted. - If so you will get some events in the App logs for the service as to why it Terminated ?

- Rancy
0
 
vmichAuthor Commented:
I dont see any events about the service stopping in the event viewer....
The only event I saw was event id 12014
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Thats strange as you say it seems the service kind of crashed or gets killed .... so there has to be some Event for it ?
As you said you have many Exchange servers and this issue is seen only on few .... what is the SP and RU's .... AV and are all on the same version ? Hope exclusions set not to scan Exchange related stuff.

- Rancy
0
 
vmichAuthor Commented:
solved
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 5
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now