Saturday 5 April 2014

Getting error code 1017 Lync Server Central Management Store replication failures

If you are getting the error code 1017 Lync Server Central Management Store replication failures in windows based computer then you think how to remove windows error 1017. You will get the easiest process to fix error code 1017 in your computer. The error message occurs when CMS file replication between Lync Server front end servers. You will receive the following error message.

Log Name:   Lync Server
Source:        LS File Transfer Agent Service
Date:          dd/mm/yyyy hh:mm:ss AM|PM
Event ID:      1017
Task Category: (1121)
Level:         Error
Keywords:  Classic
User:          N/A
Computer:      server01.contoso.net
Description:
File transfer failed for some replica machines. Microsoft Lync Server, 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: sever05.contoso.com: Https destination unavailable.
Cause: Possible issues with transferring files to the replicas listed above.

Resolution: Check the accessibility of file shares or https web services listed above.


Some cause of getting error code 1017

When the internal firewall that is for the perimeter network is host the lync server. The edge server pool is not able to allow or not configured for the transferring by using outgoing TCP port 4433.





Process to fix error code 1017


If you want to remove windows error code 1017 then you have to apply the given steps in your computer. The process to fix error code 1017 is given step by step in the below paragraph.


  • First of all open the Lync Server Management Shell and then type the following Lync Server PowerShell cmdlet

Get-CsManagementStoreReplicationStatus –CentralManagementStoreStatus

  • Now see the result of the Get-CsManagementStoreReplicationStatus PowerShell cmdlet.
  • Now type again the following command in the Lync Server PowerShell cmdlet.
Invoke-CsManagementStoreReplication

  • Again type the above command that is:
Get-CsManagementStoreReplicationStatus –CentralManagementStoreStatus

  • Again see the result of Get-CsManagementStoreReplicationStatus PowerShell cmdlet.

Now troubleshoot the TCP port 4433 and you will see the error that is facing by you will be removed. The process that is given above is lengthy so you can also use third party tool to fix this issue. I fix my pc from this error via third party tool. This is the perfect choice by me and now my pc working very well without generating any error. you may also get so many features from this tool to keep safe your pc.


No comments:

Post a Comment