Quantcast
Channel: Exchange Server 2013 - High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 1985

Add DAG member, Event 4999 MSExchange Common

$
0
0

Hey all

I have a 4 node DAG spread over two sites. I introduce a 5 node, let's call it EX-DR-03, to my second site. Everything fine. I then add 6 node, EX-DR-01, to second site. This causes replication service to fail on 5th node and itself. Databases cannot be mounted (service fail in EAC). I'm seeing multiple Event 4999 MSExchange Common errors caused by MSEXchangeMigrationWorkflow service constantly restarting on EX-DR-01, as below:

Watson report about to be sent for process id: 10340, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, MSExchangeMigrationWorkflow, unknown, M.E.M.L.L.<>c__DisplayClass11.<GetLocalServerData>b__10, System.NullReferenceException, 49af, unknown.

ErrorReportingEnabled: False

This may or may not be relevant, but suspect it could be: EX-DR-01 was previously an Exchange server but I was unsatisfied with the build. I removed Exchange, dropped it off the domain and rebuilt it. The new server now has the same name and IP address.

I really could use some help with this one.

Many thanks!

EDIT: this is an issue with both servers. When added to the dag the replication service terminates unexpectedly:

Watson report about to be sent for process id: 6860, with parameters: E12IIS, c-RTL-AMD64, 15.00.0995.029, msexchangerepl, M.E.Cluster.Replay, M.E.C.R.NetworkDiscovery.ResolveLocalNic, System.NullReferenceException, ee97, 15.00.0995.028.

ErrorReportingEnabled: False



Viewing all articles
Browse latest Browse all 1985

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>