Storage Migration Service - Config Scan Fails

TSimpsonAZ 6 Reputation points
2021-05-03T18:25:39.763+00:00

I have just started using Storage Migration Service (SMS) from Windows Admin Center and I keep getting an error when I run the inventory scan, which is basically step one.
On one specific Windows 2012R2 server, it always fails the Config Scan when I run the inventory scan. It gives a non specific error of 'System.exception' was thrown. I also consistently get two SMS events of 2503 and 2509. Which basically says that the Orchestrator server can't reach the source server or there is a firewall rule or permission problem.
I don't believe there is any problem with the Orchestrator service communicating with the source server because I can 'see' the other server from it and connect to the shares. I also have disabled the firewall and every non-essential program on the source server with no luck and I'm connecting/using a domain admin account to run the process.

I can successfully run the scan on other similar Windows 2012R2 servers. They are ALL on the same physical, local LAN and run similar apps.

Not sure what else to do as I have tried everything I can think of and every solution I have found on the web doesn't fix the issue.

Windows Server Storage
Windows Server Storage
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Storage: The hardware and software system used to retain data for subsequent retrieval.
622 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Yuhan Deng 3,756 Reputation points Microsoft Vendor
    2021-05-04T02:24:59.71+00:00

    Hi,
    2503 is caused by a code defect in Storage Migration Service when you provide migration credentials in the form of a User Principal Name (UPN), such as 'danny@microsoft.com'. The Storage Migration Service orchestrator service fails to parse this format correctly, which leads to a failure in a domain lookup that was added for cluster migration support in KB4512534 and 19H1.
    To work around this issue, provide credentials in the domain\user format, such as 'Microsoft\danny'.
    2509 is caused by a code defect in the Storage Migration Service. The only workaround currently is to rename the computer to have the same name as the NetBIOS name, then use NETDOM COMPUTERNAME /ADD to add an alternate computer name that contains the longer name that was in use prior to starting Inventory. Storage Migration Service supports migrating alternate computer names.

    For your reference:
    https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues

    Thanks for your time.
    Best regards,
    Danny

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. TSimpsonAZ 6 Reputation points
    2021-05-04T14:12:59.793+00:00

    Thanks for the information but I have seen this already and I don't have that issue at least with 2503. I have always been using domain\username (a domain admin account) but still get the error.

    As for 2509 I have seen that article as well but it just doesn't seem to be true in my case.

    Here's an example of my server name that fails. NetBIOS name: PHXSVR1 Full name: PHXSVR1.company.local Domain: company.local
    Here's a server that works fine with SMS. NetBIOS name: PHXSVRTS1 Full name: PHXSVRTS1.company.local.

    I see no reason why one server gets the error 2509 when the other server doesn't when they use the same name format.

    Am I missing something here?

    0 comments No comments

  3. Yuhan Deng 3,756 Reputation points Microsoft Vendor
    2021-05-05T02:11:54.31+00:00

    Hi,
    This is quite strange.
    I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
    In addition, if the issue has been proved as system flaw, the consulting fee would be refund. You may find phone number for your region accordingly from the link below.
    Global Customer Service phone numbers:
    https://support.microsoft.com/en-us/help/13948/global-customer-service-phone-numbers

    Thanks for your time.
    Best regards,
    Danny

    -----------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.