This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 45%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Hi all
I am trying to migrate a file server running Windows Server 2008 R2 Standard SP1 fully updated until 01-2020 ( NO Extended support) to a server running Windows Server 2019 Standard.
Installed and fully updated Windows Admin Center and all required modules.
The target server is used as the orchestrator also.
Everything goes smooth when running the wizard, but on the last step where the last validation before the transfer starts I get and error
Fail: Error HRESULT E_FAIL has been returned from a call to a COM component.
The destination exists.
Pass
The destination server isn't the same server as the source.
Pass
The SMB connection works.
Pass
We can use the credential provided.
Pass
The credential has administrative privileges.
Pass
The destination proxy is registered.
Pass
Backup privileges can be enabled for these credentials.
Pass
The destination is unique.
Pass
The source and destination computers are supported for transfer.
Pass
The destination server has at least two CPU cores.
Pass
Volume D: - The source volume exists.
Pass
Volume D: - The destination volume exists.
Pass
Volume D: - The destination volume is unique.
Pass
Volume D: - The file systems are supported.
Pass
Volume D: - The file systems match.
Pass
Volume D: - There is enough free space on the destination volume.
Pass
Windows Admin Center Version 2009 Build 1.2.2009.21002
Windows Storage Migration Service Version 1.114.0
Any ideas how to bypass/fix/what the hell this error means????
Thanks in advance for the help.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 34%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
I have just built a test infrastructure pretty much the same as you're describing above. I'm trying to migrate a 2008R2 file server to a 2019 server and I am getting the same error you have above. I have a purpose built Orchestrator server along with a purpose built Windows Admin Server. All running latest updates. WAC ver 2009 Build 1.2.2009.21002 and the SMS extension 1.114.0.
Whilst looking I have come across the following :-
It was posted yesterday and says there will be an update within the next 48 Hours for WAC which should resolve the issue. I guess we will have to wait and see with fingers crossed.
Updated to SMS 1.115, the FAIL message is still there but now you can bypass it.
Tested and working now using the instructions on the article you mentioned.
An other problem that occurred during the cutover to the new server is that it fails to map the network configuration, probably because both server are using DHCP.
The process is now stuck in 72% after moving the shared folders and renaming the source server.
I did not change the cutover time out time which is set by default to 2 days.
Any way to stop the process and not wait 2 days for timeout?
I'm sorry this is the first time I'd actually come to use the Storage Migration Services and was hit by this problem on the first go. I have also just run through my test and it has completed fine re the workaround mentioned above. I guess the only difference is that I was using fixed IP addresses throughout. Even for the rename of the old server I issued a static and manually assigned a new name for it.
I'm not sure but my guess would be just to do a reboot of the Orchestrator server if it won't interfere with anything else. I guess the problem you will be left with is the state of the two servers, source and destination, where did it get too, removal from AD and renaming and all of that. I would suggest that when you go for a retest use static addresses. I'm assuming you are using static in Production too. If not I would say to change that before you plan to migrate.
I was just curious if someone had the same problem but anyhow the test succeeded using static IP addresses so I would call it a success for now.
Do not know if I am going to wait for a solid fix and not a workaround for proceeding with the migration.
Anyway thank you and good luck with your migration.
Hi,
Thanks for your time!
Best Regards,
Anne
-----------------------------
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 51%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EML%3C/text%3E%3C/svg%3E)
I am getting the same error during validation. The source server is a DC and the destination server is not. Source is Win 2012R2 and destination is server 2019 standard.
Hi there and thanks for the response.
11/12/2020-11:13:58.770 [Erro] GetTransferDeviceState request failed for job=test 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]
11/12/2020-11:13:58.772 [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
11/12/2020-11:13:58.775 [Erro] GetCutoverDeviceState request failed for job=test error=0x902B: ErrorCode: 36907, Cutover configuration not found
at Microsoft.StorageMigration.Service.StorageMigrationService.GetCutoverDeviceState(String jobName, Int32 maxCount, Byte[] nextToken) [d:\os\src\base\dms\service\StorageMigrationService.ICutover.cs::GetCutoverDeviceState::348]
11/12/2020-11:13:58.776 [Erro] ExceptionMessage : (Cutover configuration not found), ExceptionToString: (ErrorCode: 36907, Cutover configuration not found
at Microsoft.StorageMigration.Service.StorageMigrationService.GetCutoverDeviceState(String jobName, Int32 maxCount, Byte[] nextToken)
at SyncInvokeGetCutoverDeviceState(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]