Cant start MS Exchange Replication Service

After installing updates on Windows Server 2008 I cant start MS Exchange Replication. The Error log says:

Log Name:      Application
Source:        MSExchangeRepl
Date:          28. 7. 2016 6:39:20
Event ID:      4004
Task Category: Service
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Couldn't start the Microsoft Exchange Replication service. Error: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager' threw an exception. ---> System.InvalidCastException: Specified cast is not valid.
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.<LoadRegistryValues>b__2(RegistryKey key)
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.TryGetRegistryParameters(Action`1 operation)
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.get_ConfigUpdaterTimerIntervalSlow()
   at Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager..ctor()
   at Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Cluster.ReplayService.ReplayService.OnStartInternal(String[] args)
   at Microsoft.Exchange.Cluster.Replay.Watson.<>c__DisplayClass1.<SendReportOnUnhandledException>b__0()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.Diagnostics.ExWatson.SendReportOnUnhandledException(MethodDelegate methodDelegate, IsExceptionInteresting exceptionInteresting, Boolean terminating)
   at Microsoft.Exchange.Cluster.Replay.Watson.SendReportOnUnhandledException(Action action)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.<>c__DisplayClass2.<OnStart>b__0()
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.SendWatsonReportOnTimeout(String caller, TimeSpan timeout, TimerCallback timeoutHandler, UnderTimeoutDelegate underTimeoutDelegate)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.OnStart(String[] args)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.ServiceQueuedMainCallback(Object state)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MSExchangeRepl" />
    <EventID Qualifiers="49156">4004</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-28T04:39:20.000000000Z" />
    <EventRecordID>1142649</EventRecordID>
    <Channel>Application</Channel>
    <Computer></Computer>
    <Security />
  </System>
  <EventData>
    <Data>System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager' threw an exception. ---&gt; System.InvalidCastException: Specified cast is not valid.
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.&lt;LoadRegistryValues&gt;b__2(RegistryKey key)
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.TryGetRegistryParameters(Action`1 operation)
   at Microsoft.Exchange.Cluster.Replay.RegistryParameters.get_ConfigUpdaterTimerIntervalSlow()
   at Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager..ctor()
   at Microsoft.Exchange.Cluster.ReplayService.ReplayComponentManager..cctor()
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Cluster.ReplayService.ReplayService.OnStartInternal(String[] args)
   at Microsoft.Exchange.Cluster.Replay.Watson.&lt;&gt;c__DisplayClass1.&lt;SendReportOnUnhandledException&gt;b__0()
   at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
   at Microsoft.Exchange.Diagnostics.ExWatson.SendReportOnUnhandledException(MethodDelegate methodDelegate, IsExceptionInteresting exceptionInteresting, Boolean terminating)
   at Microsoft.Exchange.Cluster.Replay.Watson.SendReportOnUnhandledException(Action action)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.&lt;&gt;c__DisplayClass2.&lt;OnStart&gt;b__0()
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.SendWatsonReportOnTimeout(String caller, TimeSpan timeout, TimerCallback timeoutHandler, UnderTimeoutDelegate underTimeoutDelegate)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.OnStart(String[] args)
   at Microsoft.Exchange.Cluster.Replay.ReplayServiceBase.ServiceQueuedMainCallback(Object state)</Data>
  </EventData>
</Event>
Dominik ProchazkaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tej Pratap Shukla ~DexterServer AdministratorCommented:
Hi
Check this link for solution to the error MS Exchange Replication Service Can't Start.
https://technet.microsoft.com/en-us/library/ff360684(v=exchg.140).aspx
https://technet.microsoft.com/en-us/library/bb217421(v=exchg.80).aspx
0
Adam BrownSr Solutions ArchitectCommented:
run this:

get-mailboxdatabasecopystatus <database name>

Open in new window


https://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx has a list of possible errors and what can cause them. Most likely your replication broke during the update and either needs to be re-seeded or the local copy of the database needs to be brought up to date.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Adam BrownSr Solutions ArchitectCommented:
The first response to this question is a link with instructions on how to start the replication service. This is not useful information when the replication service is incapable of being started. The most common cause of replication service failure is Database replication failure. Get-databasecopystatus in powershell will display database replication and give information on what the nature of the failure is. In addition, the link provided will assist in tracking down the problem. Without additional information and response from the user who posted the question, however, it is not possible to determine if this information has been used to resolve the error. Thus, full points should not be awarded.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.