sfcanderson
asked on
The Microsoft Exchange RPC Client Access service entered the stopped state
We're having a problem with one of our Exchange 2010 Standard servers, which holds all of the roles. It's set up with a basic DAG and a 2nd Exchange 2010 server that also holds all of the roles in a basic failover, which is not having any problems. This is our primary mail server that all of our clients connect to.
For the last two weeks the Microsoft Exchange RPC Client Access service is shutting down, which disconnects everyone from Outlook until we restart it. It's not crashing, the event log shows a graceful shutdown of the service (See event log at end of post).
There aren't any events near the times that it shuts down that point to why and it happens at different times throughout the day, so I'm running out of ideas.
Here are the recent times/dates to give you an idea:
3/9 - 9:28 am and 12:01 am
3/8 - 9:29 am and 8:18 am
3/7 - 4:11 pm
3/1 - 10:31 am and 8:49 am
2/28 - 3:41 pm and 2:20 pm
Does anyone have any thoughts on where to look for the reason the service is shutting down?
Event properties in the System log:
Log Name: System
Source: Service Control Manager
Date: 3/9/2011 9:28:24 AM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Servername.Internal.FQDN
Description:
The Microsoft Exchange RPC Client Access service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695- 8e1e-26931 d2012f4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="16384">7036</E ventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80800000000000 00</Keywor ds>
<TimeCreated SystemTime="2011-03-09T15: 28:24.6982 31100Z" />
<EventRecordID>20325</Even tRecordID>
<Correlation />
<Execution ProcessID="772" ThreadID="31324" />
<Channel>System</Channel>
<Computer>COMPUTERNAME</Co mputer>
<Security />
</System>
<EventData>
<Data Name="param1">Microsoft Exchange RPC Client Access</Data>
<Data Name="param2">stopped</Dat a>
<Binary>4D0053004500780063 0068006100 6E00670065 0052005000 43002F0031 000000</Bi nary>
</EventData>
</Event>
For the last two weeks the Microsoft Exchange RPC Client Access service is shutting down, which disconnects everyone from Outlook until we restart it. It's not crashing, the event log shows a graceful shutdown of the service (See event log at end of post).
There aren't any events near the times that it shuts down that point to why and it happens at different times throughout the day, so I'm running out of ideas.
Here are the recent times/dates to give you an idea:
3/9 - 9:28 am and 12:01 am
3/8 - 9:29 am and 8:18 am
3/7 - 4:11 pm
3/1 - 10:31 am and 8:49 am
2/28 - 3:41 pm and 2:20 pm
Does anyone have any thoughts on where to look for the reason the service is shutting down?
Event properties in the System log:
Log Name: System
Source: Service Control Manager
Date: 3/9/2011 9:28:24 AM
Event ID: 7036
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Servername.Internal.FQDN
Description:
The Microsoft Exchange RPC Client Access service entered the stopped state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-
<EventID Qualifiers="16384">7036</E
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80800000000000
<TimeCreated SystemTime="2011-03-09T15:
<EventRecordID>20325</Even
<Correlation />
<Execution ProcessID="772" ThreadID="31324" />
<Channel>System</Channel>
<Computer>COMPUTERNAME</Co
<Security />
</System>
<EventData>
<Data Name="param1">Microsoft Exchange RPC Client Access</Data>
<Data Name="param2">stopped</Dat
<Binary>4D0053004500780063
</EventData>
</Event>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Good find! After installing the second version of RU 3 the problem seems go have gone away.
You may also want to enable auditing on that server for starting and stopping services
If you have antivirus software running, verify that it has the appropriate exclusions for Exchange and IIS files