MSExchangeGuru.com

Learn Exchange the Guru way !!!

 

RPC Client Access Service keeps restarting in Exchange 2013

Let’s see how to address and issue where RPC Client Access Service keeps restarting on Exchange 2013 server with / without CU1.

Event log will show the below error:

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.

The service restarts by itself but it becomes annoying for the users because they will get an offline/online popup box in outlook.

This is an issue which occurs in only few environments and not in every environment so this might not occur in your environment.

There is no need of applying this fix until you face this issue.

Solution:

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_MACHINESoftwarePoliciesMicrosoftWindows 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**

Prabhat Nigam

Microsoft MVP | Exchange Server

Team @MSExchangeGuru

25 Responses to “RPC Client Access Service keeps restarting in Exchange 2013”

  1. Larry Says:

    HI I had this issue and I solved it by changing the MS Exchange RPC Client Access to log on using the system account instead on the NEtwotk Service account.

  2. Prabhat Nigam Says:

    Thank you Larry for the update. I have updated your fix in the document as well.

  3. Scott Says:

    Neither of these fixes worked for me on a server with CU1 installed. Stopping the Microsoft Exchage Health Manager service stopped the crashes.

  4. Prabhat Nigam Says:

    Thank you Scott for the update. I have updated this fix as well

  5. Marc Says:

    Can anyone confirm if this issue is fixed in CU2?

  6. Prabhat Nigam Says:

    @Marc
    This issue is not hitting all setups so it might be tough to fix. Also you can see there are multiple fix for the same issue.
    Anyways, as of now I have not heard any update from MS if they have it fixed in CU2. I will share as soon as I get any update.

  7. Ivailo Says:

    Prabhat,

    Shouldn’t the registry path be “HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\RPC”?

    Ivailo

  8. Prabhat Nigam Says:

    Ivailo,
    Have you got same issue fixed by that?

  9. Dave Carrick Says:

    2012 Server, Ex. 2013 CU1: +1 for stopping the exchange health manager service… it solved the issue instantly.

  10. pratheesh Says:

    I done it didn’t work but stopping Exchange Health Manager resolved issue for me

  11. Prabhat Nigam Says:

    @Dave and Pratheesh

    Am I correct in saying 3rd solution worked for you?

  12. Robert Says:

    Can anyone tell me exactly what the Health Manager Service does?

  13. Ratish Nair Says:

    Hey Robert – Exchange 2013 introduced “managed availability process” which monitors the server and performs automated troubleshooting tasks if it finds an issue with any of the components. MA runs within the Microsoft Exchange Health Manager service. Play with Get-ServerComponentState –Identity ServerName to know about Server Components and its current state.

  14. Robert Says:

    Gotcha,

    So basically, the service thinks it found something wrong with RPC so it’s restarting the service altogether? That doesn’t bode well for everyone connected. Oh well, let’s hope this issue is handled when CU2 comes out. I can’t of much else to do and I’m bothered by the fact that I have manually stop a service that sounds like it will actually help things in the long run.

  15. Ratish Nair Says:

    To be very honest with you, I’ve had several issues with MA in CU2 and earlier versions. After installing CU3 system is been stable for almost one week – 0 problems… apply it with confidence…

  16. Robert Says:

    Awesome, thanks for the genuine experience sharing. I confidently do everything after taking vm snapshots!

  17. Florin Lapadat Says:

    Hello,
    In my case, stopping the exchange health manager service solved the issue, but i wasn`t so happy to stop an exchange service.

    Last week I apply SP1 for Exchange. Before that, I start the exchange health manager service. Now everything works perfect.

    Be careful!! In case you are using third-party or custom-developed transport agents (in my case Kaspersky 8 for Microsoft Exchange), after applying SP1 for Exchange, Microsoft Exchange Transport service will no longer start. To solve the issue you must apply the fix from MS KB2938053 http://support.microsoft.com/kb/2938053/en-us

    Good luck!

  18. Prabhat Nigam Says:

    Thank you for sharing the update.

  19. Jovin Says:

    Hello, I have a bit different issue where all my services are shutdown and reconnected at around the same time every day.

    Application event 1002 msexchange Front End HTTP Proxy is found on the CAS server. It says Autodiscover,OAB,Web Services shutting down.

    I tried disabling HM service , but the issue still occurs .Prabhat , do you think your fixes above will apply to me?

  20. Prabhat Nigam Says:

    @Jovin
    If you are on SP1 then this issue has been taken care.

    I would need more info to see what is the issue. Managed availability might have restart app pools if they were being hung or got some issue.

    Run Exbpa and review more logs. Also check the task manager.

  21. Jovin Says:

    Hi Prabhat, I have disabled Health Manager service(Managed Availability) . So Autorecovery & responder should not function. Somehow it is not related to that. It is something else causing Application pool restarts. The information in the Client Access :-

    Log Name: Application
    Source: MSExchange Front End HTTP Proxy
    Date: 06/06/14 8:28:08 AM
    Event ID: 1002
    Task Category: Core
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: PRD-CAS-01.BANKING.QA
    Description:
    [Autodiscover] Application shutting down.
    Event Xml:

    1002
    4
    1
    0x80000000000000

    322847
    Application
    PRD-CAS-01.BANKING.QA

    Autodiscover

    The same events for OAB,EWS,EAS. Task manager shows everything is fine and this happens for less than a minute everyday . ExBPA only shows setting MaxUserPort to 60000 related to the problem.

  22. Jovin Says:

    Forgot to add ,I’m on SP1

  23. Josh Says:

    Been awhile since the last post, but…
    I’ve run into this issue as well. MSE RPC Service stops and restarts every few minutes.
    In Eventvwr: “Microsoft Exchange RPC service manager encountered an unexpected error while starting. Error details: The wait operation timed out (258)”

    On Exchange 2013, CU9, Co-existence.
    I’ve tried the three fixes suggested without success.

  24. Prabhat Nigam Says:

    Guys, log your issue at
    https://social.technet.microsoft.com/Forums/en-US/home?category=exchangeserver&filter=alltypes&sort=lastpostdesc

    or open a ticket with Microsoft. if it is a bug then Microsoft issue then you should not be charged.

    —–
    Just verify after a restarting server with only Microsoft service (disable all 3rd part service and restart).

  25. rami mansour Says:

    third solution is helpful with my case

Leave a Reply

migrate exchange to office 365

Categories

Archives