Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Exchange 2013 - Clients could not connect

Posted on 2014-10-15
3
Medium Priority
?
592 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 2000 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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

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

Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
How to effectively resolve the number one email related issue received by helpdesks.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
Suggested Courses
Course of the Month13 days, 13 hours left to enroll

963 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