Solved

Exchange 2013 - Clients could not connect

Posted on 2014-10-15
3
547 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

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

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…
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

739 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