Error messages received when replacing the sylink.xml file
Last Updated April 08, 2019
When attempting to restore communication by replacing the sylink.xml file either through command line, remote communications package push, or when using sylink.exe errors are received.
Little to no detail is provided in these errors to facilitate necessary troubleshooting
Symantec Endpoint Protection (SEP) 11 or later
Error (*) in smc -importSylink
Sylink Error codes are as follows:
Error 0 - Success Error 1 - Invalid Argument Error 2 - Unable to remove backup Sylink Files Error 3 - Unable to copy new Sylink Files / Access Denied Error 4 - Unable to restart Symantec client Error 5 - Unable to backup Sylink files Error 6 - Unable to stop Symantec client Error 7 - Symantec client is not installed Error 8 - Sylink file is Invalid Error 9 - Sylink file is too large Error 10 - Sylink file cannot be opened Error 11 - Sylink file does not exist Error 12 - Error Parsing Sylink drop command XML Error 13 - Error Retrieving Environment Error 14 - Unable to import Sylink file Error 15 - Symantec client must be closed Error 16 - Fail to create window Error 17 - Unknown error
Note: The most common reason for errors when importing the Sylink file is Tamper Protection. Please ensure that Tamper Protection is turned off on the SEP Client shown
If disabling Tamper Protection and importing the Sylink file doesn't resolve your issue, look for the error and see below:
Error 1 - Invalid argument
Review the script used for any errors or misconfiguration
Error 2 - Unable to remove backup Sylink files / Error 5 - Unable to backup Sylink files / Error 15 - Symantec Client must be closed
Usually related to an issue with the sylinkdrop tool. You can work around the issue by manually replacing the Sylink following these steps:
Go to Start > Run
Type smc -stop then click OK. You will notice that Symantec Shield is no longer in your task bar.
Copy the Sylink.XML file and paste that in %Programdata%\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config folder. It will ask you if you want to overwrite or replace the already existing file, Click on Yes.
Go to Start > Run
Type smc -start then click OK.
The client will became managed
Error 3 - Unable to copy new Sylink files / Access Denied