1 2 Previous Next 18 Replies Latest reply on Feb 10, 2016 6:47 AM by technobabble

    PolicySync.exe fails through CSA

    JSMCPN Expert

      Windows Agents on the internet (9.6 SP1) cannot sync policies through CSA.  Patch, Inventory and Remote Control DO work through the CSA, and if I do a Portal sync BEFORE putting the computer in the Internet, I CAN download and install the listed packages through the CSA.  It is just policy sync that is failing, all else works great.

       

      The Portal Manager quickly throws "Failed to load packages" when clicking the refresh/sync button.  The same computer syncs just fine when connected to the corporate network.

      PolicySync.log:

      Fri, 15 May 2015 09:32:03 GetLdapInfo: ldapwhoami.exe failed - err=1355      << NET HELPMSG 1355 returns "The specified domain controller either does not exist or could not be contacted"

      Fri, 15 May 2015 09:32:03 GetLdapInfo: use cached logon info

      Fri, 15 May 2015 09:32:03 GetLdapInfo: not a valid ldapinfo, return E_FAIL

       

      PolicySync.exe.log:

      05/15/2015 09:32:03 INFO  4188:1RollingLog : Run PolicySync.exe
      05/15/2015 09:32:03 INFO  4188:4RollingLog : LoadLocalPolicyInfo: load local machine
      05/15/2015 09:32:03 INFO  4188:4RollingLog : LoadLocalPolicyInfo: load user
      05/15/2015 09:32:03 INFO  4188:3RollingLog : Request: failed get target info.
      05/15/2015 09:32:03 INFO  4188:1RollingLog : PolicySync: failed request
      05/15/2015 09:32:03 INFO  4188:1RollingLog : Exit PolicySync.exe with code -3

       

      Of course this machine cannot talk to a domain controller when it is off the corporate network, so why is the whole Sync failing just because of an expected condition?

      Also, when I manually run ldapwhoami.exe from a command prompt, it does return data but also a 1355 exit code.  Shouldn't PolicySync be treating 1355 as a SUCCESS instead of FAIL when not connected to corporate network?

        1 2 Previous Next