Microsoft Exchange RPC Client Access Service didn't automatically start after lastest Security patches

hi all

running ex2010 with lastest SP.

after the last patching round the Microsoft Exchange RPC Client Access Service didnt start automatically on  all 3 of our primary or active mailbox servers and 3 primary CAS servers . Just wondering if anyone else experienced this?

1 mailbox server needed another restart to get the service to start again. The other 5 servers we were able to start the service manually ok.
LVL 2
Daryl GawnSystem AdministratorAsked:
Who is Participating?
 
McKnifeCommented:
Of course the event log should also be consulted - it will have an entry that says if it was a timeout or not. Just serach for the service name within the windows system event log.
0
 
McKnifeCommented:
Hi.

Be aware that this could simply be a performance problem. Services have time-outs and if the service hasn't started within a certain time (usually 2 minutes), it will simply stop trying. If updates were installed, the machine will reboot and when rebooting, complte the update installation, which causes a heavy load on the hard drive and can lead to the mentioned effect.

So please check the performance of the storage system(s) and/or modify the timeouts.
0
 
Daryl GawnSystem AdministratorAuthor Commented:
thanks McKnife, i am monitoring the performance.  Just thought id ask incase anyone was experiencing the same around updates
0
 
Daryl GawnSystem AdministratorAuthor Commented:
we wont know if this is going to happen again untill next reboot but McKnife has good suggestions regarding performance that we will monitor
0
 
McKnifeCommented:
No rush in closing, come back any time.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.