RPC Client Access Service failing many times per day

My system log has numerous 7031 errors (up to 50 a day) indicating that the Exchange RPC Client Access service terminate unexpectedly.  Each time it happens all extenral (for sure) Outlook users lose contact and have to reconnect.

I also see WAS 5009 showing a process service one of the App Pools in IIS terminating unexpectedly.  Often it i the MSExchangeRpcProxyAppPool, but they also appear for ny of them.

I don't see any other interesting erros in the system logs or application logs during that time.

Any ideas on how to stabilize the RPC service so clients aren't forced to keep reconnecting?

Eric.

April 17th, 2013 7:11am

Post the detailed even log to understand the issue
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2013 1:55pm

Sure.

RPC Client access failure ID 7031:

- System

  - Provider

   [ Name]  Service Control Manager
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4}
   [ EventSourceName]  Service Control Manager
 
  - EventID 7031

   [ Qualifiers]  49152 

   Version 0 
   Level 2 
   Task 0 
   Opcode 0 
   Keywords 0x8080000000000000
 
  - TimeCreated

   [ SystemTime]  2013-04-17T13:55:56.255964200Z 
   EventRecordID 58817
 
   Correlation 
  - Execution

   [ ProcessID]  572
   [ ThreadID]  15224
 
   Channel System 
   Computer <server FQDN>
 
   Security

- EventData

  param1 Microsoft Exchange RPC Client Access
  param2 1
  param3 5000
  param4 1
  param5 Restart the service
   4D005300450078006300680061006E00670065005200500043000000
--------------------------------------------------------------------------------

Binary data:
In Words

0000: 0053004D 00780045 00680063 006E0061
0008: 00650067 00500052 00000043 
In Bytes

0000: 4D 00 53 00 45 00 78 00   M.S.E.x.
0008: 63 00 68 00 61 00 6E 00   c.h.a.n.
0010: 67 00 65 00 52 00 50 00   g.e.R.P.
0018: 43 00 00 00               C...

WAS RPCProxyAppPool failure ID 5011:

- System

  - Provider

   [ Name]  Microsoft-Windows-WAS
   [ Guid]  {524B5D04-133C-4A62-8362-64E8EDB9CE40}
   [ EventSourceName]  WAS
 
  - EventID 5011

   [ Qualifiers]  32768 
   Version 0 
   Level 3 
   Task 0 
   Opcode 0 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2013-04-17T14:16:27.000000000Z 
   EventRecordID 58844
 
   Correlation 
  - Execution

   [ ProcessID]  0
   [ ThreadID]  0
 
   Channel System 
   Computer <server FQDN>
 
   Security

- EventData

  AppPoolID MSExchangeRpcProxyAppPool
  ProcessID 4304
   6D000780
--------------------------------------------------------------------------------

Binary data:
In Words

0000: 8007006D   

In Bytes

0000: 6D 00 07 80               m..

Eric.

April 17th, 2013 5:23pm

I fail to see the description part in the information you posted.

Free Windows Admin Tool Kit Click here and download it now
April 17th, 2013 6:05pm

Sorry. Is this what you are looking for:

Log Name:      System

Source:        Service Control Manager

Date:          4/17/2013 11:03:32 AM

Event ID:      7031

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <server FQDN>

Description:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7031</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T15:03:32.094266000Z" />

    <EventRecordID>58874</EventRecordID>

    <Correlation />

    <Execution ProcessID="572" ThreadID="16232" />

    <Channel>System</Channel>

    <Computer><server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Microsoft Exchange RPC Client Access</Data>

    <Data Name="param2">1</Data>

    <Data Name="param3">5000</Data>

    <Data Name="param4">1</Data>

    <Data Name="param5">Restart the service</Data>

    <Binary>4D005300450078006300680061006E00670065005200500043000000</Binary>

  </EventData>

</Event>

Log Name:      System

Source:        Microsoft-Windows-WAS

Date:          4/17/2013 10:50:40 AM

Event ID:      5011

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      <Server FQDN>

Description:

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '13408'. The data field contains the error number.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />

    <EventID Qualifiers="32768">5011</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T14:50:40.000000000Z" />

    <EventRecordID>58867</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer><Server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="AppPoolID">MSExchangeRpcProxyAppPool</Data>

    <Data Name="ProcessID">13408</Data>

    <Binary>6D000780</Binary>

  </EventData>

