Forum Discussion

loenenb's avatar
loenenb
Copper Contributor
Nov 22, 2018

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

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?

17 Replies

Sort By
  • mchltrgn's avatar
    mchltrgn
    Copper Contributor
    Nov 16, 2023
    Good day,

    Same issue here.

    OLD file server : 2008R2
    NEW file server : 2022

    Orchestrator installed on NEW file server.

    Initial data transfert worked fairly well with some errors on files.
    Unable to download ERRORS log. Other logs are fine.

    Collected the logs as described in aka.ms/smslogs. No ERRORS log in the zip generated file.

    Took ownership and modified ACL on file Microsoft.StorageMigration.Service.exe.config and modified registry using command below :

    net stop sms
    - takeown /f "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /a && icacls
    "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /grant Administrators:f
    - reg add HKLM\Software\Microsoft\SMSPowershell /v WcfOperationTimeoutInMinutes /t REG_DWORD /d 60
    - icacls "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /setowner "NT SERVICE\TrustedInstaller" && icacls
    "C:\Windows\SMS\Microsoft.StorageMigration.Service.exe.config" /grant:r Administrators:RX
    - net start sms

    SMS no longer starts with message : The Storage Migration Service service on Local Computer started and then stopped. Some services stop automatically if they are not in use by another services or programs.

    Have not found anything useful in Event Viewer.

    What are my options?

    Thank you.
  • chatro9314's avatar
    chatro9314
    Copper Contributor
    Feb 11, 2019

    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.
  • Brian Nichols's avatar
    Brian Nichols
    Copper Contributor
    Dec 19, 2018

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

  • Sudhir_AP's avatar
    Sudhir_AP
    Icon for Microsoft rankMicrosoft
    Dec 12, 2018

    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

    • Deleted's avatar
      Deleted
      Dec 18, 2019

      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

       

Resources