Forum Discussion
Solved
Storage Migration Service Error 36890
Hello Really hoping someone can help, I have found similiar posts but they are much older and usually resolution has been to update Storage Migration Extension (I am using 4.1.0) I am receiving Er...
- I think I have a solution, temporary.
I managed to successfully proceed and transfer files.
I used the old version of the "Storage Migration Service" - v.2.44.0.
To do so:
- Connect to a server where WAC is installed via console (in my case destination server via IPMI);
- Uninstall WAC;
- Download the WAC installer;
- Disable internet access;
- Install WAC;
- Go to WAC settings -> Extensions -> disable
"Automatically update extensions";
- enable Internet;
- Proceed to the migration job.
Maybe this will work for you too, till all we're waiting to fix the issue in the latest version of the Storage Migration Service extension.
Rebecca_Wambua
Microsoft
MicrosoftHi Whytey88, thank you very much for bringing this issue up. I would like to confirm that I have brought this up with the relevant team and that they will be looking into it very soon.
Noisyboy and BaconIsYummy much appreciation for sharing a workaround!
Edit: Adding bug number: 48988802
Any update or response on this from the team?
While the workaround is great would be good to know if 4.9 works or is still to be addresses
- Rebecca_WambuaHi, I believe the fix is in, please update to the latest extension and let me know if the issue is resolved on your end!
- Hi Rebecca, the issue is resolved using version 4.9.0 of the Storage Migration Service extension and also v4.11.0 of the Storage extension. Last week I was able to get past the point where we were having issues and the transfer completed successfully. Unfortunately I then bumped into the known issue of renaming failing to complete at 75%, due to Server 2022 KB5035857, (https://learn.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues#cut-over-of-windows-server-2022-fails-with-error-5-at-computer-rename). But I was able to manually finish off the cut over from that point.
- Rebecca_WambuaHi, yes. They notified me this work is scheduled to begin in the next sprint. I have no ETA and not sure how much time the fix will take, but I'll give a guesstimate of mid-April.
- I have also been experiencing this bug with a 2012 R2 Source Server. I raised my own ticket on the 5th February but have not had any progress so far. I saw that a new extension version 4.9.0 was released, (Friday?). But am yet to have confirmation that it fixes the issue or have yet to try myself with this new extension version.
