I forgot to note that I made sure that the source server was up-to-date with windows updates and subsequently rebooted the system. I also disabled the firewall to eliminate that as a possible cause, but it still reports the same errors and the transfer never starts. I've allowed the transfer step to continue for a couple hours, thinking there may still be something running the background, but nothing ever happens and there are only 3 informational event 5000 entries after the final two errors. The debug log shows 3 entries of the errors before the end of the log, which is otherwise just filled with informational entries.
Storage Migration Service fails to start transfer
I am attempting to transfer file shares from a Server 2012 R2 file sharing server to a new Server 2019 server. They are both virtual machines running under VMware. I recently successfully performed this on two other identical systems without issue. I get through all the steps, but when I get to the final transfer step, it never starts. I do find the following errors in the debug log, but I have been unable to find any solution.
Event 5000, Microsoft-Windows-StorageMigrationService
11/09/2021-08:20:31.629 [Erro] GetTransferDeviceState request failed for job=FACSTAFF error=36890: ErrorCode: 36890, Transfer was not run at Microsoft.StorageMigration.Service.StorageMigrationService.GetTransferDeviceState(String jobName, Int32 maxCount, Byte[] nextToken) [d:\os\src\base\dms\service\StorageMigrationService.ITransfer.cs::GetTransferDeviceState::2184]
Event 5000, Microsoft-Windows-StorageMigrationService
11/09/2021-08:20:31.630 [Erro] ExceptionMessage : (Transfer was not run), ExceptionToString: (ErrorCode: 36890, Transfer was not run
at Microsoft.StorageMigration.Service.StorageMigrationService.GetTransferDeviceState(String jobName, Int32 maxCount, Byte[] nextToken)
at SyncInvokeGetTransferDeviceState(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)) [d:\os\src\base\dms\service\ErrorHandlerBehaviorAttribute.cs::HandleError::37]
5 answers
Sort by: Most helpful
-
-
Limitless Technology 39,611 Reputation points
2021-11-09T19:25:07.473+00:00 Hello @G. Shearer
Try to go trough this article and follow the steps to bypass this issue:
Storage Migration Service known issues
Hope this helps with your query!
-----
--If the reply is helpful, please Upvote and Accept as answer-- -
G. Shearer 1 Reputation point
2021-11-10T15:00:42.033+00:00 Thank you for your response. The link you provided is one of the first results of a simple search and was not helpful.
-
Marcel Fistarol 1 Reputation point
2021-11-24T15:57:38.703+00:00 I faced the same issue.
Fix:
-> update the "Windows Server Storage Migration Service Extension" to Version 2.6.1 on Windows Admin Center.
Settings / Extensions / Available Extensions /
Hope this helps
-
Net Runner 610 Reputation points
2024-02-06T09:51:21.1733333+00:00 Since both servers are virtual machines, why don't you re-attach the VMDK disk that hosts your files to the new server and export/import network shares?
Unlike the Storage Migration Service, which must copy all the data, the above approach takes only several minutes.