Home

Storage Migration Service - Can't open transfer and error logs after migrating data

%3CLINGO-SUB%20id%3D%22lingo-sub-290318%22%20slang%3D%22en-US%22%3EStorage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290318%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EHi%20Community%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAfter%20migrating%20a%20drive%20I'm%20trying%20to%20see%20which%20file%20transfers%20failed%20and%20why%20but%20I'm%20getting%20this%20message%20when%20trying%20to%20open%20either%20the%20transfer%20log%20or%20the%20errors%20only%20log%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ETransfer%20Log%20-%20Please%20check%20file%20sharing%20is%20allowed%20in%20your%20firewall.%20%3A%20This%20request%20operation%20sent%20to%20net.tcp%3A%2F%2Flocalhost%3A28940%2Fsms%2Fservice%2F1%2Ftransfer%20did%20not%20receive%20a%20reply%20within%20the%20configured%20timeout%20(00%3A01%3A00).%20The%20time%20allotted%20to%20this%20operation%20may%20have%20been%20a%20portion%20of%20a%20longer%20timeout.%20This%20may%20be%20because%20the%20service%20is%20still%20processing%20the%20operation%20or%20because%20the%20service%20was%20unable%20to%20send%20a%20reply%20message.%20Please%20consider%20increasing%20the%20operation%20timeout%20(by%20casting%20the%20channel%2Fproxy%20to%20IContextChannel%20and%20setting%20the%20OperationTimeout%20property)%20and%20ensure%20that%20the%20service%20is%20able%20to%20connect%20to%20the%20client.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20destination%20server%20is%20also%20the%20migration%20server%20(just%20migrating%20one%20drive)%20and%20all%20required%20ports%20were%20openend%20automatically%2C%20I've%20also%20double%20checked%20the%20firewall%20on%20the%20source%20server.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAnyone%20have%20any%20ideas%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-334625%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-334625%22%20slang%3D%22en-US%22%3E%3CP%3ETry%20adjusting%20the%20timeout%20values%20on%20the%20orchestrator%20server.%20If%20you're%20migrating%20a%20lot%20of%20data%20the%20default%20value%20may%20be%20to%20short.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3COL%3E%3CLI%3EEdit%20%22C%3A%5CWindows%5CSMS%5CMicrosoft.StorageMigration.Service.exe.config%22%20and%20change%20the%20sendTimeout%20from%201%20to%2010%20minutes.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%3CBINDINGS%3E%3C%2FBINDINGS%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%3CNETTCPBINDING%3E%3C%2FNETTCPBINDING%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%3CBINDING%20name%3D%22%26quot%3BNetTcpBindingSms%26quot%3B%26lt%3B%2FP%22%3E%3C%2FBINDING%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20sendTimeout%3D%2200%3A10%3A00%22%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLI%3E%3CLI%3EAdd%20the%20following%20registry%20key%20to%20change%20the%20WCF%20client%20timeout%20from%201%20to%2010%20minutes%20as%20well.%3CBR%20%2F%3E%3CBR%20%2F%3Ereg%20add%20HKLM%5CSoftware%5CMicrosoft%5CSMSPowershell%20%2Fv%20WcfOperationTimeoutInMinutes%20%2Ft%20REG_DWORD%20%2Fd%2010%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLI%3E%3CLI%3ERestart%20the%20SMS%20services%20on%20the%20orchestrator%20server.%3C%2FLI%3E%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304287%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304287%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EFile%20and%20Printer%20sharing%20needs%20to%20be%20allowed%20through%20the%20firewall%20on%20the%20Orchestrator%20host%20(Host%20you%20are%20managing%20in%20Windows%20Admin%20Center).%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-300932%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-300932%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EIf%20I%20understand%20the%20issue%20correctly%20you%20are%20migrating%20a%20share%20from%20a%20source%20server%20to%20a%20destination%20server%20that%20also%20happens%20to%20the%20machine%20that%20you%20are%20connected%20to%2C%20correct%3F%3C%2FP%3E%3CP%3EYou%20are%20driving%20the%20transfer%20from%20the%20UX%20and%20noticed%20that%20it%20failed.%20Now%20you%20want%20to%20find%20out%20why%20it%20failed%20and%20so%20you%20click%20on%20the%20button%20to%20check%20errors%20and%20that%20gives%20you%20the%20error%20that%20you%20pasted.%20Correct%3F%3C%2FP%3E%3CP%3EIf%20you%20have%20an%20active%20repro%20can%20you%20please%20check%20if%20the%20Storage%20Migration%20Service%20is%20running%20on%20the%20destination%20server%3F%3C%2FP%3E%3CP%3EPlease%20collect%20logs%20as%20per%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fsmslogs%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Fsmslogs%3C%2FA%3E%20and%20send%20them%20to%20smsfeed%40microsoft.com.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-853230%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-853230%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F269946%22%20target%3D%22_blank%22%3E%40chatro9314%3C%2FA%3EThanks!%26nbsp%3B%20Fixed%20it%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1071980%22%20slang%3D%22en-US%22%3ERe%3A%20Storage%20Migration%20Service%20-%20Can't%20open%20transfer%20and%20error%20logs%20after%20migrating%20data%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1071980%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F253526%22%20target%3D%22_blank%22%3E%40Sudhir_AP%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20solution%20worked%20perfectly%20for%20me%2C%20thank%20you!%3CBR%20%2F%3EI%20was%20able%20to%20extract%20the%20error%20logs%20from%20the%20Proxy_Debug.log%20file%20using%20PS%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-python%22%3E%3CCODE%3ESelect-String%20%22Transfer%20error%20for%22%20.%5Chostname_Proxy_Debug.log%20%7C%20Select-Object%20-ExpandProperty%20Line%20%7C%20Out-File%20.%5Chostname_Proxy_Debug_Error.log%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
loenenb
New Contributor