</Event>

April 17th, 2013 6:23pm

Sorry. Is this what you are looking for:

Log Name:      System

Source:        Service Control Manager

Date:          4/17/2013 11:03:32 AM

Event ID:      7031

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <server FQDN>

Description:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7031</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T15:03:32.094266000Z" />

    <EventRecordID>58874</EventRecordID>

    <Correlation />

    <Execution ProcessID="572" ThreadID="16232" />

    <Channel>System</Channel>

    <Computer><server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Microsoft Exchange RPC Client Access</Data>

    <Data Name="param2">1</Data>

    <Data Name="param3">5000</Data>

    <Data Name="param4">1</Data>

    <Data Name="param5">Restart the service</Data>

    <Binary>4D005300450078006300680061006E00670065005200500043000000</Binary>

  </EventData>

</Event>

Log Name:      System

Source:        Microsoft-Windows-WAS

Date:          4/17/2013 10:50:40 AM

Event ID:      5011

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      <Server FQDN>

Description:

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '13408'. The data field contains the error number.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />

    <EventID Qualifiers="32768">5011</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T14:50:40.000000000Z" />

    <EventRecordID>58867</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer><Server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="AppPoolID">MSExchangeRpcProxyAppPool</Data>

    <Data Name="ProcessID">13408</Data>

    <Binary>6D000780</Binary>

  </EventData>

</Event>

  • Edited by E Long Wednesday, April 17, 2013 3:26 PM
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2013 6:23pm

Sorry. Is this what you are looking for:

Log Name:      System

Source:        Service Control Manager

Date:          4/17/2013 11:03:32 AM

Event ID:      7031

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      <server FQDN>

Description:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />

    <EventID Qualifiers="49152">7031</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x8080000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T15:03:32.094266000Z" />

    <EventRecordID>58874</EventRecordID>

    <Correlation />

    <Execution ProcessID="572" ThreadID="16232" />

    <Channel>System</Channel>

    <Computer><server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="param1">Microsoft Exchange RPC Client Access</Data>

    <Data Name="param2">1</Data>

    <Data Name="param3">5000</Data>

    <Data Name="param4">1</Data>

    <Data Name="param5">Restart the service</Data>

    <Binary>4D005300450078006300680061006E00670065005200500043000000</Binary>

  </EventData>

</Event>

Log Name:      System

Source:        Microsoft-Windows-WAS

Date:          4/17/2013 10:50:40 AM

Event ID:      5011

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      <Server FQDN>

Description:

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '13408'. The data field contains the error number.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-Windows-WAS" Guid="{524B5D04-133C-4A62-8362-64E8EDB9CE40}" EventSourceName="WAS" />

    <EventID Qualifiers="32768">5011</EventID>

    <Version>0</Version>

    <Level>3</Level>

    <Task>0</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2013-04-17T14:50:40.000000000Z" />

    <EventRecordID>58867</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>System</Channel>

    <Computer><Server FQDN></Computer>

    <Security />

  </System>

  <EventData>

    <Data Name="AppPoolID">MSExchangeRpcProxyAppPool</Data>

    <Data Name="ProcessID">13408</Data>

    <Binary>6D000780</Binary>

  </EventData>

</Event>

  • Edited by E Long Wednesday, April 17, 2013 3:26 PM
April 17th, 2013 6:23pm

I had the same issue. Installing CM1 seemed to have helped. It's been running for two days without these errors.
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2013 6:38pm

I have CU1 installed and it hasn't seemed to make much difference. 
April 17th, 2013 7:08pm

It could also be CPU related. Take a look at MSExchangeRpcProxyAppPool in IIS application pools and see if you can limit it.
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2013 4:23pm

I have the exact same problem, 7031 event id's (7 over a 24 hour period) and several 5011 and 5009 event errors mainly related to the  MSExchangeRpcProxyAppPool app pool.

I completely re-installed the system, and used recover server setup switch. Formatted the C drive and did not use the old MSexchange files (except for the mailbox database + log files).

