Nov 22 2018 05:33 AM - edited Nov 22 2018 06:41 AM
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?
Dec 12 2018 01:00 PM
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
Dec 19 2018 11:32 AM
File and Printer sharing needs to be allowed through the firewall on the Orchestrator host (Host you are managing in Windows Admin Center).
Feb 11 2019 12:09 PM - edited Feb 11 2019 12:10 PM
Try adjusting the timeout values on the orchestrator server. If you're migrating a lot of data the default value may be to short.
<bindings>
<netTcpBinding>
<binding name="NetTcpBindingSms"
sendTimeout="00:10:00"
Sep 12 2019 11:39 AM
@chatro9314Thanks! Fixed it for me.
Dec 18 2019 05:59 AM
@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
Jul 27 2020 11:59 AM
The only account that has full control is the Trusted Installer for me. So it will not allow me to change the config file.
Nov 18 2020 01:45 PM
Dec 14 2020 06:29 AM
i have this issue. I have just done a transfer of a 1.9 TB drive with just over 2 million files on but have 18 files that have failed and really need to know which ones. I can download the Transfer log/Migrated users log/Migrated groups log but the Error log fails with the error:
Ensure port TCP/445 (SMB File and Print Sharing) is open on the orchestrator server. The error was: [0x8000] Unknown service error.
I have rebooted the Orchestrator server, turned the Windows Defender Firewall off (there is no other firewall), I have increased the NetTcpBindingSms Time out to 10 minutes as others have suggested. But none of these have worked. Please could you help me get the log so I can find what the missing 18 files are.
Also when downloading the Transfer log it doesn't appear to have all 2 million files within, it is only showing the files from one of the shares and not all the shares that have been migrated, how do I download all files log?
Jun 21 2023 08:11 AM
I am having the same issue and have tried to suggested fix. Has anyone found a resolution to this issue? I really need to know which files are failing.
Sep 01 2023 01:56 PM
@Goldleader80 I'm having this same issue. Did you ever find a solution? Thanks.
Sep 02 2023 01:42 PM
Nov 16 2023 06:48 AM
Nov 16 2023 07:06 AM
Feb 11 2024 08:13 AM
How were you able to edit the file? Like you when I switched owners to edit the file once I rebooted it would error out the same as you.
Thanks