none
Windows Admin Center 1910 / Storage Migration Service Download of error protocol failed RRS feed

  • Question

  • Hi,

    last night, the 1st run of migration from our old fileserver to new one (Srv2019) was finished.

    During run, several errors with different files occured, so we want to download the error protocol, but we can´t.

    The downdoad runs into timeout, within the configured timeout of 1min, the download was not finished, as stated in the log message here:

    Vergewissern Sie sich, dass Port TCP 445 (SMB-Dateifreigabe und -Druckfreigabe) auf dem Orchestratorserver geöffnet ist. (Check, that Port TCP 445 SMB File and Printer Sharing was opened on the orchestrator server)
    Fehler: 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..

    I just want to change the timeout setting as I found a note here:
    https://social.msdn.microsoft.com/Forums/en-US/dc4a6bdc-4dd7-4e68-b24d-cd83a3bfece5/nettcp-operationtimeout-question?forum=wcf
    , but I couldn´t find any config file for Admin Center, where I can put it in.

    Anyone here, who got the same problem or knows about the config files of WAC/SMS?

    Wednesday, January 22, 2020 9:11 AM

Answers

  • Hi ,

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

    This issue is caused by an extremely large number of transferred files that cannot be filtered in the default one minute timeout allowed by Storage Migration Service.

    To work around this issue:

    1.On the orchestrator computer, edit the %SYSTEMROOT%\SMS\Microsoft.StorageMigration.Service.exe.config file using Notepad.exe to change the "sendTimeout" from its 1 minute default to 10 minutes

    <bindings>
       <netTcpBinding>
         <binding name="NetTcpBindingSms"
                  sendTimeout="00:01:00"

    2.Restart the "Storage Migration Service" service on the orchestrator computer.

    3.On the orchestrator computer, start Regedit.exe

    4.Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\SMSPowershell

    5.On the Edit menu, point to New, and then click DWORD Value.

    6.Type "WcfOperationTimeoutInMinutes" for the name of the DWORD, and then press ENTER.

    7.Right-click "WcfOperationTimeoutInMinutes", and then click Modify.

    8.In the Base data box, click "Decimal"

    9.In the Value data box, type "10", and then click OK.

    10.Exit Registry Editor.

    11.Attempt to download the errors-only file again.

    This behavior will be changed in a later release of windows server 2019.

    For more details about this known issue, please refer to the following article:

    Storage Migration Service times out downloading the transfer error CSV

    Best Regards,

    Candy



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Thursday, January 23, 2020 6:00 AM

All replies

  • Hi ,

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

    This issue is caused by an extremely large number of transferred files that cannot be filtered in the default one minute timeout allowed by Storage Migration Service.

    To work around this issue:

    1.On the orchestrator computer, edit the %SYSTEMROOT%\SMS\Microsoft.StorageMigration.Service.exe.config file using Notepad.exe to change the "sendTimeout" from its 1 minute default to 10 minutes

    <bindings>
       <netTcpBinding>
         <binding name="NetTcpBindingSms"
                  sendTimeout="00:01:00"

    2.Restart the "Storage Migration Service" service on the orchestrator computer.

    3.On the orchestrator computer, start Regedit.exe

    4.Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\Software\Microsoft\SMSPowershell

    5.On the Edit menu, point to New, and then click DWORD Value.

    6.Type "WcfOperationTimeoutInMinutes" for the name of the DWORD, and then press ENTER.

    7.Right-click "WcfOperationTimeoutInMinutes", and then click Modify.

    8.In the Base data box, click "Decimal"

    9.In the Value data box, type "10", and then click OK.

    10.Exit Registry Editor.

    11.Attempt to download the errors-only file again.

    This behavior will be changed in a later release of windows server 2019.

    For more details about this known issue, please refer to the following article:

    Storage Migration Service times out downloading the transfer error CSV

    Best Regards,

    Candy



    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Thursday, January 23, 2020 6:00 AM
  • Thank you very much, Candy - problem solved, and now, I´ve found this answer also in the "know bugs" list with SMS :)

    Thursday, January 23, 2020 9:04 AM

  • I am glad to hear that your issue was successfully resolved. 

    Have a  nice day!


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com   

    Thursday, January 23, 2020 9:09 AM