This indeed leads to outlook being unable to connect, after a while (at the old system, anywhere between one and 7 days I couldn't even kill the process (access denied), the only thing I can do is a full reboot.

Now this is a Hyper-V VM, running on 2012, it runs the OS, Exchange 2013 CU1 (I didn't seem to have this problem when using 2013 RTM) and Remote Access and NPS.

Now I am not sure what else to do, as a complete re-install didn't seem to work at all.

edit:

After about 1.5 days, the server again needed to restart for outlook clients to be able to connect. (ActiveSync continues to work normally, so does OWA).

The RPC CA service failes, but a restart doesn't work as the old process is still running, no way to kill the old process, as any attempt either via taksmgr or process explorer leads to access denied (even after specifically assigning myself rights to the process)

In event log, first 7031 appears, followed by 7032 and finally several 7011, and the 5011 continues to appear.

7031:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

7032:

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:

An instance of the service is already running.

7011

a timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSExchangeRPC service.

and

5011

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '21368'. The data field contains the error number.

April 21st, 2013 10:24pm

I have the exact same problem, 7031 event id's (7 over a 24 hour period) and several 5011 and 5009 event errors mainly related to the  MSExchangeRpcProxyAppPool app pool.

I completely re-installed the system, and used recover server setup switch. Formatted the C drive and did not use the old MSexchange files (except for the mailbox database + log files).

This indeed leads to outlook being unable to connect, after a while (at the old system, anywhere between one and 7 days I couldn't even kill the process (access denied), the only thing I can do is a full reboot.

Now this is a Hyper-V VM, running on 2012, it runs the OS, Exchange 2013 CU1 (I didn't seem to have this problem when using 2013 RTM) and Remote Access and NPS.

Now I am not sure what else to do, as a complete re-install didn't seem to work at all.

edit:

After about 1.5 days, the server again needed to restart for outlook clients to be able to connect. (ActiveSync continues to work normally, so does OWA).

The RPC CA service failes, but a restart doesn't work as the old process is still running, no way to kill the old process, as any attempt either via taksmgr or process explorer leads to access denied (even after specifically assigning myself rights to the process)

In event log, first 7031 appears, followed by 7032 and finally several 7011, and the 5011 continues to appear.

7031:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

7032:

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:

An instance of the service is already running.

7011

a timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSExchangeRPC service.

and

5011

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '21368'. The data field contains the error number.

  • Edited by sjaak327 Monday, April 22, 2013 9:11 AM
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2013 10:24pm

I have the exact same problem, 7031 event id's (7 over a 24 hour period) and several 5011 and 5009 event errors mainly related to the  MSExchangeRpcProxyAppPool app pool.

I completely re-installed the system, and used recover server setup switch. Formatted the C drive and did not use the old MSexchange files (except for the mailbox database + log files).

This indeed leads to outlook being unable to connect, after a while (at the old system, anywhere between one and 7 days I couldn't even kill the process (access denied), the only thing I can do is a full reboot.

Now this is a Hyper-V VM, running on 2012, it runs the OS, Exchange 2013 CU1 (I didn't seem to have this problem when using 2013 RTM) and Remote Access and NPS.

Now I am not sure what else to do, as a complete re-install didn't seem to work at all.

edit:

After about 1.5 days, the server again needed to restart for outlook clients to be able to connect. (ActiveSync continues to work normally, so does OWA).

The RPC CA service failes, but a restart doesn't work as the old process is still running, no way to kill the old process, as any attempt either via taksmgr or process explorer leads to access denied (even after specifically assigning myself rights to the process)

In event log, first 7031 appears, followed by 7032 and finally several 7011, and the 5011 continues to appear.

7031:

The Microsoft Exchange RPC Client Access service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.

7032:

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Microsoft Exchange RPC Client Access service, but this action failed with the following error:

An instance of the service is already running.

7011

a timeout (30000 milliseconds) was reached while waiting for a transaction response from the MSExchangeRPC service.

and

5011

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '21368'. The data field contains the error number.

  • Edited by sjaak327 Monday, April 22, 2013 9:11 AM
April 21st, 2013 10:24pm

In my case the problems didn't/don't cause the system to stop completely - it just disconnects all the clients for between a minute and 5 minutes.

Based on jalabert's comment, I took a careful look at what was happening.  Since it was happening so frequently I could literally watch in task manager as it occured:  One of the IIS Worker processes begins consuming more and more CPU and memory to the point where it was consuming all available memory and CPU.  At that point the system would log the 7031 error.  Shortly after that the system would return much more reasonable resource levels (it was hard to tell if the IIS Worker process was being replaced or just freeing up.)

Taking a look at the configuration of the virtual machine and the Hyper-V server I discovered:

1) The system drive for the Exchange VM was configured as a dynamic drive, not a static drive

2) Only 1 virtual processor was assigned to it

3) Total allocated memory was 8GB (Microsoft's minimum, but I now suspect that minimum is barely enough to let the sytem run without keeling over permanently - given a system with only about 30 regular users you would think the minimum would be enough)

4) The page file in the Exchange VM was barely 3.5GB.

Over the weekend I had the drive converted to a fixed size VHDX, added an additional processor, increased RAM to 10GB (all I could for the moment), and reset the page file to something much larger.

The RPC Client Access service crashes dropped from more than 50 a day to about 3 and recovery when it happens is much, much faster.  The remaining crashes seem to be centered around the time most of the users are coming on line for the first time for the day.

Shortly we will be adding additional RAM to the box and rearranging a couple of things so I can get the RAM allocated to the Exchange VM raised to 16GB and add a couple more processors.  Hopefully, that will resolve the remaining RPC Client Server crashes.

Final note:  Every crash of the RPC Client Service appears to be preceded by the 5011 WAS communication error event, but not every 5011 is followed by an RPC Client Service crash.  The 5011 errors are still happening 10 or 12 times a day.  Hopefully those will go away also with a bit more resources available to the Exchange server.


Free Windows Admin Tool Kit Click here and download it now
April 25th, 2013 1:14am

In my case the problems didn't/don't cause the system to stop completely - it just disconnects all the clients for between a minute and 5 minutes.

Based on jalabert's comment, I took a careful look at what was happening.  Since it was happening so frequently I could literally watch in task manager as it occured:  One of the IIS Worker processes begins consuming more and more CPU and memory to the point where it was consuming all available memory and CPU.  At that point the system would log the 7031 error.  Shortly after that the system would return much more reasonable resource levels (it was hard to tell if the IIS Worker process was being replaced or just freeing up.)

Taking a look at the configuration of the virtual machine and the Hyper-V server I discovered:

1) The system drive for the Exchange VM was configured as a dynamic drive, not a static drive

2) Only 1 virtual processor was assigned to it

3) Total allocated memory was 8GB (Microsoft's minimum, but I now suspect that minimum is barely enough to let the sytem run without keeling over permanently - given a system with only about 30 regular users you would think the minimum would be enough)

4) The page file in the Exchange VM was barely 3.5GB.