Hi Community,

 

After migrating a drive I'm trying to see which file transfers failed and why but I'm getting this message when trying to open either the transfer log or the errors only log:

 

Transfer Log - Please check file sharing is allowed in your firewall. : This request operation sent to net.tcp://localhost:28940/sms/service/1/transfer did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

 

My destination server is also the migration server (just migrating one drive) and all required ports were openend automatically, I've also double checked the firewall on the source server.

 

Anyone have any ideas?

5 Replies

Hi,

If I understand the issue correctly you are migrating a share from a source server to a destination server that also happens to the machine that you are connected to, correct?

You are driving the transfer from the UX and noticed that it failed. Now you want to find out why it failed and so you click on the button to check errors and that gives you the error that you pasted. Correct?

If you have an active repro can you please check if the Storage Migration Service is running on the destination server?

Please collect logs as per https://aka.ms/smslogs and send them to smsfeed@microsoft.com.

 

Thanks

File and Printer sharing needs to be allowed through the firewall on the Orchestrator host (Host you are managing in Windows Admin Center).

Try adjusting the timeout values on the orchestrator server. If you're migrating a lot of data the default value may be to short.

  1. Edit "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" and change the sendTimeout from 1 to 10 minutes.

         <bindings>

               <netTcpBinding>

                 <binding name="NetTcpBindingSms"

                          sendTimeout="00:10:00"

  2. Add the following registry key to change the WCF client timeout from 1 to 10 minutes as well.

    reg add HKLM\Software\Microsoft\SMSPowershell /v WcfOperationTimeoutInMinutes /t REG_DWORD /d 10

  3. Restart the SMS services on the orchestrator server.

@Sudhir_AP 

This solution worked perfectly for me, thank you!
I was able to extract the error logs from the Proxy_Debug.log file using PS:

Select-String "Transfer error for" .\hostname_Proxy_Debug.log | Select-Object -ExpandProperty Line | Out-File .\hostname_Proxy_Debug_Error.log

 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies