On Windows, the updateschema.pl script in Access Manager 7.1 patch 3 and later requires the version 4.21 or later ldapjdk.jar file. In some old ldapjdk.jar files, the version is not even defined in the META-INF/MANIFEST.MF file. If the LDAP JDK version is older than 4.21 or not defined, the updateschema.pl script exits with an error.
Workaround. Download and install the latest LDAP JDK patch, as described in Sun Java System LDAP JDK Patches.
If Access Manager 7.1 patch 4 is deployed from a WAR file, the updateschema script cannot run successfully for the following reasons:
On Solaris systems, the -B option is not available for the version of the ldapsearch utility that is called by the updateschema.sh script.
On Linux systems, the -Z option is not available for the version of the ldapsearch utility that is called by the updateschema.sh script.
On Windows, if you are running the updateschema.pl script, you cannot specify that the Directory Server is SSL enabled.
On Solaris or Linux systems, edit the updateschema.sh script and change the path for the ldapsearch utility to point to a version that supports the -B and -Z options. You might need to download a version of ldapsearch that supports these options. Then, rerun the updateschema.sh script.
On Windows, enable non-SSL access to Directory Server and rerun the updateschema.pl script.