none
Issues migrating some users RRS feed

  • Question

  • Hi,

    I am having a strange issue that I am not sure why it is happening and any information as to why would be greatly appreciated, My environment is a 3 DC network with a 3 way 2013 (CU22) dag and the new Exchange 2019 (CU2).

    Error 1:

    Migration rate:
    Error: MigrationTransientException: An error caused a change in the current set of domain controllers. --> An error caused a change in the current set of domain controllers.

    Error 2:

    Migration rate:
    Error: MigrationTransientException: Failed to reconnect to Active Directory server dc1.domain.local Make sure the server is available, and that you have used the correct credentials. --> Failed to reconnect to Active Directory server dc1.domain.local. Make sure the server is available, and that you have used the correct credentials. --> Active Directory server dc1.domain.local is not available. Please retry at a later time.

    I am able connect from all all the DC's from all the Exchange servers, without issues so I don't know what to look for?
    The strange issue is that this has not affected all my users just some?

    Thanks in advance,
    Gareth Vorster

    Saturday, September 21, 2019 11:19 AM

All replies

  • Hi

    Is this using the migration batch in Exchange 2019 or doing a simple move with PowerShell? sometimes a reboot of exchange servers fixes issues. Error states it has lost access to the domain controller DC1


    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Sunday, September 22, 2019 6:41 PM
    Moderator
  • Hi GVorster,

    I find some similar error information as you provided above for your reference:

    Weird issue with exchange 2010 and domain controllers

    Cross Forest 2010 - 2013: Failed to reconnect to Active Directory server

    Failed to resolve the linked master account

    In addition, have you checked the event viewer to see whether there is any related error log?

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Monday, September 23, 2019 6:53 AM
  • Hi Edward,

    I will try reboot the server angain, hever I dont seem to be having this issue on any of the 2013 servers only the 2019 Exchange. What is stranger is that it only seems to be affecting certain mailboxes on different servers in the DAG?

    I will get back to you in regards to if this has helped when I can reboot this server, I will try late tonight.

    Kind regards,
    Gareth Vorster

    Monday, September 23, 2019 8:03 AM
  • Hi Joyce,

    These dont seem to be the same, as I am running these servers on the same network segment and VLAN and need any federated trusts.

    Thank you for this info though I will see if there is possbile anything there that can help me slim this down a bit.

    Kind regards,
    Gareth Vorster

    Monday, September 23, 2019 8:07 AM
  • Hi GVorster,

    Is there any update about your issue?

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Wednesday, September 25, 2019 7:28 AM
  • Hi Joyce,

    It seems the restart has not helped my issue, I am still getting the error?
    I have managed to move a few more users however this is going very slowly and is trial and error on who can be moved.

    Kind regards,
    Gareth Vorster

    Wednesday, September 25, 2019 7:41 AM
  • Hi GVorster,

    What commands did you run on which server?

    Have you checked the event viewer to get any related error logs?

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 27, 2019 7:01 AM
  • Hi Joyce,

    I'm running the migrations through the EAC, I have tried a command that references the DC to be used however this did not work for me.
    I have however found something that seems to be working and it looks like it has something to do with the DB's on the server. Currently I have found that migrating a user to an empty DB on a server on the 2013 DAG and then migrating them again to the 2019 Exchange seems to run without issue.

    If this works for the next few I was having an issue with I will mark this as a semi answer as obviously its not fully right but at least it gets the job done.

    Kind regards,
    Gareth Vorster

    Friday, September 27, 2019 7:07 AM
  • Hi GVorster,

    Thanks for sharing this method.

    In addition, if you have any progress about this issue, post the updates here and if the issue is successfully solved, you can share your solution and mark them or the helpful reply as answer, this will make answer searching in the forum easier and be beneficial to other community members as well.

    Regards,

    Joyce Shen


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Friday, September 27, 2019 9:21 AM
  • Hi GVorster,

    "Error: MigrationTransientException: An error caused a change in the current set of domain controllers. --> An error caused a change in the current set of domain controllers.

    "Error: MigrationTransientException: Failed to reconnect to Active Directory server DC2-W2K19.xxx.com. Make sure the server is available, and that you have used the correct credentials. --> Failed to reconnect to Active Directory server DC2-W2K19.xxx.com. Make sure the server is available, and that you have used the correct credentials. --> Active Directory server DC2-W2K19.xxx.com. is not available. Please retry at a later time."

    I am migrating 2016 to 2019 . Exactly got same error message when i migrating some databases with some users. I have tried your suggestion to first migrate to empty DB and then migrate to 2019 but when i try to migrate an empty DB got same error.

    I know there is no issue on DCs. Checked all variations, dcdiag , dns test etc. All replications working good and there is no error. I dont get it what is that error cause. There are some migration jobs i already have. Waiting to finish these jobs and i will try to restart 2 exchanges and than will try again.

    I think its related to exch 2019 bug maybe.

    Best regards,

    Saturday, October 26, 2019 10:08 AM
  • Run repadmin /options on each DC and post the output

    Mariëtte Knap [alumna Microsoft SBS MVP]
    www.server-essentials.com | Linkedin | Migrations done the easy way | DNN MVP 2019

    Saturday, October 26, 2019 10:54 AM
  • From DC1-W2K19

    Repadmin: running command /options against full DC localhost
    Current DSA Options: IS_GC


    From DC2-W2K19

    Repadmin: running command /options against full DC localhost
    Current DSA Options: IS_GC

    Saturday, October 26, 2019 11:26 AM
  • Hi GVorster,

    "Error: MigrationTransientException: An error caused a change in the current set of domain controllers. --> An error caused a change in the current set of domain controllers.

    "Error: MigrationTransientException: Failed to reconnect to Active Directory server DC2-W2K19.xxx.com. Make sure the server is available, and that you have used the correct credentials. --> Failed to reconnect to Active Directory server DC2-W2K19.xxx.com. Make sure the server is available, and that you have used the correct credentials. --> Active Directory server DC2-W2K19.xxx.com. is not available. Please retry at a later time."

    I am migrating 2016 to 2019 . Exactly got same error message when i migrating some databases with some users. I have tried your suggestion to first migrate to empty DB and then migrate to 2019 but when i try to migrate an empty DB got same error.

    I know there is no issue on DCs. Checked all variations, dcdiag , dns test etc. All replications working good and there is no error. I dont get it what is that error cause. There are some migration jobs i already have. Waiting to finish these jobs and i will try to restart 2 exchanges and than will try again.

    I think its related to exch 2019 bug maybe.

    Best regards,

    I dig into this error and i have found this error on event viewer when i try to start migration jobs;

    Process w3wp.exe (RemotePS) (PID=20016).  Exchange Active Directory Provider lost contact with domain controller DC2-W2K19.xxx.com.  Error was 0x50 (Other) (Additional information: Not enough memory resources are available to process this command.
    Active directory response: 00000008: SysErr: DSID-0205199E, problem 12 (Not enough space), data 0
    ).  Exchange Active Directory Provider will attempt to reconnect with this domain controller when it is reachable. 

    So about this issue there is a thread for known bug on 2019 Domain Controllers.

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/4f14412f-dd81-4b9a-b6b5-aa69100e87d0/intermittent-not-enough-space-errors-when-doing-ldap-queries-against-2019-domain-controller?forum=winservergen




    • Proposed as answer by hsynynrdg Saturday, October 26, 2019 1:08 PM
    • Edited by hsynynrdg Saturday, October 26, 2019 1:09 PM
    Saturday, October 26, 2019 1:07 PM
  • Ok i have updated all my DC with Windows update to latest CU problem is fixed on Exchange move requests.

    You can also try and mark this as resolved.

    Saturday, October 26, 2019 2:15 PM
  • Hi Hsynynrdg,

    What I seemed to find is that it may have been because I have very busy servers. I have 3 2013 servers and 1 2019 server for now. I needed to balance the load between all 3 2013 servers the I would migrate the users that I need onto the quieter of the 3 2013 servers and then I am able to migrate them to the 2019 users without an issue.

    I think in my case it is just because my databases are really busy, to give you an idea, out mail server is around 7Tb of storage.

    I'm glad that you have come right.

    Kind regards,
    Gareth Vorster

    Saturday, October 26, 2019 2:50 PM
  • Hi GVorster,

    You gave me an idea and i have found and fixed my issue. Thank you for your help and i am glad that you have fixed your problem too.

    BTW i have total around 8TB databases too.

    Best regards,

    Huseyin Yanardag



    • Edited by hsynynrdg Sunday, October 27, 2019 11:18 AM
    Sunday, October 27, 2019 11:17 AM