Over the weekend I had the drive converted to a fixed size VHDX, added an additional processor, increased RAM to 10GB (all I could for the moment), and reset the page file to something much larger.

The RPC Client Access service crashes dropped from more than 50 a day to about 3 and recovery when it happens is much, much faster.  The remaining crashes seem to be centered around the time most of the users are coming on line for the first time for the day.

Shortly we will be adding additional RAM to the box and rearranging a couple of things so I can get the RAM allocated to the Exchange VM raised to 16GB and add a couple more processors.  Hopefully, that will resolve the remaining RPC Client Server crashes.

Final note:  Every crash of the RPC Client Service appears to be preceded by the 5011 WAS communication error event, but not every 5011 is followed by an RPC Client Service crash.  The 5011 errors are still happening 10 or 12 times a day.  Hopefully those will go away also with a bit more resources available to the Exchange server.


  • Edited by E Long Wednesday, April 24, 2013 10:14 PM
  • Proposed as answer by reprac Monday, April 29, 2013 9:27 PM
April 25th, 2013 1:14am

In my case the problems didn't/don't cause the system to stop completely - it just disconnects all the clients for between a minute and 5 minutes.

Based on jalabert's comment, I took a careful look at what was happening.  Since it was happening so frequently I could literally watch in task manager as it occured:  One of the IIS Worker processes begins consuming more and more CPU and memory to the point where it was consuming all available memory and CPU.  At that point the system would log the 7031 error.  Shortly after that the system would return much more reasonable resource levels (it was hard to tell if the IIS Worker process was being replaced or just freeing up.)

Taking a look at the configuration of the virtual machine and the Hyper-V server I discovered:

1) The system drive for the Exchange VM was configured as a dynamic drive, not a static drive

