locked
File transfer failed for some replica machines. RRS feed

  • Question

  • Hi everyone,

    I' have started seeing an error in event viewer in Skype for business server. Tried troubleshoot it, but havent found a solution and your assitance may be very helpful.


    File transfer failed for some replica machines. Skype for Business Server 2015, File Transfer Agent will continuously attempt to replicate to these machines.

    While this condition persists, configuration changes will not be delivered to these replica machines.
    Replica file transfer failures:
    EdgeServer2.domain.com: 
    First Observed: 1/1/0001 1:00:00 AM Details: 
    EdgeServer2.domain.com: Invalid Path. (working\fta\to-master)
    First Observed: 5/25/2018 10:39:52 PM Details: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Windows\system32\working\fta\to-master'.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileSystemEnumerableIterator`1.CommonInit()
       at System.IO.Directory.GetFiles(String path)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.DeleteFiles(String dirPath)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.ExecuteImpl()
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.Execute()
       at Microsoft.Rtc.Xds.Replication.Common.TaskManager`1.ExecuteTask(Object state)

    EdgeServer2.domain.com: Https destination unavailable.
    First Observed: 6/16/2018 6:40:24 PM Details: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://edgeserver2.domain.com:4443/ReplicationWebService that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 111.111.111.111:4443
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       --- End of inner exception stack trace ---

    Server stack trace: 
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
       at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)
       at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Rtc.Xds.Replication.Common.IReplicationWebService.DownloadFiles(String senderFqdn, String sourceDirPath, String tempDirPath)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.CopyFilesFromReplicaUsingWcf(String fromDir, String tmpDir, String toDir)
    System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 111.111.111.111:4443
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
       at System.Net.HttpWebRequest.GetRequestStream()
       at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()
    System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 111.111.111.111:4443
       at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

    Dependent Machines: ALL : EdgeServer2.domain.com;
    Cause: Possible issues with transferring files to the replicas listed above.
    Resolution:
    Check the accessibility of file shares or https web services listed above.

    When I run Get-CSManagementStoreReplicationStatus, all the replicas are up to date and replication seems to be working fine, however errors in the event viewer keep appearing.

    I have run CLS logging tool to capture XDS replication information, but I receive the same information as in the event viewer:

    TL_ERROR(TF_COMPONENT) [SkypePool\FrontEndServer]4470.10BFC::07/04/2018-12:49:09.282.006CE262 (XDS_File_Transfer_Agent,FileTransferTask.IsUnhandledException:filetransfertask.cs(901)) 
    (00000000007730E6)Unexpected error occured: [System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Windows\system32\working\fta\to-master'.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.FileSystemEnumerableIterator`1.CommonInit()
       at System.IO.Directory.GetFiles(String path)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.DeleteFiles(String dirPath)]

    Basically XDS logging and event viewer says:

    Could not find a part of the path 'C:\Windows\system32\working\fta\to-master'.

    But this location does not exist on any of the servers? How it is setup and why the event viewer started generating logs like 2 months ago, we did not change anything anything regards FileShares, Topology. I thought that Skype should look for folder RTCReplicaRoot which is specified in the registries HKLM\Systeam\CurrentControlSet\Services\Replica

    Wednesday, July 4, 2018 1:45 PM

All replies

  • Hi Maluks,

    First of all , please run the Get-CsManagementStoreReplicationStatus in SFB shell,if edge server's replication status was showing as False,if so please run Invoke-CsManagementStoreReplication -ReplicaFQDN servername

    Could you reach the edge server's replication web service URL(https://edgeserver2.domain.com:4443/ReplicationWebService) via port 4443 as described in the event log?

    If so ,we can remove the firewall issue or an issue with the web service.

    Do you install all the servers in Hyper-V and running windows 2012 R2?

    If so ,please check you install the 4072650 for all you VMs,if you not install it for all your VMs,it will create this issue.


    Best Regards,
    Leon Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, July 5, 2018 6:00 AM
  • Hi,

     

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.


    Best Regards,
    Leon Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, July 6, 2018 8:37 AM
  • When I run Get-CsManagementStoreReplicationStatus, I get status that all servers are up to date, even though errors are continuing to flow in the event viewer.

    I am able to access  web page - https://edgeserver2.domain.com:4443/ReplicationWebService

    What I don't understand is why edge server is refusing the connection as stated in the event.

    "No connection could be made because the target machine actively refused it 111.111.111.111:4443"

    Monday, July 9, 2018 1:05 PM
  • Hi ,

    Based on your error message in the log,I find a similar error in other case ,they have a gateway in your topology, then Uninstalled and reinstalled the gateway using the recovery key solve their issue.If you have a gateway ,please try it.


    Best Regards,
    Leon Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Wednesday, July 11, 2018 11:23 AM
  • Hi,

     

    Are there any update for this issue, if the reply is helpful to you, please try to mark it as an answer, it will help others who has similar issue.


    Best Regards,
    Leon Lu


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


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Monday, July 23, 2018 7:03 AM
  • Unfortunately, I do not know what happened, but after system maintenance issue disappeared by itself.
    Monday, August 6, 2018 4:16 PM