Driverset Won't Compare or Deploy

[jburns80]

So we're using Designer 4.7.2, but for some reason when running a compare of the driverset, not any particular driver, but the driverset it won't compare, it runs for a few minutes and then times out and stops. Also can't deploy, it does the same thing. We do have about 20 driver on the driverset but I wouldn't think this would cause the driverset to fail to compare or deploy. We have new servers that need the GCV's deployed to them and can't get the driverset to deploy them. Anyone have this issue?

[lhaeger]

jburns80 wrote:

>
> So we're using Designer 4.7.2, but for some reason when running a
> compare of the driverset, not any particular driver, but the driverset
> it won't compare, it runs for a few minutes and then times out and
> stops. Also can't deploy, it does the same thing. We do have about 20
> driver on the driverset but I wouldn't think this would cause the
> driverset to fail to compare or deploy. We have new servers that need
> the GCV's deployed to them and can't get the driverset to deploy them.
> Anyone have this issue?

What do you see at the server side in ndstrace for LDAP? anything interesting
in the workspace log? Temporarily allow cleartext connections and capture a
network trace...

[geoffc]

On 3/19/2019 2:14 PM, jburns80 wrote:
>
> So we're using Designer 4.7.2, but for some reason when running a
> compare of the driverset, not any particular driver, but the driverset
> it won't compare, it runs for a few minutes and then times out and
> stops. Also can't deploy, it does the same thing. We do have about 20
> driver on the driverset but I wouldn't think this would cause the
> driverset to fail to compare or deploy. We have new servers that need
> the GCV's deployed to them and can't get the driverset to deploy them.
> Anyone have this issue?
>

So first off, since working is more important than fixing the underlying
problem at first.

For the driver set GCV's not in a GCV object, right click on the
driverset in Designer, Live, DriverSet configuration, Compare Attributes.

This is faster and just does attrs of the object,not all children.

Then for GCV's that are DirXML-GlobalConfig objects (I.e. From packages)
you can go to each object (child of drievrset ) and Live compare them.

Finally if you have added GCV's, then the linkage is stored in
DirXML-Policies, and you can fix this via LDAP.

cn=GCV,cn=DriverName,cn=Driverset,ou=idm,o=data#X#14

X is the order you want this to appear in the list, starting at 0. 14
is the position in the policy flow, which you can see here:

https://www.netiq.com/communities/cool-solutions/talking-about-dirxml-policies-attributes/