Feb 03 2024 01:18 AM
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 Error 36890 and gets stuck at loading once I reach the start the transfer stage (more details below)
Source Server is 2008 R2 and Destination is Server 2022 Standard, Current server is a DC but my understanding is I will need to demote before we start the cutover? (I did also remove AD and it didnt make any difference, so have restored AD/DC as I had to abort the migration)
Thanks in advance
02/03/2024-09:10:21.994 [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::2187]
02/03/2024-09:10:21.995 [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]
Feb 06 2024 12:24 PM
@Whytey88 I have the same problem. Last week (Jan 31) I successfully migrated a 2008R2 file server. This week, I can't transfer any data between servers--not even for jobs that existed before this problem started. It all seems to work normally until I get to the Transfer Data > Start the Transfer page. At that point, I just get a loading message and the spinning dots.
Feb 06 2024 02:10 PM
Im glad its not just me having not used it before i assumed it was just me.
Ive tried recreating job and even try the process from a completely new server acting as a orchestra and still same.
Hopefully its something that can be patched?
Feb 06 2024 04:18 PM
Feb 07 2024 02:20 AM
Well that makes three of us, like you i have done some prep then testing and was ready to go.
I can only hope its sonething they patch soon otherwise im going to have to manual migrate
Feb 07 2024 02:43 AM
SolutionFeb 07 2024 04:35 AM
Feb 07 2024 06:52 AM
Feb 07 2024 08:24 AM
Feb 12 2024 07:03 AM
I shortcut this a bit. You can go into Settings > Extensions and uninstall the SMS extension. Then, when the screen comes back, install the old version that came during install (2.4.4 I think). It save all of my existing jobs and is running as it should now.
And thank you for this workaround. It was a huge help!
Feb 12 2024 07:14 AM
Feb 13 2024 10:42 PM - edited Feb 13 2024 10:43 PM
Hi @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
Feb 15 2024 09:21 AM
Feb 19 2024 06:56 AM
@JeremyShupick Sorry for the delay, in my case I have around 600GB and its pretty much instant.
I certainly wouldn't expect it to take anymore than a few minutes, I left it originally running for 30mins and thought something was wrong 6 hours later I realised it wasn't right so logged this issue!
Feb 26 2024 02:14 AM
Feb 26 2024 05:59 AM - edited Feb 26 2024 05:59 AM
@Whytey88 Thanks, I was able to downgrade to a previous version and was successful in getting the migrated over to the new server.
Feb 26 2024 06:25 AM
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
Feb 28 2024 10:45 PM
Mar 11 2024 12:09 AM
Feb 07 2024 02:43 AM
Solution