After Upgrade washington to xanadu - MID Server down - how to resolve?

[Baskarank]

After Upgrade washingtondc to xanadu in non production instance  then MID Server down and i have 2 unresolved issue 

Issue:

------

1.MID Server failed to upgrade

2.User mid_acc_rdev associated with down MID Server: 17... No login attempts within reporting period.

[Mark Manders]

What did the logs say (agent log)?

What happened when you tried to trigger the upgrade manually?

Is the user active/existing (cloning could do some damage on this part)?