Forum Discussion
Storage Migration Service Hangs on Adding a Destination
Greetings,
Trying to migrate a file server from a Server 2016 instance to Server 2019 with Server Migration Service (SMS). I can get the inventory to complete (takes about 3 hours). When I move to the "Transfer data" stage, I can enter the credentials without issue. When I click "Next" to "Add a destination device...", the interface hangs while "Loading...." something. The "Include device" toggle is greyed out. (see attached, source server redacted).
I have let this run for about an hour and there was no change.
Source device has a number of shares (+40). The inventoried size is 8.54TB and the inventoried files is 1.91M. Quite a bit.
Configuration:
FS01: Source file server (WIndows 2016)
FS02: Destination file server (Windows 2019). VM with 2 Xeon E5-2620 CPUs, 8GB of RAM.
FS02: Orchestrator server
PC01: WAC (Windows 10 Professional 1809)
I have tried running the work using Edge and Chrome and get the same behavior. Load on FS02 is around 3% and very little RAM is being used.
The SMS debug log is recording the following errors
- "Cutover configuration not found"
- "GetTransferDeviceState request failed"
- "Transfer was not run"
- "GetCutoverDeviceState request failed"
Any insights or suggestions?
10 Replies
ffries_nano I am having the same problem migrating from Server 2008 R2 to Server 2019. I was able to complete a migration on another server running the same OS, but have been stuck at Loading for this new migration. I have tried updating to the latest Windows Management framework on the 2008 R2 computer, tweaking firewall rules and making sure that Windows was up to date.
Have you found a solution yet?
Thanks,
Bob
Hey bobbowlin,
I opened a ticket with Microsoft and they are looking into the problem. They gave an initial indication that this may be part of a known problem with Storage Migration Service, but have not yet confirmed.
Will pass along any insights.
Good luck on your end.