2) Only 1 virtual processor was assigned to it

3) Total allocated memory was 8GB (Microsoft's minimum, but I now suspect that minimum is barely enough to let the sytem run without keeling over permanently - given a system with only about 30 regular users you would think the minimum would be enough)

4) The page file in the Exchange VM was barely 3.5GB.

Over the weekend I had the drive converted to a fixed size VHDX, added an additional processor, increased RAM to 10GB (all I could for the moment), and reset the page file to something much larger.

The RPC Client Access service crashes dropped from more than 50 a day to about 3 and recovery when it happens is much, much faster.  The remaining crashes seem to be centered around the time most of the users are coming on line for the first time for the day.

Shortly we will be adding additional RAM to the box and rearranging a couple of things so I can get the RAM allocated to the Exchange VM raised to 16GB and add a couple more processors.  Hopefully, that will resolve the remaining RPC Client Server crashes.

Final note:  Every crash of the RPC Client Service appears to be preceded by the 5011 WAS communication error event, but not every 5011 is followed by an RPC Client Service crash.  The 5011 errors are still happening 10 or 12 times a day.  Hopefully those will go away also with a bit more resources available to the Exchange server.


  • Edited by E Long Wednesday, April 24, 2013 10:14 PM
  • Proposed as answer by reprac Monday, April 29, 2013 9:27 PM
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2013 1:14am

In my case, the VM was configured with 8 GB, Fixed VHD disks and 4 virtual CPU's. I have reduced the number of virtual CPU's to two, and since 3.5 days I have no RPC service crashes, no WAS errors. I keep my fingers crossed but it seems reducing the number of virtual cpu's from 4 to 2 might have fixed the problems I was having.
April 25th, 2013 12:40pm

Same here, all my AppPools are also crashing on regular basis. Happens after CU1. Eventlogs like:

A process serving application pool 'MSExchangeRpcProxyAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '5232'. The data field contains the error number.

A process serving application pool 'MSExchangeSyncAppPool' suffered a fatal communication error with the Windows Process Activation Service. The process id was '7176'. The data field contains the error number.

A process serving application pool 'MSExchangePowerShellFrontEndAppPool' terminated unexpectedly. The process id was '11612'. The process exit code was '0xffffffff'.

A process serving application pool 'MSExchangeOWAAppPool' terminated unexpectedly. The process id was '9772'. The process exit code was '0xffffffff'.

Free Windows Admin Tool Kit Click here and download it now
April 28th, 2013 1:00am

Hi,

Can you check 'MSExchangeRpcProxyAppPool' whether associated with any other 3rd partly .DLL files.

I had the same issue in Exchange 2003 Front End server which is caused Cisco .DLL file.

Regards 

April 28th, 2013 2:24pm

I don't see any other elements associated with the pool beyond the Exchange RPC applications.

The RPC Client Service failures are still happening, although with added processor (2 virtual) and RAM (16GB) the frequency went down significantly.  On average it is still happening 4 or 5 times per day.  There are enough users on the system that someone gets affected when connections to the Exchange server drop.

Any suggestions on where else to look to troubleshoot the problem?


Free Windows Admin Tool Kit Click here and download it now
May 9th, 2013 6:04pm

I don't see any other elements associated with the pool beyond the Exchange RPC applications.

The RPC Client Service failures are still happening, although with added processor (2 virtual) and RAM (16GB) the frequency went down significantly.  On average it is still happening 4 or 5 times per day.  There are enough users on the system that someone gets affected when connections to the Exchange server drop.

Any suggestions on where else to look to troubleshoot the problem?


  • Edited by E Long Thursday, May 09, 2013 3:04 PM
May 9th, 2013 6:04pm

I don't see any other elements associated with the pool beyond the Exchange RPC applications.

The RPC Client Service failures are still happening, although with added processor (2 virtual) and RAM (16GB) the frequency went down significantly.  On average it is still happening 4 or 5 times per day.  There are enough users on the system that someone gets affected when connections to the Exchange server drop.

Any suggestions on where else to look to troubleshoot the problem?


  • Edited by E Long Thursday, May 09, 2013 3:04 PM
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2013 6:04pm

Stopping the Exchange Health Manager service fixes it, I had the same problem, and this is the solution for now. No more Outlook disconnects.
June 27th, 2013 12:46am

