Sylinkdrop - return code 14

[Jqx Jqx]

We are moving version 14.xxx SEP clients to new management server. This is being done using sylinkdrop.exe tool to replace sylink.xml file on workstations. 

Commandline: sylinkdrop.exe -silent -p oursupersecretpassword newcommunicationsettings.xml

For some reason when sylinkdrop is executed with this above command line using administrative command prompt on local machine it works without problems. When we deploy exactly the same command line from Configuration Manager to workstations sylinkdrop.exe returns error code 14. Configuration Manager is executing the package and commands from System context on local machine. 

Has anyone seen this issue before? What is that error code 14? There is also no logfiles generated by sylinkdrop.exe?

 

 

[MDubya]

So based on the documentation, there are only a handful of return values for SylinkDrop:

So I'm not sure if it's coming directly from the SylinkDrop utility. That said, I found a posting that referenced an exit code of 14 and SMS: https://social.technet.microsoft.com/Forums/exchange/en-US/2d71b9c6-d140-4334-8e76-e90de9af8403/exit-code-14?forum=configmgrgeneral

I have no idea if this will help, but it's something to look at. Good luck.

-Mike

P.S. Maybe try running the package under user credentials, just to see if you get a different result (make them an admin if you have to for the test). Or, if you open an elevated command prompt as the Local System account and run it manually, do you still get a success? Local System can behave differently than a local admin. Verify the SCCM settings...is running interactive checked...uncheck it. Just shots in the dark in case something helps.

[Jqx Jqx]

I was able to debug it. It's not related to system context. Just remove the silent parameter and it's displaying the error: Error (3) in smc -importSylink. This will give us return code 14 but I'm not sure why it's not working.

[Jqx Jqx]

This gets very interesting and I really cant understand what is wrong with sylinkdrop. If I copy the xml file to different folder than where the main sylinkdrop.exe is located it works and no more gives return code 14 aka (Error (3) in smc -importSylink). 

 

This won't work (return code 14)

C:\Windows\Temp\sylinkdrop.exe -silent -p oursupersecretpassword C:\Windows\Temp\newcommunicationsettings.xml

This works:

C:\Windows\Temp\sylinkdrop.exe -silent -p oursupersecretpassword C:\SomeFolder\newcommunicationsettings.xml

 

[jdptech]

This gets very interesting and I really cant understand what is wrong with sylinkdrop. If I copy the xml file to different folder than where the main sylinkdrop.exe is located it works and no more gives return code 14 aka (Error (3) in smc -importSylink). 

This won't work (return code 14)

C:\Windows\Temp\sylinkdrop.exe -silent -p oursupersecretpassword C:\Windows\Temp\newcommunicationsettings.xml

This works:

C:\Windows\Temp\sylinkdrop.exe -silent -p oursupersecretpassword C:\SomeFolder\newcommunicationsettings.xml

 

I am seeing the same thing.  I have been banging my head against my desk for hours on this one.  Thanks for the clue.  I wish Symantec didn't have to make it so hard on us with these undocumented "features".