Ok, this is an interesting edge case, that takes a bit of work to
trigger, but is pretty funny if you get there.

If you are using Designer 4.02 AU4 that supports the new feature
of two new policy sets for Startup and Shutdown and you never do the
Properties of the IDVault, Server tab, edit the server, click the get
current status, it seems like it will assume it is a engine, and
thus supports the new policy sets.

It will then allow you to deploy settings using those values.

But the engine is NOT amused, and you get this error:

DirXML Log Event -------------------
Driver: \FDU-IDV\fdu\idm\DriverSet\Active Directory Driver
Status: Error
Message: Code(-9010) An exception occurred:
java.lang.ArrayIndexOutOfBoundsException: 15
com.novell.nds.dirxml.engine.ConfigAbstraction.loa dPolicyList(ConfigAbstraction.java:4281)
com.novell.nds.dirxml.engine.ConfigAbstraction.get PolicyList(ConfigAbstraction.java:4248)
com.novell.nds.dirxml.engine.Driver.initializeScri pting(Driver.java:1828)
at com.novell.nds.dirxml.engine.Driver.startShim(Driv er.java:1363)
at com.novell.nds.dirxml.engine.Driver.initialize(Dri ver.java:264)
at com.novell.nds.dirxml.engine.Driver.<init>(Driver. java:236)
com.novell.nds.dirxml.engine.DriverEntry.run(Drive rEntry.java:551)
at java.lang.Thread.run(Unknown Source)

java.lang.ArrayIndexOutOfBoundsException: 15

15? Why 15? Well, it turns out that the Startup and shutdown policy
sets got the numbers 15 and 16.

Check out:

Turns out DirXML-Policies is a Typed Name attr, which means a DN, then
two integers. (Of course the DN is really an integer under the covers).

The DN is the object to be linked. One of the integers is the numerical
value of the policy set. The second integer is its ordering within the
policy set.

Currently the defined values for the policy set are (from that article):
0 Schema Map
1 Input Transform
2 Output Transform
3 ECMA Script Object
4 Sub Event Transform
5 Pub Event Transform
6 Sub Match
7 Pub Match
8 Sub Create
9 Pub Create
10 Sub Command Transform
11 Pub Command Transform
12 Sub Placement
13 Pub Placement
14 GCV Objects

So that is why 15 is out of bounds.

So this is a pretty funny error, that you have to work pretty hard to
get into...

Now it turns out, I had a package that used these policy sets I was
playing with, and then I triggered the real bug.

I removed the package with the linkages but I had first clicked the
Version update button and now Designer knew this was a 4.0.2 patch 0
system, and just removing the package and deploying did not update the
DirXML-Policies to remove the incorrect values (actually the removed

And then there is no way to fix it in Designer. Because you cannot tell
Designer the IDM version is and it appears they nicely filtered
the option to manage the 15/16 options if the vault is anything less.

(If you need to fix it, use an LDAP browser and edit the DirXML-Policies
attribute, and kill all references that have 15 or 16 in them).

But kind of a funny bug, that takes a fair bit of work to trigger.