Storage Migration Service stuck on step 2 "Transfer Data" Start the transfer phase

Spencer 20

Hello, I have a dedicated Orchestrator VM running WAC on windows server 2022 datacenter. I am running into an issue migrating a 2012r2 server to windows server 2022. I have been able to go through all the steps up to step 2. I was able to successfully migrate all of the shares and files and folders aside from 2. Since this is a production server, this is where i stopped, and planned on coming back to do a delta sync on any files or folders that had changed, prior to migration. Now that i am back at the transfer screen, it just sits there stuck on the loading screen and never loads the shares/files/folders to sync. It seems that some updates may have ran that could possibly be the issue here, but looking for some help: Orchestrator WAC: Version (1.5.2312.09001) Orchestrator Storage Migration Service: Version 4.1.0 Source and Destination servers are fully patched Source windows 2012r2 has WinRM service running, and Powershell version 5.1.14409.2001 Error logs on Orchestrator: error=3690 on event ID 5000 (Microsoft-Windows-StorageMigrationService/Debug)

H M 0 Reputation points

2024-02-14T20:29:52.8466667+00:00

Hi, I first installed WAC version 2306 and abled to get to Start Transfer and Transferred the data stage. The issue was to get the Error log to identify what files didn't get transferred. Then in mid Jan, I updated WAC to version 2311. Same issue like you, it just kept spinning "Loading" and never get headache. Just today, I found an old post in 2019 that had the same issue and the solution for not getting "Loading", that he revert back to the older version. (https://techcommunity.microsoft.com/t5/windows-admin-center/storage-migration-service-hangs-on-addin... ) So I did that. I removed 2311 then reinstall 2306 and now I could get to the Transfer page. For the issue downloading Error log, see this: https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues#stor... However, editing sms config file, is not straight forward. You need to take over and hand over to the SYSTEM. Someone put the steps (credit for that guy, but sorry, i lost the link) to do edit the config and add Registry: To work around: 1. Open CMD with Admin. 2. net stop sms 3. takeown /f "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /a && icacls "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /grant Administrators:f 4. edit the %SYSTEMROOT%\SMS\Microsoft.StorageMigration.Service.exe.config file using Notepad.exe to change the "sendTimeout" from its 1-minute default to 10 hours. <bindings>
<netTcpBinding>
<binding name="NetTcpBindingSms"
sendTimeout="10:00:00" 5. reg add HKLM\Software\Microsoft\SMSPowershell /v WcfOperationTimeoutInMinutes /t REG_DWORD /d 60 6. icacls "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /setowner "NT SERVICE\TrustedInstaller" && icacls "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /grant:r Administrators:RX 7. net start sms Hope this helps.

Accepted answer

Net Runner 505 Reputation points

2024-02-10T18:00:17.9633333+00:00

Those kinds of errors usually occur when there is an AV or EDR solution is running on one of the servers. Disabling them is crucial for the process to run flawlessly.

If both servers are virtual machines, it may be quicker to simply re-attach the VHDX/VMDK file that is hosting your data and export/import network shares from/to Windows Registry. This approach takes minutes compared to SMS.

If old server is a physical one there is still an option to do as above virtualizing the existing physical disk using Microsoft Disk2VHD https://aka.ms/disk2vhd or free V2V Converter https://www.starwindsoftware.com/starwind-v2v-converter.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Storage Migration Service stuck on step 2 "Transfer Data" Start the transfer phase

0 additional answers