2 Replies Latest reply on Jun 1, 2016 10:33 AM by daveselias

    LDMS 9.6sp2 Portal Manager "Failed to load Packages" Error

    Rookie

      Configuration:

       

      Core Server

                      Virtual Server Hosted on VMware ESXi 5.5.0 build 3568722

      WinSrv 2012R2

                      CPU (8) 2.30 GHz

                      RAM 12Gb

                      VMware tools v.9.0.12 build 1897911

      SQL Server

                      Virtual Server Hosted on VMware ESXi 5.5.0 build 3568722

      WinSrv 2012R2

      SQL Server 2012R2 Ent

                      CPU (4) 2.70GHz

                      RAM 8Gb

                      VMware tools v.9.0.12 build 1897911

      Clients

                      Virtual Workstations on VMware ESXi 5.5.0 build 3568722

      Windows 7 Ent sp1 / Windows 10 Ent

      LDMS Agent version 9.60.3.24

                      Users are not local admins

      Notes

      All machines are currently on domain and on network without firewalls enabled. AV is McAfee agentless.

       

      Issue:

                      Some users when clicking on the Refresh button in the LANDesk Portal Manager they receive a "Failed to load Packages" error. This issue appears to be user specific and not machine specific as it affects any machine the user logs into and performs the same action.


      packageFailed.JPG


      The PolicySync.exe.log file shows this error:

      Run PolicySync.exe

      05/17/2016 09:53:15 INFO  6904:3     RollingLog : LoadLocalPolicyInfo: load local machine

      05/17/2016 09:53:15 INFO  6904:3     RollingLog : LoadLocalPolicyInfo: load user

      05/17/2016 09:53:20 INFO  6904:1     RollingLog : Request: Request policies

      05/17/2016 09:53:25 INFO  6904:1     RollingLog : Request: GetWebResponse ok

      05/17/2016 09:53:25 INFO  6904:1     RollingLog : Request: exception - There is an error in XML document (1, 2027).

      05/17/2016 09:53:25 INFO  6904:1     RollingLog : PolicySync: failed request

      05/17/2016 09:53:25 INFO  6904:1     RollingLog : Exit PolicySync.exe with code -3

       

      The proxyhost log shows these lines:

      2016-05-24 22:38:04(5060-5024) proxyhost.exe:127.0.0.1:56194 - - [24/May/2016:18:38:04 -0500] "HEAD HTTP://mycoreserver/ldlogon/ldappl3.PAZ HTTP/1.1" 200 258 825

      2016-05-24 22:38:07(5060-5024) proxyhost.exe:127.0.0.1:56194 Connection terminated reading request line for socket 4 error code -2

       

      I am able to follow these steps to “force” policies the user/machine are assigned and run

      1.       Open Portal Manager to verify the policies showing

      2.       From the Console verify the taskID for tasks assigned to the user/machine through the Scheduled tasks and diagnostics tool.

      3.       On the client machine in an elevated command prompt execute:

                “%ProgramFiles(x86)%\LANDesk\LDClient\PolicySync.exe /TASKID=#”

      4.       Executing the line above for each task ID where the "#" symbol is.

      5.       Close Portal Manager

      6.       Open Portal Manager

      On reopening of the portal manager the policy tasks display until the next reboot/logoff

       

      This issue started becoming more widespread after an AD consolidation project that flattened out OU structure and significantly increased the number of user objects in each OU. So I did not know if that could have hit the threshold of what the LDMS task LDAP queries were capable of handling.