Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1015945%22%20slang%3D%22en-US%22%3EFix%20for%20the%20Storage%20Migration%20Service%20%22Couldn't%20transfer%20storage%20on%20any%20of%20the%20endpoints%22%20issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015945%22%20slang%3D%22en-US%22%3E%3CP%3EHeya%20folks%2C%20%3CA%20href%3D%22https%3A%2F%2Ftwitter.com%2Fnerdpyle%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ENed%3C%2FA%3E%20here%20again.%20For%20those%20of%20you%20seeing%20this%20issue%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fstorage%2Fstorage-migration-service%2Fknown-issues%23error-couldnt-transfer-storage-on-any-of-the-endpoints-and-check-if-the-source-device-is-online---we-couldnt-access-it%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fstorage%2Fstorage-migration-service%2Fknown-issues%23error-couldnt-transfer-storage-on-any-of-the-endpoints-and-check-if-the-source-device-is-online---we-couldnt-access-it%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWith%20an%20error%20in%20WAC%20like%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CEM%3E%22Couldn't%20transfer%20storage%20on%20any%20of%20the%20endpoints.%200x9044%22%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20detailed%20error%20in%20WAC%20like%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CEM%3E%22Check%20if%20the%20source%20device%20is%20online%20-%20we%20couldn't%20access%20it.%22%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20an%20event%20log%20entry%20like%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CEM%3E%22Error%20ID%3A%26nbsp%3B36931%26nbsp%3B%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CEM%3ECouldn't%20transfer%20storage.%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20style%3D%22padding-left%3A%2030px%3B%22%3E%3CEM%3EGuidance%3A%20Check%20the%20detailed%20error%20and%20make%20sure%20the%20transfer%20requirements%20are%20met.%20The%20transfer%20job%20couldn't%20transfer%20any%20source%20and%20destination%20computers.%20This%20could%20be%20because%20the%20orchestrator%20computer%20couldn't%20reach%20any%20source%20or%20destination%20computers%2C%20possibly%20due%20to%20a%20firewall%20rule%2C%20or%20missing%20permissions.%22%3C%2FEM%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20fixed%20it%20in%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fhelp%2F4520062%2Fwindows-10-update-kb4520062%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3ECumulative%20Update%20KB4520062%3C%2FA%3E.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ESo...%20there%20you%20go.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-%20Ned%20Pyle%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1015945%22%20slang%3D%22en-US%22%3E%3CP%3ESMS%20error%26nbsp%3B%3CEM%3E%22Couldn't%20transfer%20storage%20on%20any%20of%20the%20endpoints.%200x9044%22%20%3C%2FEM%3Efixed%20in%26nbsp%3BKB4520062.%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

Heya folks, Ned here again. For those of you seeing this issue:

 

https://docs.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues#error...

 

With an error in WAC like: 

 

"Couldn't transfer storage on any of the endpoints. 0x9044"

 

And detailed error in WAC like: 

 

"Check if the source device is online - we couldn't access it."

 

And an event log entry like:

 

"Error ID: 36931 

Couldn't transfer storage.

 

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."

 

We fixed it in Cumulative Update KB4520062.

 

So... there you go.

 

- Ned Pyle