Solved

Exchange 2013 - Clients could not connect

Posted on 2014-10-15
3
528 Views
Last Modified: 2014-10-16
We have 5 exchange servers.  3 Database and 2 CAS.

One of our CAS vm's appeared to start having issues and began throwing this error in the event viewer.

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Health Manager service, but this action failed with the following error:
An instance of the service is already running.

All of our exchange boxes are:
Exchange Server 2013 Cumulative Update 3 (CU3)       15.0.775.38

With that said a lot of our citrix users were hit and miss.  I am guessing CAS5 was not allowing and CAS4 was.  Half the users could use outlook and have it load their profile etc.. the other half no, it would hand their citrix session.

This just randomly started happening yesterday Morning and a reboot fixed the server.  That is not normal nor does it tell us what we can do to prevent this in the future.

While Looking online I see a lot of suggestions that point to the RPC service terminating but there are no logs in our event viewer that indicate that.  Just the Service Control Manager and then the Health Manager.

If more detail needs to be provided please let me know, it is a fairly simple set up.  1 DAG, 5 servers, 2 of them CAS.
0
Comment
Question by:Missoulait
3 Comments
 

Author Comment

by:Missoulait
ID: 40383110
Event ID 7031

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange Health Manager service, but this action failed with the following error:
An instance of the service is already running.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 40383129
CU3 is no longer supported.
You need to upgrade to SP1 at a minimum, preferably CU5 to remain in support.

Exchange 2013 is still in active development, get the servers up to date then see if the problems continue.

It is no longer an option to ignore patching of Exchange, you need to stay on the current or previous CU release.

Simon.
0
 
LVL 12

Expert Comment

by:Md. Mojahid
ID: 40383633
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In-place Upgrading Dirsync to Azure AD Connect
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

839 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question