Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Exchange 2013 to Exchange 2016

$
0
0

Hi

I have a exchange 2013 CU 12 environment in to which i am updating to exchange 2016 CU3. The E2016 mailbox roles have been installed correctly and the CAS function is working correctly. The problem I have is with setting up a new DAG for the new servers.

The commands to enable the DAG have run correctly but when looking at the settings in EAC I get the following error.

"Object reference not set to an instance of an object"

and no DAG settings are displayed. I am also unable to add databases to the DAG.

Looking around the net I have found that I need to move the arbitration mailboxes to the new exchange servers to resolve this issue. Which is were i hit my current problem.

I can find the mailboxes but they refuse to be moved and just queued to be processed. Looking deeper I find that although the mailboxes are located in a active mail store the server name attached to them no longer exists.

Name                 Database   ServerName

SystemMailboxab85}  mbx_store2 xxcxxxbrc003

FederatedEmail.4c1f mbx_store2 xxxxxxbrc003

SystemMailbox{      mbx_store2 xxxxxxbrc003

Migration.8f3e7716- mbx_store2 xxxxxxbrc003

SystemMailbox       mbx_store1 xxxxxxbmc002

Server ending 003 is no longer valid, server ending in 002 is. Both databases exists in a DAG.

I am assuming here that the issue is with server 003 no longer being valid although they all refuse to move to a new store.

Anyone have any ideas how i can resolve this?

thank you in advance.


Viewing all articles
Browse latest Browse all 7129

Trending Articles



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