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(105.60000000000001, 47%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
I am currently migrating the date from our old server to the new virtual machine in Azure.
The old server is running on windows server 2008 R2 data center.
The new server is running on windows server 2019 data center.
I am using Storage Migration services provided by the windows admin center.
I have created a job in Storage migration services. It has passed the validation and scanned the whole data onto the server.
after that, I have proceeded with the next step which is transferring the data onto a new server. I have entered the destination credentials and it allows me to select the source and destination drive. I have checked the validation for transferring the data and it passed all the required validations. However, when I click the Start Transfer button, it shows the below errors.
Error message in Transfer Data Section
Couldn't transfer storage to any of the endpoints.
Error message in SMB Details
This endpoint already exists. try skipping this endpoint in the transfer configurations or deleting the endpoint and transferring again.
This is the error message from StorageMigrationService/Admin event Log
Couldn't transfer storage.
State: Failed
Error: 36931
Error Message:
Guidance: Check the detailed error and make sure the transfer requirements are met. The transfer job couldn't transfer any source and destination computers. This could be because the orchestrator computer couldn't reach any source or destination computers, possibly due to a firewall rule, or missing permissions.
This is the error message from StorageMigration-Proxy/Debug event Log
11/30/2020-21:01:27.391 [Erro] Transfer validation failed. ErrorCode: 45057, Endpoint already exists and has different resource path than expected.
at Microsoft.StorageMigration.Proxy.Service.Transfer.TransferOperation.Validate()
at Microsoft.StorageMigration.Proxy.Service.Transfer.TransferRequestHandler.ProcessRequest(FileTransferRequest fileTransferRequest, Guid operationId) [d:\os\src\base\dms\proxy\transfer\transferproxy\TransferRequestHandler.cs::ProcessRequest::126]
I have enabled all the required firewall rules for transferring the data from source to destination.
I have also updated the windows updates onto both the servers.
Can you please look into this matter and let me know how to resolve this error?
It is transferring the data from Folders. However, it is not allowing me to transfer the data from C: drive.
Waiting for your valuable reply.
![](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(60.8, 64%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERN%3C/text%3E%3C/svg%3E)
I was having a similar error while migrating data from Windows 2012 R2 to Windows 2019.
I was using same account for both source and the target, when i used a different account for the target the error was rectified and the data migration started. Hope it may help someone.
Thank you Andrew Mackintosh, after reading your comments i did some research on the transfer configurations part and was able to overcome the error.
Hi,
It seems to be a known issue, please check the following article for detailed information:
Please check if Server 2019 has installed KB4520062.
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.
Hi,
I would like to check if the reply could be of help? If yes, please help accept answer, so that others meet a similar issue can find useful information quickly. If you have any other concerns or questions, please feel free to feedback.
Best Regards,
Anne
Hey @Xiaowei He
Thank you for your reply.
It was not that issue of windows update. I had already updated that before posting it here.
This endpoint already exists. try skipping this endpoint in the transfer configurations or deleting the endpoint and transferring again.
I was thinking about transferring the whole drive's content to a new server on a different drive. However, the drive was already existed on the new server so it didn't allow me to transfer the whole drive's data. I had to select each and every folder from that source drive and then transferred it and then it allowed me to transfer the data.
I hope it helps someone who is facing this kind of issue.
Thanks
Thanks for your feedback.