Storage Migration Service transfer fails with Exception of type 'System.Exception' was thrown.

EvanMc 96 Reputation points
2020-10-08T21:02:13.443+00:00

Using Storage Migration Service through WAC to migrate shares from a fully patched 2008R2 server to a 2019 server. I've confirmed all settings here: https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/migrate-data; and reviewed Known Issues here: https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues.

WAC is running on a third 2019 server. SMS running on the destination 2019 server (it was the only way to get the validation step to recognize the proxy).

All steps now work reliably through "Validate Devices", but the transfer fails repeatedly around 36% having processed ~330,000 of ~1M files (252 failed files).
31111-smsfail.png

Hoping to get Ned Pyle's attention... @Ned Pyle [MSFT]

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,458 questions
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.
631 questions
Windows Server Migration
Windows Server Migration
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Migration: The process of making existing applications and data work on a different computer or operating system.
408 questions
Accepted answer
  1. EvanMc 96 Reputation points
    2020-10-09T16:15:50.81+00:00

    Thank you for the reply. Were you able to resolve the SYS path issue in SMS, or did you have to resort to a different option for copying the files?

    I still have a lot of log files to sift through, but from the "SMB detail" in the screenshot, the majority of the missing files are located on the 2008R2 server here: D:\Shared\Users, which can be read by my Domain Admin account as \SERVER2008\d$\Shared\Users.

    I did have to set "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy" on the 2008R2 and 2019 servers. Otherwise UAC was blocking access, even though my domain Admin account is a member of Domain Admins Global group and Domain Admins is a member of the servers' Local Admins group.

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. EvanMc 96 Reputation points
    2020-10-09T22:50:51.407+00:00

    You are talking about the setting in "Adjust settings" with the description:

    Back up folders on the destination that have the same relative path as folders on the source—files in these destination folders will be overwritten so that the destination is an exact copy of the source. We recommend selecting an initially empty destination, but backing up overwritten files provides a safeguard.

    I read that as, if I uncheck the Backup option, the transfer will overwrite the files Robocopy carefully copied even if the Robocopy version is the better file. That doesn't make much sense no matter how I type it. I guess it boils down to I trust Robocopy's decision making over the Migration Service. I'll have to do some testing.

    I did find Ned Pyle (@Ned Pyle [MSFT] ) hanging out in https://techcommunity.microsoft.com/t5/windows-admin-center/bd-p/WindowsServerManagement late last year, but my Microsoft account can't log in over there.

    0 comments
  2. Barrey Jewall 1 Reputation point
    2020-10-13T20:08:15.44+00:00
    0 comments
  3. EvanMc 96 Reputation points
    2020-10-19T16:40:19.873+00:00

    I ended up using robocopy to transfer the files and set the security, registry export/import to set the shares, and manually change the server names and IPs.

    Not as pretty as WAC and SMS, but my way was successful, and SMS nothing but trouble.

    0 comments