Sorry for my question, but we have installed the German version of the Exchange 2013: Do you mean the "C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Diagnostics.Service.exe" ?

Free Windows Admin Tool Kit Click here and download it now
June 27th, 2013 6:56pm

I have found the service you referenced: it is called Microsoft Exchange Integrity (if I translate the German words 1:1 back to English).

Only stopping the service is not enough. Our Exchange server startet the service during the night again. He have to set it do the manual start type and stopp it. Do you have experience about the impact on the Exchange server?

Best regards,

Peter

June 28th, 2013 10:23am

hello dear.. i would suggest you to try .. hope this helps

"1. This can be fixed by adding the following registry key. Here are the steps:

  1. On windows 2008 Click on start Run or on windows 2012 open command prompt with run as administrator
  2. Type regedit and hit enter
  3. Go to the following location

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\

  4. Right Click and select new Dword Value
  5. Type MinimumConnectionTimeout with the decimal value 120
  6. Close regedit and restart the server.

or

2. This can also be fixed by the below solution:

Change the log on account of MS Exchange RPC Client Access service from system account to Netwotk Service account.

or

3. Another fix for this issue is here:

Stop and Start the Microsoft Exchange Health Manager service.

Issue should get fixed. **use at your own risk**"

Free Windows Admin Tool Kit Click here and download it now
June 29th, 2013 3:03am

hello dear.. i would suggest you to try .. hope this helps

"1. This can be fixed by adding the following registry key. Here are the steps:

  1. On windows 2008 Click on start Run or on windows 2012 open command prompt with run as administrator
  2. Type regedit and hit enter
  3. Go to the following location

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\

  4. Right Click and select new Dword Value
  5. Type MinimumConnectionTimeout with the decimal value 120
  6. Close regedit and restart the server.

or

2. This can also be fixed by the below solution:

Change the log on account of MS Exchange RPC Client Access service from system account to Netwotk Service account.

or

3. Another fix for this issue is here:

Stop and Start the Microsoft Exchange Health Manager service.

Issue should get fixed. **use at your own risk**"

August 5th, 2013 2:54pm

CU2 has the same issue. I am working on a 4 server (2 CAS, 2 MBX) install for a customer and all 4 servers were logging the error in the event log. The customer was complaining of random Outlook disconnects. They would usually start happening after couple of days after reboot. I fixed it by disabling the Exchange Health Manager service. No issues for the last week and a half. Today I will restart the service on all servers and try #1 and/or #2 as suggested by Shah.

Best regards,

Ivailo Mitkov

Free Windows Admin Tool Kit Click here and download it now
August 9th, 2013 1:58pm

The second did the trick for me. MS Exchange RPC Client Access service cant be running with "NT AUTHORITY\SYSTEM" it should be running with "NT AUTHORITY\NETWORK SERVICE"

If network service will ask for password just delete them and press OK.

Dont disable Microsoft Exchange Health Manager service because then you wont get any health information from Exchange.

That will do the trick.

September 2nd, 2013 4:16am

Same issues here with Ex2013 CU1. Wondering what would be the Microsoft's official suggested repair for tackling this issue?
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2013 4:12pm

If you turned off IPv6 immediately turn it back on! (will never be turned off)
December 11th, 2013 1:39am

Harri, thank you!

It is really helped me for solve this issue.

  • Edited by edmar_dp 5 hours 12 minutes ago
Free Windows Admin Tool Kit Click here and download it now
December 11th, 2013 1:41am

Harri, thank you!

It is really helped me for solve this issue.

  • Edited by edmar_dp Wednesday, December 11, 2013 6:44 AM
December 11th, 2013 9:41am

"1. This can be fixed by adding the following registry key. Here are the steps:

  1. On windows 2008 Click on start Run or on windows 2012 open command prompt with run as administrator
  2. Type regedit and hit enter
  3. Go to the following location

    HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\

  4. Right Click and select new Dword Value
  5. Type MinimumConnectionTimeout with the decimal value 120
  6. Close regedit and restart the server.

or

Error in "3":

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Rpc

http://blogs.technet.com/b/messaging_with_communications/archive/2012/06/06/outlook-anywhere-timeout-issue-and-recommendation.aspx


Free Windows Admin Tool Kit Click here and download it now
January 10th, 2014 6:59am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics