We are running LDMS 8.8 SP2 with the following patches applied: SWD-2025388.2-2 and SWD-2080688.2-2.
We have a couple of hundred Launchpad links that we are sending down to our end users based on their active directory groups. This has worked well on all but a small subset of our PC's. This small subset has a large number of icons for there group. Most of our users get 3-7 icons, but for the people in this group they get 24+ icons.
What we are seeing is now when they go to do a policy sync, either manually or when the schedule kicks it off, we get an error saying that Policy synchronization has encountered a problem and needs to close. We are sorry for the inconvenience. (I added the details of this crash below)
szAppName : policy.sync.exe szAppVer : 220.127.116.11
szModName : policy.sync.exe szModVer : 18.104.22.168 offset : 0002c4a7
We have tried reinstalling the agent on these PC's, deleting and recreating the Database on the pcs, Recreating and re-assigning several of their icons, but it is still crashing.
When I go and un-associate this group from a few of the icons, everything goes back to working. When I put those few icons back, it crashes again. When I pull those few icons off and try a few completely different icons, it still crashes. The only thing that has worked is if I change the association in the task for those few icons from the LDAP query of the group to just a simple LDMS query using PC names, they work fine.
I have been able to reproduce this several times. In fact I am to a point now that if I remove one of my icons, everything works, if I add that 1 icon back...or any other icon, it goes back to crashing.
When looking at the policy.sync.log it seems like it checks in with the core once, doesn't find anything, checks again and then pauses waiting for a response from the core.
I have attached my policy.sync.log file...one thing you will notice is when the sync works you will see a "[START]" and some stuff and then a "[STOP]" but when policy.sync.exe crashes you will see a "[START]" but no stop...just another [START] again when it tries to run a policy sync again.
Does anyone have any ideas about this? I don't know if maybe it is the # of Links, or the Links are corrput, or maybe we have too many policies applied...I am pretty stuck at this point.
I also attached the policy.invoker.log, but that doesn't really point to much.
Any help would be greatly appreciated.