Make your own free website on Tripod.com



Table A-1    Directory Server Error Codes

Code

Severity

Probable Cause

Action

4104

Error

The server cannot detect a backend to do the import. This is an internal error and should not occur under normal circumstances.

Contact Sun ONE Technical Support.

4105

Error

The backend will not accept wire import. This is an internal error and should not occur under normal circumstances.

Contact Sun ONE Technical Support.

4107

Error

The value of the specified configuration attribute is too large.

Change the value of the specified configuration attribute. See the attribute description in this Reference for the acceptable value range.

4108

Error

The server is unable to obtain any information on the specified configuration file.

Check that the file exists and that it has the appropriate access rights.

4109

Error

The server is unable to open the specified configuration file.

Check that the file exists and that it has the appropriate access rights.

4110

Error

The server is unable to read the specified configuration file.

Check that the file exists and that it has the appropriate access rights.

4111

Error

The mandatory password storage scheme Salted Secure Hashing Algorithm (SSHA) could not be retrieved from the configuration file.

Check that the password storage scheme SSHA exists in the configuration file. If it is not present, add it.

4112

Error

The specified plug-in does not have a valid signature.

Provide a valid signature for the plug-in or disable the plug-in.

4112

Error

An error occurred while loading configuration information for the specified plug-in.

Check that the configuration information for the specified plug-in is accurate. For more information, it may be useful to turn debugging on for SLAPI_DEBUG_PLUGIN. Change the configuration information as required and restart the server.

4119

Error

No encoding scheme was found in the configuration file.

Under normal circumstances, this error will not occur, because the server cannot start if the mandatory scheme SSHA is not present in the configuration file.

Add a password storage scheme plug-in to the configuration file and restart the server.

4120

Error

The tag (algorithm) specified to hash the password is not defined in the configuration file.

Add a password storage scheme to the configuration file, or change the specified scheme, and restart the server.

4121

Error

The tag (algorithm) specified to hash the password is defined but the server is unable to retrieve the associated information.

Check the password storage scheme configuration and its installation and restart the server.

4122

Error

An error occurred reading the configuration files. The specific cause for the error is logged in the log files.

See the log files for more information.

4123

Error

An error occurred reading the dse.ldif configuration file. The specific cause for the error is logged in the log files.

See the log files for more information.

4124

Error

An attempt was made to set an unknown attribute in the configuration file.

Check and correct the attribute name.

4125

Error

The configuration file backup has failed. The reason for the failed backup is provided in the error message.

Correct the error and back up the configuration file manually.

4126

Error

This indicates a resource problem on the machine.

Restart the server.

4127

Error

This indicates a resource problem on the machine.

Restart the server.

4128

Error

An error occurred when attempting to load the specified configuration file.

Check that the configuration file exists and that it has the appropriate access permissions. See the error log for more details.

4129

Error

There is an error in the configuration file. Details of the error are reported in the error log.

Edit the configuration file to correct the reported problems and restart the server.

4130

Error

Several possible causes (file system full, incorrect permissions, etc.). Details of the error are reported in the error log.

Check that the configuration file exists and that it has the appropriate access permissions.

4131

Error

The server cannot read the specified entry. Details of the error are provided in the error message.

Check that the entry is valid and change as necessary.

4132

Error

The server cannot parse the specified entry. There is an error in the LDIF syntax of the entry.

Check that the entry is valid and change as necessary.

4133

Error

System error (file system full, incorrect permissions, etc.)

Check the log file for more information and restart the server.

4134

Error

The server cannot write to the specified DSE file.

Check the specified path and ensure that you have the appropriate write permissions.

4135

Error

The server cannot rename the specified DSE file.

Check the specified path and ensure that you have the appropriate write permissions.

4136

Error

The configuration file contains an invalid value for the specified plug-in.

Check the value in the configuration file and set a valid value.

4137

Error

An attempt was made to delete a child entry for which there was no subcount on the parent.

This error should not occur under normal circumstances.

4138

Error

Plug-in dependencies have not been configured correctly.

Check that the dependencies are valid and that they are enabled.

4139

Error

An error occurred while resolving dependencies (usually the consequence of an earlier problem - disabled plug-in, etc.)

Check that the dependencies are valid and that they are enabled.

4140

Error

This may be due to:

  1. Incorrect configuration of the plug-in entry in the dse.ldif file.

  2. The library is missing or in the wrong location.

  3. The expected symbol corresponding to the init function could not be found in the library.

  1. Check the plug-in configuration in the dse.ldif file.

  2. Check that the library path and the init function name are correct.

4152

Error

A plug-in configuration entry does not have a recognized plug-in type.

Check the configuration and correct the specified plug-in entry.

4153

Error

Multiple plug-ins of the specified type have been defined in the configuration. Only a single plug-in of that type is allowed.

Correct the configuration so that there is only a single plug-in of the specified type.

4158

Error

Invalid unbind PDU. This is an error in the client code.

Correct the error in the client code.

4159

Error

Invalid controls in an unbind PDU. The control is marked as critical and is unknown to the server or the control is badly encoded. This is an error in the client code.

The client should not require critical controls on unbind. Correct the error in the client code.

4162

Error

The server is unable to obtain the subject in the client certificate.

Check the message in the error log for more information.

4163

Error

The server is unable to obtain the certificate issuer of the client certificate.

Check the message in the error log for more information.

4164

Error

An error occurred during the decoding of an attribute value assertion. The format of the attribute value assertion is incorrect.

Check the client application making the request.

4165

Error

The MessageID tag was not found in the LDAP request.

The request is invalid. Check the application that created the request.

4166

Error

An error occurred while decoding the operation tag.

The request is invalid. Check the application that created the request.

4167

Error

An error occurred while loading the dynamic library. This may be because the library does not exist, the library requires another library that does not exist, or the library could not resolve a symbol.

Check that the library exists and is accessible.

4177

Error

The specified lock file could not be opened.

Check that the lock file exists and is accessible.

4178

Error

The specified file could not be opened.

Check that the file exists and is accessible.

4191

Error

The server was unable to change the user and group identity to the specified user.

Check the user privileges and correct.

4612

Error

Unable to start slapd because it is already running.

Stop the running server instance before launching a new server.

4613

Error

Unable to start slapd because a process is currently importing the database.

Stop the running import process instance before launching a new server.

4614

Error

Unable to run db2ldif with the -r flag because the database is being used by another slapd process.

If the other process is not an import process, run db2ldif.pl -r instead. If it is an import process, stop the running import process before launching db2ldif.

4615

Error

Unable to run db2ldif because a process is currently importing the database.

Stop the running import process before launching db2ldif.

4616

Error

Unable to run db2bak because a process is importing the database.

Stop the running import process before launching db2bak.

4617

Error

Unable to import the database because it is being used by another slapd process.

Stop the running slapd process before importing.

4618

Error

Unable to create an index because the database is being used by another slapd process.

Stop the running slapd process before creating indexes.

4623

Error

When trying to convert the absolute path, it was discovered that the pathname is too long.

Change the relative path or the absolute path base so that the sum of their length is lower than the maximum allowed length.

4625

Error

When trying to convert the absolute path, the server was unable to determin the current directory.

Contact Sun ONE Technical Support.

4626

Error

Internal error when converting from a set of modifications to an entry.

Contact Sun ONE Technical Support.

4627

Error

Unable to test the database because it is being used by another slapd process.

Stop the running process and retry.

4629

Error

System error - the directory could not be created.

Check that your file system is valid and retry.

4631

Error

Referrals have been suppressed. The server was unable to obtain the target DN and operation structure.

Contact Sun ONE Technical Support.

4633

Error

No password for the key database has been supplied within the arguments configured for this suffix. The password is required to retrieve the key and proceed with encryption.

Use the -Y pwd or -y pwd-file arguments when executing the ldif2db command.

4634

Error

The security initialisation required by the attribute encryption feature failed.

Make sure that the password supplied is correct and that the password file syntax is correct. Check that SSL has been configured correctly (cert file ciphers.)

4737

Error

Security initialization failed. The server was unable to read the configuration from the specified configuration DN.

Check that the configuration DN is valid and retry.

4738

Error

Security initialization error. The server was unable to retrieve the SSL configuration attribute nscertfile.

Check that the value of the nscertfile attribute is correct and retry.

4739

Error

Security initialization error. The server was unable to retrieve one of the SSL configuration attributes, nscertfile or nskeyfile.

Check that the value of the nscertfile and nskeyfile attributes are correct and retry.

4740

Error

Security initialization error. NSS initialization failed.

Check the NSS configuration and retry.

4741

Error

Security initialization error. NSS initialization failed.

Contact Sun ONE Technical Support.

4742

Error

Security initialization error. The server was unable to retrieve the SSL configuration attribute nssslSessionTimeout.

Check that the value of the nssslSessionTimeout attribute is correct and retry.

4744

Error

Security initialization error. The server was unable to obtain the required token (from the nsssltoken attribute).

Check that the nsssltoken attribute is present in the cipher family entry, and that it has a valid value.

4745

Error

Security initialization error. The server was unable to find the required slot.

Make sure that the security token (external or internal) is accessible to the server.

4746

Error

System error. The server was unable to create a temp directory.

Check that the current user has sufficient access rights to create the temp directory and retry.

4747

Error

Security initialization error. The server was unable to set the SSL export policy.

Contact Sun ONE Technical Support.

4748

Error

Security initialization error. The server was unable to set SSL cipher preference information.

  1. Check the syntax of the ciphers in the configuration.

  2. Make sure that all the ciphers are supported by the server.

4749

Error

Security initialization error. The server was unable to import the NSPR file descriptor into SSL.

Contact Sun ONE Technical Support.

4750

Error

Security initialization error. The server was unable to obtain the internal slot?

Contact Sun ONE Technical Support.

4751

Error

Security initialization error. The server was unable to authenticate.

Contact Sun ONE Technical Support.

4756

Error

The ciphers are invalid.

Check the ciphers and retry.

4757

Error

The configuration of the SSL session cache failed, due to a disk space problem.

Free up some room in the /tmp directory directory and retry.

4758

Error

The configuration of the SSL session cache failed.

Contact Sun ONE Technical Support.

4759

Error

Security initialization error. The server could not enable security on the imported socket.

Contact Sun ONE Technical Support.

4760

Error

Security initialization error. The server could not enable SSLv3 on the imported socket.

Contact Sun ONE Technical Support.

4761

Error

Security initialization error. The server could not enable TLS on the imported socket.

Contact Sun ONE Technical Support.

4766

Error

The encryption alias has not been configured.

Contact Sun ONE Technical Support.

4769

Error

The server was unable to set the SSL client ready for client authentication.

Check that the certificate and key databases are accessible to the server (acting as an SSL client).

4772

Error

SSL client authentication cannot be used because a password has not been defined.

Make sure that the server receives the password for the security token, using a pin.txt file option with the start-slapd command.

4773

Error

SSL error - the server cannot enable client authentication.

Check that the password given to the server is correct.

4774

Error

Simple bind over SSL failed. The password may be incorrect.

Check that the password for the DN is correct.

4775

Error

The bind attempt failed with the SASL EXTERNAL method. The server was unable to find any external credentials.

Make sure that the client's certificate is received by the server before the bind attempt.

4776

Error

SASL error. The details of the error are logged in the error log.

Check the error log for more information.

4779

Error

Security initialization error. The server was unable to create the pin object.

Make sure that the server receives the password for the security token, using a pin.txt file option with the start-slapd command.

4780

Error

Security initialization error. The server was unable to authenticate to the required slot.

The password entered was incorrect. Check the correct password and retry.

4781

Error

The server is configured to allow or require client authentication for SSL. The database contains no CA certificates marked as trusted for issuing client certificates. The server cannot perform SSL client authentication.

Install one or more CA certificates using the console. Ensure that the trust attributes of CA certificates installed with certutil include the T trust attribute.

4782

Error

NSS context creation failed.

Ensure that a valid certificate is available so that the key may be generated.

4785

Error

The server was unable to accomplish the cipher operation.

It is likely that the context is incorrect. Restart the server.

4786

Error

The cryptography mechanism is invalid or unsupported.

Generate a symmetric key for the cryptography mechanism or choose a supported mechanism.

4793

Error

The server was unable to generate the symmetric key.

Check that a security token is available to the server (as a certificate.)

4795

Error

The server was unable to map the key generation mechanism to the cryptography mechanism.

Restart the server.

4796

Error

The server was unable to retrieve a private key from the certificate.

Ensure that the certificate has been imported into the database with both its private and public keys. (This is usually performed as part of the process beginning with a certificate request.)

4797

Error

The signature required for attribute encryption failed.

Restart the server.

4798

Error

The password for the key database has been rejected.

Enter a new password and retry.

4799

Error

The server was unable to find the key database password. No password was provided, or the password syntax was incorrect.

Enter a non-null password or ensure that a valid password file, containing a valid password, is supplied.

4800

Error

No key database password was specified (either explicitly or via a password file.)

Supply a valid password or the path to a valid password file.

4801

Error

The server was unable to read the key database password from the password file.

Check the password file access rights and ensure that the file is of a reasonable size.

4802

Error

The syntax of the password file is incorrect. The ":" is missing.

Supply a password file with the correct syntax.

4803

Error

The token identifier in the password file does not match the open token.

Supply a token identifier that is consistent with the nsSSLToken attribute value in the configuration.

4865

Error

A loop was detected while retrieving the virtual attributes of an entry.

Check the virtual attributes configured for this entry and break the loop.

4866

Error

There is insufficient memory for the server to allocate a service provider for the virtual attributes map insert.

Make more memory available to the server and restart the server.

4867

Error

The server detected a virtual attribute loop when comparing virtual attribute service providers.

Check the virtual attributes configured for this entry and break the loop.

4868

Error

There is insufficient memory for the server to allocate a service provider for the virtual attributes register.

Make more memory available to the server and restart the server.

4869

Error

There is insufficient memory for the server to allocate a service provider handle.

Make more memory available to the server and restart the server.

4870

Error

There is insufficient memory for the server to allocate a map for virtual attributes.

Make more memory available to the server and restart the server.

4871

Error

There is insufficient memory for the server to allocate a new hash table for virtual attributes.

Make more memory available to the server and restart the server.

4872

Error

The server was unable to create a new lock for virtual attribute map creation. This is probably due to a memory error.

Make more memory available to the server and restart the server.

4994

Error

More than one backend instance has been specified for the attempted task.

Contact Sun ONE Technical Support.

4995

Error

You are a version of the backend plug-in API that is no longer supported and cannot perform the database import.

Upgrade to a newer version of the backend plug-in API (at least version 3), recompile, and add the import functionality.

4996

Error

No ldif2db function is defined for this backend. This kind of database is unable to perform an import.

Use a backend that has the import functionality.

4997

Error

The server is unable to allocated a new task for the import. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

4998

Error

The database could not be exported because the specified backend could not be found.

Check the configuration file and make sure that the correct database and suffix are specified.

4999

Error

The db2ldif function failed when attempting to export the database.

See the error log for more information and contact Sun ONE Technical Support.

5000

Error

The database could not be exported because no backend instance names were specified.

Contact Sun ONE Technical Support.

5003

Error

You are a using version of the backend plug-in API that is no longer supported and cannot perform the database import.

Upgrade to a newer version of the backend plug-in API (at least version 3), recompile, and add the import functionality.

5004

Error

No ldif2db function is defined for this backend. This kind of database is unable to perform an import.

Use a backend that has the import functionality.

5005

Error

The server is unable to allocated a new task for the export. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5006

Error

The server is unable to create a thread for the export. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5007

Error

The db2archive function failed when attempting to backup.

See the error log for more information and contact Sun ONE Technical Support.

5008

Error

The database could not be backed up because the db2archive function was not defined.

None - this type of database cannot be backed up.

5009

Error

You are a using version of the backend plug-in API that is no longer supported and cannot perform the database backup.

Upgrade to a newer version of the backend plug-in API (at least version 3), recompile, and add the backup functionality.

5010

Error

The server is unable to allocated a new task for the backup. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5011

Error

The server is unable to create a backup thread. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5012

Error

The restore process failed.

See the error log for more information and contact Sun ONE Technical Support.

5014

Error

You are using a version of the backend plug-in API that is no longer supported and cannot perform the database restore.

Upgrade to a newer version of the backend plug-in API (at least version 3), recompile, and add the restore functionality.

5015

Error

The server is unable to allocated a new task for the restore. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5016

Error

The server is unable to create a restore thread. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5017

Error

The db2index function failed when attempting to restore the database.

See the error log for more information and contact Sun ONE Technical Support.

5019

Error

The database could not be indexed because no db2index function was defined for the backend.

Contact Sun ONE Technical Support.

5020

Error

The server is unable to allocated a new task for the index. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5021

Error

The server is unable to create an index thread. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5023

Error

The server is unable to create a task node.

See the error log for more information and contact Sun ONE Technical Support.

5024

Error

The server is unable to create a global tasks lock. This is usually due to a resource problem.

Free up resources on the machine and restart the server.

5025

Error

The database could not be imported because the server was unable to locate the instance name for the specified suffix.

Check that the suffix is specified correctly in the configuration.

5026

Error

The database could not be imported because the server was unable to locate the database for the specified suffix.

Check that the database and the suffix are specified correctly in the configuration.

5027

Error

The database could not be imported because the server was unable to locate the specified backend.

Check that the database and the suffix are specified correctly in the configuration.

5028

Error

The database could not be imported due to a problem with the suffix configuration.

Check that the suffix is specified correctly in the configuration.

5029

Error

The database could not be exported because it could not be found.

Check that the database and the suffix are specified correctly in the configuration.

5030

Error

The database could not be restored because the archive2db function was not defined.

None - this type of database cannot be restored.

5031

Error

The server cannot index the database because the specified backend was not found.

Contact Sun ONE Technical Support.

5034

Error

An export has been called with incompatible options nsExportReplica=true and dsDecryptAttrs=false. It is not possible to dump a replica with encrypted attributes.

Avoid using both options at the same time. Ensure that attributes are decrypted (i.e. dsDecryptAttrs=true) if you want to export the database for replication purposes.

5121

Error

The server cannot register an object extension (during resource limit initialization).

Contact Sun ONE Technical Support.

5122

Error

System error - the server cannot create a new lock for the resource limit.

Contact Sun ONE Technical Support.

5123

Error

Resource limit initialization failed. This is likely to be a resource issue.

Check the error message in the log file and contact Sun ONE Technical Support.

5124

Error

The server could not obtain the object extension (for the resource limit).

Contact Sun ONE Technical Support.

5126

Error

A parameter error occurred when registering a new resource to be tracked. The LDAP attribute type that can be consulted in the bound entry to determine the limit's value is already registered.

Check that the attribute provided is registered only once.

5127

Error

A parameter error occurred when registering a new resource to be tracked.

  1. Check that the type is SLAPI_RESLIMIT_TYPE_INT

  2. Check that attrname is an LDAP attribute type that can be consulted in the bound entry to determine the limit's value.

5127

Error

Internal error. When retrieving the integer limit associated with a connection and a resource, a parameter with a NULL value was found.

Contact Sun ONE Technical Support.

5128

Error

Parameter error. The handle used to identify a resource is unknown.

Contact Sun ONE Technical Support.

5129

Error

An attempt is being made to allocate 0 or a negative number of bytes. This is likely to be a software issue.

Contact Sun ONE Technical Support.

5130

Error

Memory allocation has failed. This is probably because of a lack of available memory.

Increase the virtual memory available to your server, or reduce the size of the server's maximum entries in cache (cachesize) or maximum database cache size (dbcachesize) parameters.

5132

Error

Memory reallocation has failed. This is probably because of a lack of available memory.

Increase the virtual memory available to your server, or reduce the size of the server's maximum entries in cache (cachesize) or maximum database cache size (dbcachesize) parameters.

5135

Error

Memory c-allocation has failed. This is probably because of a lack of available memory.

Increase the virtual memory available to your server, or reduce the size of the server's maximum entries in cache (cachesize) or maximum database cache size (dbcachesize) parameters.

5136

Error

String duplication has failed. This is probably because of a lack of available memory.

Increase the virtual memory available to your server, or reduce the size of the server's maximum entries in cache (cachesize) or maximum database cache size (dbcachesize) parameters.

5137

Error

BER value duplication has failed. This is probably because of a lack of available memory.

Increase the virtual memory available to your server, or reduce the size of the server's maximum entries in cache (cachesize) or maximum database cache size (dbcachesize) parameters.

5249

Error

An entry in the configuration file was empty or could not be parsed.

Check the entry syntax in the configuration file.

5250

Error

The specified configuration attribute in the dse.ldif file has no value or the value is invalid.

Check that the value of the attribute under cn=config in the dse.ldif file is either on or off.

5251

Error

The error log filename could not be set, either because the filename was NULL or the path was invalid.

Check that the value of the attribute nsslapd-errorlog under cn=config in the dse.ldif file is valid, and that the path exists.

5252

Error

The error log level could not be set because its value is undefined.

Check that the value of the attribute nsslapd-errorlog-level under cn=config in the dse.ldif file is set, and is correct.

5253

Error

The request to set the maximum number of file descriptors has failed. The value is either NULL, or out of the permitted range [1..max] where max is the maximum number of file descriptors that can be created by a process.

Check that the value of the attribute nsslapd-maxdescriptors in the dse.ldif file is not higher than the RLIMIT_NOFILE parameter, and is not lower than 1.

5254

Error

The attribute nsslapd-errorlog-level in the configuration file has been ignored, because the -d option was specified at the command line.

Do not specify the -d option at the command line if you want the value of this attribute in the configuration file to be taken into account.

5255

Error

Failed to load the specified plug-in because the configuration entry of the plug-in in the dse.ldif file is invalid.

Check and correct the faulty configuration entry in the dse.ldif file.

5385

Error

While attempting to convert an LDIF entry to an LDAP entry, the server found that the entry has no DN.

Check the entry and make sure that it has a DN.

5390

Error

While attempting to convert a string entry to an LDAP entry, the server found that the entry has no DN.

Check the entry and make sure that it has a DN.

5392

Error

An error occurred while attempting to remove attribute values. This may be due to a duplicate attribute value.

Check the attribute values being removed.

5393

Error

The server failed to add a value to the value tree.

Check the error log for more information.

5395

Error

The attribute nscpEntryWSI cannot be computed by a user who is not the Directory Manager.

Check the client application making the request. The client must bind as root to be able to compute this attribute.

5505

Error

A plugin has attempted to register a new extension to an object type, but the object type is in use, by at least one object.

Correct the plugin code.

5641

Error

The parent node for the current mapping tree node could not be located.

Check the nsslapd-parent-suffix attribute of the entry in the configuration file (dse.ldif).

5642

Error

The new mapping tree node is either a "backend" or "referral on update" node but has no backend defined.

Check the nsslapd-backend attribute of the entry in the configuration file (dse.ldif).

5643

Error

The new mapping tree node is either a "referral" or "referral on update" node but has no referral defined.

Check the nsslapd-referral attribute of the entry in the configuration file (dse.ldif).

5644

Error

The distribution plugin could not be loaded.

Check the error log for more information. The dynamic library may not be present, may be inaccessible, or may be using another library that is not present.

5645

Error

The entry is missing either the distribution plugin or the distribution function name.

Check the nsslapd-distribution-plugin and nsslapd-distribution-func attributes in the configuration file (dse.ldif).

5648

Error

The mapping tree node could not be created.

Check the error log for evidence of the failure, otherwise not contact Sun ONE Technical Support.

5659

Error

The distribution function in the plugin library could not be located.

Check the error log for more information. The dynamic library may not be present, may be inaccessible, or may be using another library that is not present.

5890

Error

No schema files are present in the schema directory.

Restore the default schema files from a backup or CD image.

5893

Error

The specified entry was added without an objectclass attribute.

Check the application that added the entry.

5894

Error

The entry was added or modified with an unknown objectclass.

Check the application that added or modified the entry.

5895

Error

The entry that was added or modified is invalid. A single-valued attribute has multiple values.

Check the application that added or modified the entry.

5896

Error

The entry that was added or modified is missing a required attribute.

Check the application that added or modified the entry.

5897

Error

The entry that was added or modified contains an invalid attribute.

Check the application that added or modified the entry.

5900

Error

While parsing the schema ldif file, no value was specified for the objectClasses attribute.

Check the schema ldif file or the schema modification request.

8194

Error

The consumer has returned a disabled error, that is, it is not in a state in which it can receive replication updates.

Enable the consumer replica. It may also be necessary to reinitialize the consumer.

8195

Error

Looping through the changelog failed.

Ensure that replication is working correctly (using the insync utility and checking the replication agreement object).

Check the error code in the error log for more information.

8196

Error

The value of the ds5ReplicaTransport
WindowSize attribute is invalid.

Check the dse.ldif file or the LDAP entry defining the Replication Agreement.
Check the modification operation attempted on the replication agreement.

8197

Error

The value of the ds5ReplicaTransport
GroupSize attribute is invalid.

Check the dse.ldif file or the LDAP entry defining the Replication Agreement. Check the modifications attempted on the replication agreement.

8198

Error

The value of the ds5ReplicaTransport
CompressionLevel attribute is invalid.

Check the dse.ldif file or the LDAP entry defining the Replication Agreement. Check the modifications attempted on the replication agreement.

8199

Error

The user is not permitted to modify the specified replication agreement attribute.

Check the dse.ldif file or the LDAP entry defining the Replication Agreement. Check the modifications attempted on the replication agreement.

8200

Error

The replication agreement is being stopped.

Wait until the agreement has been stopped and retry.

8202

Error

A replication agreement with the specified DN could not be found.

Check the specified DN and all replication agreements. Check that the error is not in the client application.

8204

Error

The server received an update operation that is permitted for internal operations only.

Check the client that sent the forbidden update operation.

8212

Error

  1. The replication schedule format is invalid.

  2. The replication agreement is stopping.

  1. Check the client application.

  2. Wait until the agreement has stopped and try again.

8213

Error

An attempt was made to change the configuration for partial replication, on an enabled replication agreement

To change the partial replication configuration, disable the replication agreement first.

8215

Error

Partial replication has not been started.

Check the configuration of this replication agreement (specifically partial configuration entries). Start the partial replication feature for this agreement in the console.

8216

Error

The partial replication configuration has been modified.

Update the current configuration on the supplier, or reinitialize the consumer.

8218

Error

The latest replication protocol (v5.0) is not supported for this consumer.

Check the version of Directory Server running on the specified consumer.

8219

Error

The server was unable to parse the update vector for the specified replica.

Check that the consumer sent the replica update vector (RUV) during the start request.

8220

Error

The time difference between the specified replicas is too great for replication to work correctly.

Ensure that the supplier and consumer machines have the same time and date. The use of the Network Time Protocol (NTP) is recommended.

8221

Error

A fatal error occurred during an incremental update. Replication on this consumer will be disabled.

Check the error log on the consumer for more information. Restart replication by updating the replication agreement and reinitializing updates.

8225

Error

An error occurred while writing an attribute value in the replica entry.

Although harmless while the server is up and running, this error may lead to a replication malfunction the next time the server is restarted.

The error occurs when the value of an important replication configuration attribute cannot be stored persistently in the dse.ldif file.

Stop the server inmediately and check the cn=replica entry for this suffix (in the dse.ldif file.) If the attribute dsfilterspconfig
checksum is present in the entry, set its value to the value included in the error log. If the attribute dsfilterspconfig
checksum is not present in the entry, add it and set its value to the value included in the error log. Restart the server.

8226

Error

An error occurred while writing an attribute value in the replica entry.

Although harmless while the server is up and running, this error may lead to a replication malfunction the next time the server is restarted.

The error occurs when the value of an important replication configuration attribute cannot be stored persistently in the dse.ldif file.

Stop the server inmediately and check the cn=replica entry for this suffix (in the dse.ldif file.) If the attribute lastInitTimeStamp is present in the entry, set its value to the value included in the error log. If the attribute lastInitTimeStamp is not present in the entry, add it and set its value to the value included in the error log. Restart the server.

8227

Error

The server was unable to access to its own internal schema entry.

Stop and restart the server. If this does not solve the problem, contact Sun ONE Technical Support.

8228

Error

A replication protocol bind error has occurred.

Check that the consumer is up and running.

8229

Error

The server was unable to start a total replication update session.

Check that the consumer is up and running.

8230

Error

The pathname is invalid, or there is unsufficient access to create the changelog directory.

Check that the path is valid and that there are sufficient access rights to create the directory.

8232

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8234

Error

The changelog is not initialized, or an attempt has been made to configure the changelog cleanup parameters, when the changelog service is not started.

Ensure that the changelog service has been enabled.

8236

Error

This is probably due to a database or file access problem.

Enable the replication logs and retry the operation to see if additional reasons are output to the error log.

8241

Error

A change record in the database has an invalid version number.

  1. Disable and re-enable replication for this database.

  2. Reinitialize the server.

  3. Contact Sun ONE Technical Support.

8242

Error

There is an invalid change record in the changelog.

Ordinarily, this error should not occur. If it does, the changelog is likely to be corrupted. In this case, reset the changelog for this database by reloading the data or disabling/enabling replication. If this does not solve the problem, contact Sun ONE Technical Support.

8243

Error

A database error occurred while the transaction was starting. This is likely to be a resource problem.

Check DB error and take action based on the error code. In other words, refer to the database errors guide.

8244

Error

A database error occurred while the transaction was being aborted. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8245

Error

A database error occurred while the transaction was being committed. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8246

Error

A database error occurred while the transaction was starting. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8247

Error

A database error occurred. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8248

Error

A database error occurred while the transaction was being aborted. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8249

Error

A database error occurred while the transaction was being committed. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8250

Error

A database error occurred. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8251

Error

A database error occurred. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8252

Error

A database error occurred. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8253

Error

A database error occurred. This is likely to be a resource problem.

Check the corresponding database error code, and take action according to the database problem.

8256

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8257

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8258

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8259

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8260

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8261

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8262

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8263

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8264

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8266

Error

An internal database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8267

Error

The server was unable to retrieve the number of entries in the changelog.

Enable replication logging and check the specific replication error code for more information.

8268

Error

A database error occurred.

Check the corresponding database error code, and take action according to the database problem.

8271

Error

The RUV returned by the consumer could not be parsed or caused a problem.

Check the consumer configuration. It may be necessary to reinitialize the consumer.

8272

Error

The consumer returned a disabled error, that is, it is not in a state to receive replication updates.

Enable the consumer replica. It may also be necessary to reinitialize the consumer.

8276

Error

The replica is still being configured. The replication session cannot be accepted yet.

Wait until the configuration is complete and restart replication on the supplier.

8277

Error

The replication session cannot be accepted because no replica has been defined for the suffix.

Check that the supplier replication agreement is correct. Enable replication on the consumer.

8278

Error

The consumer is configured as a legacy replica and can therefore not accept multimaster replication.

Correct the replication topology.

8279

Error

The consumer is denying the right to replicate

Check that the replication identity is properly defined and matches the one that the supplier is using.

8281

Error

The consumer is not yet initialized and can therefore not accept changes.

Initialize the consumer, either online or offline.

8282

Error

The consumer appears to have the same replicaId as the supplier (both are masters).

Disable and re-enable replication, providing a different ReplicaID for one of the servers.

8283

Error

The consumer replica is already busy with a replication session.

Wait and try later. If this error persists, restart the server.

8284

Error

The consumer server is a master and can therefore not accept a partial replica.

Make the consumer a read-only server, or unconfigure partial replication in the replication agreement.

8287

Error

The value of the attribute ds5ReplicaTransport
GrpPktSize is invalid.

Check the dse.ldif file or the LDAP entry defining the replication agreement.

Check the modifications attempted on the replication agreement.

8288

Error

Value of attribute ds5ReplicaTransport
ConcurrencyLevel is invalid.

Check the dse.ldif file or the LDAP entry defining the replication agreement.

Check the modifications attempted on the replication agreement.

8292

Error

Consumer initialization has been requested but the supplier database is empty.

Load data onto the supplier before attempting to initialize the consumer with that supplier.

8293

Error

A fatal problem has occurred on the remote consumer.

Check the error log on the consumer for more information. Once the problem has been solved, you will need to update the replication agreement and reinitiate updates.

8294

Error

The changelog file contains data changes from a replica that has been unconfigured.

No action is necessary - this is an informational message.

8302

Error

A protocol error occurred. The entry was incorrectly encoded.

Check the error code and contact Sun ONE Technical Support.

8303

Error

Schema replication failed locally on the consumer.

Check error code and contact Sun ONE Technical Support.

8307

Error

An internal error occurred while adding an entry to the import queue, or while acknowledging the entry to the supplier.

Check the error log for a disk space problem and reinitialize the database. If the problem persists, contact Sun ONE Technical Support.

8308

Error

A badly formed change was received.

Contact Sun ONE Technical Support.

8311

Error

An internal error occurred in the sequencing of replicated operations.

Contact Sun ONE Technical Support.

8312

Error

The replicated change could not be applied on this consumer.

Check the error code. A delete operation may generate a return code of 32 - this error code is harmless (a dependency of changes between several masters).

If the error persists, contact Sun ONE Technical Support.

8318

Error

Authentication failed. This may be due to an invalid host:port, an invalid identity, or the fact that the consumer is down.

Check the error code and fix the replication agreement. It may be necessary to restart the consumer.

8319

Error

Replication was unable to start. This is likely to be caused by an error in the replication configuration.

Check the error log for more information. Also check the error logs on the consumers.

8320

Error

Replication was unable to end. This may be because a network outage has occurred, the consumer is down, or the consumer has already dropped the connection.

Check the error log for more information. Also check the error logs on the consumers.

12289

Error

The TCP port to which you are attempting to bind is already in use.

  1. Restart the server, using a different port.

  2. Stop the application bound to that port and restart the server.

12290

Error

There is an error in the naming service configuration.

Add listen host (variable) to the naming service.

12291

Error

The LDAP port is missing from the configuration.

Add an LDAP port to the configuration file or use the command line.

12292

Error

System error, probably due to a resource problem.

Free up resources on the machine and restart the server.

12293

Error

There is an error in the configuration file. See the reservedfd attribute.

Increase the maximum number of file descriptors (in the configuration file) by increasing the value of nsslapd-maxdescriptors.Otherwise, check the Directory configuration and reduce the resource usage (number of threads, and number of backends, for example.)

12294

Error

There are insufficient file descriptors to accept new connections. This may be because:

  1. the value of the maxdescriptors attribute is too small

  2. the hard limit on descriptors is too small

  3. the value of the reservedescriptors attribute is too large

Increase the number of file descriptors available to the slapd process.

The error log displays the number of file descriptors currently available to the slapd process, and the number of descriptors reserved for internal slapd use. The total number of file descriptors available to the process must be greater than variable

12295

Error

Probably due to a resource problem on the system.

Restart the directory server.

12296

Error

Probably due to a resource problem on the system.

Restart the directory server.

12297

Error

Probably due to a resource problem on the system.

Restart the directory server.

12298

Error

Internal error.

Contact Sun ONE Technical Support.

12299

Error

There is an error in the naming service configuration.

Add the listen host variable to the naming service. See your operating system documentation for more information.

12300

Error

There is an error in the naming service configuration.

Add the listen host variable to the naming service. See your operating system documentation for more information.

12301

Error

The server was unable to initialize the security library.

Contact Sun ONE Technical Support.

12302

Error

More than one directory server is running.

Stop the directory servers that should not be running.

12304

Error

The server was unable to locate the specified user in the system account database.

Add the user to the system account database and restart the server.

12308

Error

This is an internal error, most likely to be related to a memory allocation problem.

Increase the virtual memory of the machine and restart the directory server.

12318

Error

An error occurred during the base64 encoding of a value. This is an internal error with no specific cause. It may be due to a resource problem.

Report the error to your administrator.

12319

Error

The request has been aborted due to an internal error.

Please contact Sun ONE Technical Support.

12320

Error

Configuration error. The server failed to obtain the frontend configuration entry.

Correct the frontend configuration entry and restart the server.

12321

Error

Configuration error. The server failed the frontend sanity check.

Correct the frontend declaration and restart the server.

12322

Error

Internal error occurred during the call to DsmlParser_startParse. This error has no specific cause but may be related to a resource problem.

Report the error to your administrator.

12323

Error

This is an internal error with no specific cause. It may be related to a resource problem.

Report the error to your administrator.

12324

Error

Internal error. The server failed to register the HTTP port.

Check that the specified port is not currently in use and restart the server.

12325

Error

Internal error. The server failed to register the HTTPS port.

Check that the specified port is not currently in use and restart the server.

12326

Error

Configuration error: the maximum size of the parser pool is lower than the current size.

In the dse.ldif file, check that the value of the ds-hdsml-poolsize attribute is lower than the value of the ds-hdsml-maxpoolsize attribute.

12327

Error

An error occurred while trying to create an instance of a UTF8 transcoder. This is an internal error with no specific cause. It may be related to a resource problem.

Report the error to your administrator.

12328

Error

Internal error. The server failed during the initialization of the DSML worker.

Please contact Sun ONE Technical Support.

12329

Error

A request has not been processed due to a connection closure.

Check the connection and retry.

12330

Error

An internal memory management error has occurred.

Please contact Sun ONE Technical Support.

12332

Error

Initialization error. The server failed to set the plug-in functions.

Correct the frontend configuration and restart the server.

12333

Error

Internal error. The server failed to instantiate the frontend plug-in.

Please contact Sun ONE Technical Support.

12334

Error

Unknown internal error.

Please contact Sun ONE Technical Support.

12335

Error

Configuration error. A configuration attribute is invalid.

Correct the specified attribute and restart the server.

12336

Error

Configuration error. The syntax of a configuration attribute is invalid.

Correct the syntax of the specified attribute and restart the server.

12337

Error

Internal I/O error.

Please contact Sun ONE Technical Support.

12338

Error

System error, probably due to insufficient resources (lack of memory).

Please contact Sun ONE Technical Support.

12339

Error

Memory management system error.

Please contact Sun ONE Technical Support.

12340

Error

Configuration error: DSML schema location is not defined. Under normal circumstances, the default value of the DSML schema location is hardcoded. However, this default value can be overridden in the dse.ldif file.

Correct the value of the ds-hdsml-schemalocation attribute in the dse.ldif file, or remove this attribute from the file.

12341

Error

Configuration error: DSML schema URN is not defined. Under normal circumstances, the default value of the DSML schema URN is hardcoded. However, this default value can be overridden in the dse.ldif file.

Correct the value of the ds-hdsml-urn attribute in the dse.ldif file, or remove this attribute from the file.

12342

Error

Configuration error. Under normal circumstances, the default value of the SOAP schema location is hardcoded. If this error occurs, there is an internal problem.

Report the error to your administrator.

12343

Error

Configuration error. Under normal circumstances, the default value of the SOAP schema URN is hardcoded. If this error occurs, there is an internal problem.

Report the error to your administrator.

12344

Error

Internal error: a lock for concurrent access to the specified list is missing. The lock should have been defined previously.

Report the error to your administrator.

12345

Error

Internal error that occurs when the pool of parsers is empty and cannot be extended (all the parsers are in use).

Increase the value of the maximum pool size, specified by the ds-hdsml-poolmaxsize attribute in the dse.ldif file.

12346

Error

An error occurred during the call to DsmlParser_getNext
Request.

None - a SOAP fault is returned to the client with the reason for the failure.

12347

Error

Configuration error. The secure identity method configuration parameter is invalid.

Correct this parameter and restart the server. Possible values for the secure identity method parameter are:

    clientCertOnly
    clientCertFirst
    httpBasicOnly

12348

Error

An exception was raised when calling XMLString::
transcode. This is an internal error with no specific cause. It may be due to a resource issue.

Report the error to your administrator.

12352

Error

A SOAP/DSML error occurred during a call to DSMLParser_startParse.

None - a SOAP/DSML error message is returned to the client with the reason for the failure.

12353

Error

This error occurs when a bad request is submitted to the parser. It should not occur in the case of the valid fake request. The DSML/SOAP schema URN and/or location may be invalid.

Check the error log for more information. If the schema URN and/or location are invalid, check the following attributes in the dse.ldif file:
ds-hdsml-dsmlurn
ds-hdsml-
 dsmlschemalocation

12354

Error

This error occurs when a bad request is submitted to the parser. It should not occur in the case of the valid fake request. Cause unknown.

Please contact Sun ONE Technical Support.

12355

Error

Configuration error: an XML schema is missing.

Insert the missing schema in the specified location and restart the server.

12356

Error

The client must provide a SOAPAction header. If it is absent, the request is rejected.

Provide a SOAPAction header, the contents of which may be set to any value (including an empty value), for example:

SOAPAction:
SOAPAction: ""
SOAPAction: "batchRequest"

12362

Error

It is likely that the port number configured for this server requires that the server be run as root.

Restart the server using a port that does not required root access or start the server as a user with root access.

20490

Error

Database recovery has failed.

This is a serious database error. Please contact Sun ONE Technical Support.

20492

Error

The Netscape Portable Runtime (NSPR) was unable to create one or more threads. This may be due to insufficient resources.

  1. Check that there is sufficient available memory and that a sufficient number of threads per process has been set up in the operating system configuration.

  2. Check the error code that appears in the log against the NSPR error codes (see the NSPR error code reference for more information.)

20494

Error

An attempt was made to open a database with a different database version. This is probably a migration issue.

Re-export the database from the old server and re-import it to the new server.

20499

Error

The internal NEXTID counter has reached the limit.

Rebuild the database.

20501

Error

The database has reported an error. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support.

20502

Error

The database has reported an error. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support

20503

Error

The database has reported an error. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support

20504

Error

The database has reported an error. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support

20505

Error

The database has reported an error other than an inability to write pages to the disk immediately. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support

20506

Error

The database has reported an error. If the printed value is positive, this is a system error. If the printed value is negative, the database has not been recognized or must be recovered.

This is a serious database error. Please contact Sun ONE Technical Support

20507

Error

This is a file system error. The server was unable to create the required guardian file.

Check that the user specified at installation has the appropriate permissions to write to the database directory.

20508

Error

The database is corrupt. This is most likely to be the result of a previously aborted database import.

Reimport or delete the database.

20512

Error

This is a file system error. The server was unable to write to or close the guardian file.

Check that the user specified at installation has the appropriate permissions to write to the database directory. Ensure that the file system is not full.

20513

Error

This is a file system error. The server was unable to delete the guardian file.

Check that the user specified at installation has the appropriate permissions to write to the database directory.

20737

Error

This is a software problem.

Please contact Sun ONE Technical Support.

20738

Error

The limit for the database internal identifier has been reached. This is probably due to several adds and deletes being performed on the local database.

Rebuild the database, using db2ldif, then ldif2db.

20739

Error

The limit for the database internal identifier is close to being reached. This is probably due to several adds and deletes being performed on the local database

If the limit has been reached, rebuild the database, using db2ldif, then ldif2db.

20740

Error

The database is not coherent. There is a child entry that is unknown to the parent entry and the numsubordinates attribute is absent in the parent entry.

Rebuild the database, using db2ldif, then ldif2db.

20745

Error

An entry could not be located during an ldbm_back_seq operation. The database is incoherent.

Rebuild the database, using db2ldif, then ldif2db.

20746

Error

An index file could not be located during an ldbm_back_seq operation. The database is incoherent.

Rebuild the database, using db2ldif, then ldif2db.

20747

Error

Certain entries were deleted while the server was attempting to sort them. This is probably due to a VLV or SORT control in a search.

Create a VLV index to avoid "on the fly" sorting.

20748

Error

The local database could not be started because the limit subsystem did not allow it to register.

Check the resource limit configuration and restart the server.

20749

Error

The local database could not be started because the underlying database component did not start.

Check that the database configuration is correct, and that enough disk space is available.

20750

Error

The local database instances could not be started.

Check that the database configuration is correct, and that enough disk space is available.

20751

Error

The binary code for one version of Directory Server was started on a database with a different version.

Check the versions and ensure that the same binary and database versions are used.

20752

Error

The server could not locate the file used for the virtual list view (VLV) index during an update.

The database is inconsistent.

Rebuild the database, using db2ldif, then ldif2db.

20753

Error

The database is incoherent.

Rebuild the database, using db2ldif, then ldif2db.

20754

Error

The system is out of memory

Check the configuration.

20755

Error

The server could not locate the file used for virtual list view (VLV) indexes.

The database is inconsistent.

Rebuild the database, using db2ldif, then ldif2db.

20756

Error

The server could not locate a cursor used for virtual list view (VLV) indexes.

The database is inconsistent.

Rebuild the database, using db2ldif, then ldif2db.

20757

Error

The server could not locate an entry that is present in the virtual list view (VLV) index.

The database is inconsistent.

Rebuild the database, using db2ldif, then ldif2db.

20758

Error

The server could not locate an entry that is referenced in a virtual list view (VLV) index.

The database is inconsistent.

Rebuild the database, using db2ldif, then ldif2db.

20759

Error

The server could not locate an index used in virtual list view (VLV).

Check the VLV configuration.

20760

Error

An LDAP client attempted to create a virtual list view (VLV) index with an invalid name. This should not harm the directory server.

Change the LDAP client so that it uses a valid name.

20761

Error

The limit for the database internal identifier has been reached. This is probably because several adds and deletes have been performed on the local database.

Regenerate the database using ldif2db and db2ldif.

20762

Error

The server was unable to index the entry being added.

Check the previous errors in the log for additional information.

20763

Error

The acceptable number of add retry counts was exceeded without success. Another operation may be ongoing, resulting in a conflict when trying to access that part of the database.

Wait until other operations have ended and retry the add operation.

20764

Error

The server was unable to initialize the attribute structure. This is probably a memory error.

Check the available memory.

20765

Error

An attempt was made to delete an entry that was not a tombstone entry.

Please contact Sun ONE Technical Support.

20766

Error

An attempt was made to tombstone an entry that is already a tombstone entry.

Please contact Sun ONE Technical Support.

20768

Error

The acceptable number of delete retry counts was exceeded without success. Another operation may be ongoing, resulting in a conflict when trying to access that part of the database.

Wait until other operations have ended and retry the delete operation.

20772

Error

The acceptable number of modify retry counts was exceeded without success. Another operation may be ongoing, resulting in a conflict when trying to access that part of the database.

Wait until other operations have ended and retry the modify operation.

20773

Error

The acceptable number of modrdn retry counts was exceeded without success. Another operation may be ongoing, resulting in a conflict when trying to access that part of the database.

Wait until other operations have ended and retry the modrdn operation.

20774

Error

The server was unable to add a new value to the index.

Check the error log for more information and contact Sun ONE Technical Support.

20775

Error

A database error occurred while trying to build the list of possible candidate entries. The index files may be corrupt.

Re-index and try again.

20776

Error

The candidate entry has a NULL referral.

Update the referral in the entry or remove the ref attribute.

20777

Error

The server failed to bypass the filter test.

Please contact Sun ONE Technical Support.

20778

Error

The server was unable to add configuration entries to the DSE.

Ensure that there is no inconsistency within the entries.

20779

Error

The configuration information under cn=config could not be read.

Please contact Sun ONE Technical Support.

20780

Error

The nsslapd-instancedir attribute under cn=config could not be read. The attribute may be missing.

Ensure that the nsslapd-instancedir attribute is present and has an appropriate value.

20786

Error

An invalid value was provided for the nsslapd-db-trickle-percentage attribute. The value should be between 0 and 100.

Check and correct the value provided for the nsslapd-db-trickle-
percentage attribute

20787

Error

An attempt was made to modify a configuration attribute while the server was running. This attribute cannot be changed online.

Stop the server before modifying the attribute.

20788

Error

The attribute value must be numerical.

Ensure that the attribute has a numerical value.

20789

Error

The value specified for the attribute is greater than the maximum permitted.

Ensure that the attribute value is smaller than or equal to the maximum value.

20790

Error

The value specified for the attribute is smaller than the minimum permitted.

Ensure that the attribute value is greater than or equal to the minimum value.

20791

Error

The value specified for the attribute is outside the permissible range.

Ensure that the attribute value is within the representable range.

20792

Error

The server failed to set the instance configuration attribute.

Ensure that both the syntax and the value of the attribute are correct.

20793

Error

The server was unable to access the ldbm configuration in the DSE.

Check that the dse.ldif file has not been corrupted and restart the server.

20795

Error

The specified instance was not found because no such instance exists.

Verify that the instance name is correct and corresponds to an existing instance.

20796

Error

The specified instance is currently processing a task.

Cancel the current task or wait for it to finish and retry.

20797

Error

An attempt was made to change the suffix associated with an ldbm database.

Do not modify the nsslapd-suffix attribute of an existing instance.

20806

Error

The system information from the backend's DBVERSION file did not match the server information.

Edit the backend's DBVERSION file to match the server information.

20807

Error

The server was unable to obtain the system information. This is possibly a permissions or NSPR compilation issue.

Check that the user specified at installation has the appropriate permissions.

20994

Error

The available space on a disk used by the Directory Server has dropped below the value of the disk-full-threshold attribute.

Increase the available disk space.

20996

Error

Database corruption.

Restore the database from a backup.

20997

Error

Database corruption.

Restore the database from a backup.

21005

Error

An attribute index is configured but the corresponding database index file could not be opened.

Check whether the file exists and/or rebuild it using db2index.

21006

Error

An attribute index has been configured but the corresponding database index file could not be opened.

Check whether the file exists and/or rebuild it using db2index.

21008

Error

Insufficient system resources.

Check the available memory.

21009

Error

Insufficient system resources.

Check the available memory.

21010

Error

Insufficient system resources.

Check the available memory.

21011

Error

Insufficient system resources.

Check the available memory.

21012

Error

Insufficient system resources.

Check the available memory.

21016

Error

An index could not be created on the disk.

Check the error log for previous messages that should isolate the problem.

21017

Error

Database corruption.

Rebuild the parentid index or restore the database from a backup.

21018

Error

Insufficient system resources.

Check the system free memory.

21022

Error

The cachesize as defined in the configuration file exceeds database limits.

Lower the value of the cachesize attribute in the configuration file.

21023

Error

Database corruption.

Rebuild the affected index or restore the database from a backup.

21249

Error

The server was unable to encrypt the specified attribute inside the entry.

Check the attribute encryption configuration.

21250

Error

The server was unable to decrypt the specified attribute inside the entry.

Check the attribute encryption configuration.

21251

Error

The value is already encrypted or does not match the algorithm specified in the configuration.

Check that the attribute encryption configuration is correct.

21252

Error

The server was unable to locate the plug-in for the specified algorithm.

Enable the encryption plug-in.

21253

Error

The server was unable to encrypt the specified values.

Check that the values are not already encrypted and that the cipher with which they are being encrypted match the configuration settings.

21254

Error

The server was unable to encrypt/decrypt the attribute's values. The attribute may already be encrypted with an incorrect algorithm or the algorithm plug-in may be missing.

Check for inconsistencies in the attribute encryption configuration.

21255

Error

An error occurred during the plug-in's encryption function.

Check the plug-in traces. Ensure that the plug-in itself has not been corrupted.

21256

Error

An error occurred during the plug-in's decryption function.

Check the plug-in traces. Ensure that the plug-in itself has not been corrupted.

24577

Error

The bulk import has been aborted.

Ensure that the bulk import is started or previously suspended before attempting an update or restart.

28673

Error

The attribute filterspconfchecksum could not be updated with a new value.

  1. Check whether the attribute already exists in the entry.

  2. Check whether the attribute is present in the dse.ldif file.

32769

Error

There is not enough memory to register the roles plug-in into the service provider broker.

Restart the server.

32770

Error

There is not enough memory to register the nsrole attribute.

Restart the server.

32771

Error

This error indicates a resource problem on the machine.

Restart the server.

32772

Error

This error indicates a resource problem on the machine.

Restart the server.

32773

Error

This error indicates a resource problem on the machine.

Restart the server.

32774

Error

This error indicates a resource problem on the machine.

Restart the server.

32775

Error

The specified entry does not contain an objectclass.

Check the entry and add the required objectclass.

32776

Error

An unknown operation has been performed on the server and is triggering a role cache update.

Check that the specified operation is valid.

32778

Error

The maximum number of nested roles has been exceeded. This is probably due to a circular role definition.

Check the role definitions. The maximum number of nested roles permitted is defined by MAX_NESTED_ROLES.

32779

Error

The entry corresponding to the DN does not exist.

Check the role definition.

32780

Error

The server is unable to update the pblock parameters.

Restart the server.

32781

Error

The role type is unknown. Valid role types are : managed, filtered, or nested.

Check the role definition and amend the type as necessary.

33025

Error

Internal error, probably due to insufficient available memory.

Free up some memory. If the error continues, please contact Sun ONE Technical Support.

33026

Error

Internal error.

Please contact Sun ONE Technical Support.

33027

Error

Internal error.

Please contact Sun ONE Technical Support.

33028

Error

Internal error.

Please contact Sun ONE Technical Support.

33029

Error

Memory corruption or invalid configuration.

Check the plug-in configuration. If it is valid, please contact Sun ONE Technical Support.

33030

Error

Memory corruption or invalid configuration.

Check the plug-in configuration. If it is valid, please contact Sun ONE Technical Support.

33031

Error

Configuration error.

Check the plug-in configuration parameters in the dse.ldif file. Make sure that the syntax and values are correct.

33032

Error

Internal error.

Please contact Sun ONE Technical Support.

33033

Error

Internal error.

Please contact Sun ONE Technical Support.

33034

Error

Internal error.

Please contact Sun ONE Technical Support.

33035

Error

Internal error.

Please contact Sun ONE Technical Support.

33036

Error

Internal error.

Please contact Sun ONE Technical Support.

33037

Error

The new superior DN does not exist.

Check the validity of the intended operation.

33038

Error

The new rdn is invalid or is not correctly specified.

Check the validity of the intended operation.

33039

Error

Internal error.

Please contact Sun ONE Technical Support.

33040

Error

Configuration error.

Check the plug-in configuration parameters in the dse.ldif file. Make sure that the syntax and values are correct.

33041

Error

An error occurred during an internal search while performing an ADD operation.

Ensure that the database is not corrupt and contact Sun ONE Technical Support.

33042

Error

An error occurred during an internal search while performing a MOD operation.

Ensure that the database is not corrupt and contact Sun ONE Technical Support.

33043

Error

Internal error.

Please contact Sun ONE Technical Support.

33044

Error

An error occurred during an internal search while performing a MODRDN operation.

Ensure that the database is not corrupt and contact Sun ONE Technical Support.

33045

Error

Configuration error.

Check the plug-in configuration parameters in the dse.ldif file.

33793

Error

The server was unable to allocate mutexes for the CoS plug-in. This is probably due to a memory problem.

Free up resources on the machine and restart the server.

33794

Error

The server was unable to register a virtual attribute service provider.

Free up resources on the machine and restart the server.

33795

Error

The server was unable to create a CoS thread.

Free up resources on the machine and restart the server.

33796

Error

The server was unable to create the CoS schema cache.

  1. Free up resources on the machine.

  2. "Touch" a CoS definition to retrigger CoS cache building.

  3. Restart the server.

33797

Error

The server was unable to index the CoS cache.

  1. Free up resources on the machine.

  2. "Touch" a CoS definition to retrigger CoS cache building.

  3. Restart the server.

33798

Error

The server was unable to allocate memory for the CoS cache.

  1. Free up resources on the machine.

  2. "Touch" a CoS definition to retrigger CoS cache building.

  3. Restart the server.

33799

Error

The server was unable to read the suffix list from the rootDSE entry.

Restart the server.

33801

Error

There is an error in the definition of the specified CoS.

Check and correct the CoS definition. Note that a definition cannot supply its own specifier. The DN of the CoS template may be incorrect.

33802

Error

The server was unable to add the specified template to the CoS cache.

  1. Free up resources on the machine.

  2. "Touch" a CoS definition to retrigger CoS cache building.

  3. Restart the server.

33803

Error

The server was unable to locate the dn of the target entry during a search operation. This error should not occur under normal circumstances.

  1. Retry the search operation.

  2. Restart the server.

33804

Error

The server was unable to locate the objectClass of the target entry during a search or update operation. This error should not occur under normal circumstances.

  1. Retry the search or update operation.

  2. Restart the server.

33806

Error

The server was unable to start the CoS plug-in. This is probably due to a memory problem.

  1. Check the CoS plug-in configuration in the dse.ldif file.

  2. Check the CoS definitions and templates.

  3. Check the error log for a more specific error message.

  4. Restart the server.

33807

Error

The server was unable to register the CoS plug-in. This is probably due to a memory problem.

  1. Check the CoS plug-in configuration in the dse.ldif file.

  2. Check the error log for a more specific error message.

  3. Restart the server.

33808

Error

There is an error in the definition of the specified CoS.

Check and correct the CoS definition.

33809

Error

The server was unable to obtain the dn of the target entry during an update operation. This error should not occur under normal circumstances.

  1. Retry the update operation.

  2. Restart the server.

34817

Error

The server is unable to initialize the ACL plug-in. This is usually an indication of memory problems.

  1. Check the ACL plug-in configuration in the dse.ldif file.

  2. Check the error log for other, more specific error messages.

  3. Restart the server.

34818

Error

The server is unable to allocate mutex or reader/writer locks for the ACL plug-in at initialization time.

  1. Check the OS configuration and increase the file descriptors limit, if possible.

  2. Check the Directory Server configuration and reduce the resource usage.

34819

Error

The server is unable to allocate sufficient aclpb pool memory for the ACL plug-in.

Free up resources on the machine and restart the server.

34820

Error

This is an internal error and should not occur under normal circumstances.

  1. Attempt the LDAP operation again.

  2. Restart the server.

  3. Copy the errors log file and contact Sun ONE Technical Support.

34822

Error

The server us unable to allocate sufficient aclpb pool memory for the ACL plug-in.

Free up resources on the machine and restart the server.

34823

Error

The server was unable to remove the specified ACIs from the entry. See the error log for more information.

Attempt the modify operation again.

34824

Error

Initialization error. The server was unable to register the specified attributes with libaccess. See the error log for more information.

Verify the configuration and installation of the ACL plug-in.

34826

Error

There is an error (possibly invalid ACI syntax) in the ACI attribute being updated.

Correct the error in the ACI and attempt the ACI update operation again.

34827

Error

ACL parsing error for a macro ACI. See the log file for the exact cause of the error.

Correct the error in the ACI and attempt the ACI update operation again.

34828

Error

ACL parsing error. The server was unable to construct an LDAP filter for the specified string.

Correct the error in the ACI and attempt the ACI update operation again.

34829

Error

ACL parsing error. See the log file for the exact cause of the error.

Correct the error in the ACI and attempt the ACI update operation again.

34830

Error

The server failed to update ACIs in the specified entry, when an ACI was deleted.

  1. Attempt the update operation again.

  2. Restart the server.

34831

Error

The server is unable to allocate mutex or reader/writer locks for the ACL plug-in at operation time.

  1. Free up resources on the machine.

  2. Attempt the LDAP operation again.

  3. Restart the server.

34832

Error

The server is unable to get/create an operation extension structure at operation time.

  1. Free up resources on the machine.

  2. Attempt the LDAP operation again.

  3. Restart the server.

34834

Error

An invalid ACL operation extension was found. This is an internal error and should not occur under normal circumstances

  1. Attempt the LDAP operation again.

  2. Restart the server.

  3. Copy the errors log file and contact Sun ONE Technical Support.

34835

Error

This is an internal error and should not occur under normal circumstances.

  1. Attempt the LDAP operation again.

  2. Restart the server.

34838

Error

ACL parsing error: the parent keyword has been used with more than ten levels. Check the log file to see the type of ACI in which the keyword was used incorrectly.

Correct the error in the ACI and attempt the operation again.

36865

Error

An error occurred while releasing the collation lock.

Restart the server.

36866

Error

An error occurred while creating the collation lock.

Restart the server.

36867

Error

No argument was provided for the NLS parameter.

Check the configuration variable.

36868

Error

Insufficient arguments were provided for the collation parameter.

Check the configuration variable.

36869

Error

An invalid value was specified for the collation strength.

Check the configuration variable.

36870

Error

An invalid value was specified for the collation decomposition.

Check the configuration variable.

36871

Error

Too many items have been specified on the configuration line.

Check the configuration variable.

36872

Error

The server was unable to open the collation configuration file.

Check the path to the collation configuration file.

36873

Error

The server was unable to parse a line in the collation configuration file.

Check the collation configuration file.

36874

Error

The location of the collation configuration file was not provided to the plug-in.

Check the path to the collation configuration file.

37121

Error

The regular expression being constructed for the DN substring filter could not be stored in the memory allocated.

Check the DN substring filter being provided to the server.

37122

Error

The regular expression being constructed for the substring filter could not be compiled.

Check the substring filter being provided to the server.

37123

Error

A filter containing an unknown type was provided to the server.

Check the filter being provided to the server.

37377

Error

The state change plug-in could not be registered with the server.

Restart the server.

37378

Error

The server was unable to create a mutex for the state change subsystem.

Restart the server.

37379

Error

The server was unable to publish the interface to the state change plug-in API.

Restart the server.

37380

Error

The server was unable to determine the DN of the modified entry.

Restart the server.

37633

Error

An attempt was made to configure multiple instances of the passthrough authentication plug-in.

Check the pass-through authentication plug-in configuration.

37634

Error

An attempt was made to use the passthrough authentication plug-in without specifying any remote servers.

Check the pass-through authentication plug-in configuration.

37635

Error

The set of parameters specified for the remote server was invalid.

Check the pass-through authentication plug-in configuration.

37636

Error

The LDAP version specified for the remote server was invalid.

Check the pass-through authentication plug-in configuration.

37637

Error

The maximum number of connections to the remote server is specified as less than or equal to zero.

Check the pass-through authentication plug-in configuration.

37638

Error

The maximum concurrency is specified as less than or equal to zero.

Check the pass-through authentication plug-in configuration.

37639

Error

An error occurred while parsing the LDAP URL.

Check the pass-through authentication plug-in configuration.

37640

Error

The pass-through suffix was not specified in the LDAP URL.

Check the pass-through authentication plug-in configuration.

37641

Error

An error occurred while splitting the list of suffixes for which authentication is to be passed through.

Check the pass-through authentication plug-in configuration.

37642

Error

One of the suffixes for which pass-through authentication is configured exists in the local directory.

Check the pass-through authentication plug-in configuration.

37644

Error

An error occurred while adding a suffix to the list of suffixes handled by backends in the server.

Restart the server.

37645

Error

No active suffixes could be located in the local server.

Check the server configuration and/or restart the server.

37646

Error

The pass-through authentication plug-in could not be registered.

Restart the server.

37647

Error

The server was unable to locate the list of arguments to the pass-through authentication plug-in.

Check the pass-through authentication plug-in configuration.

37648

Error

The pass-through authentication plug-in could not be configured based on the arguments provided.

Check the pass-through authentication plug-in configuration.

37649

Error

The server was unable to determine the required information regarding the bind operation.

Check the bind request.

37650

Error

The server was unable to retrieve the set of controls associated with the bind request.

Check the bind request.

37651

Error

The server was unable to set the DN or authentication type associated with this connection.

Restart the server.

37889

Error

A failure occurred while registering the referential integrity plug-in.

Restart the server.

37890

Error

The server was unable to retrieve the required information about a delete operation.

Check the delete request.

37891

Error

The server was unable to determine the number of parameters to the referential integrity plug-in.

Restart the server.

37892

Error

The server was unable to retrieve the parameters associated with the referential integrity plug-in.

Restart the server.

37893

Error

No arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37894

Error

Insufficient arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37895

Error

The server was unable to retrieve the required information about a modrdn operation.

Check the delete request.

37896

Error

The server was unable to determine the number of parameters to the referential integrity plug-in.

Restart the server.

37897

Error

The server was unable to retrieve the parameters associated with the referential integrity plug-in.

Restart the server.

37898

Error

No arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37899

Error

Insufficient arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37900

Error

No arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37901

Error

An error occurred while searching for references to the deleted/renamed entry.

  1. Check the error log for details of the error.

  2. Restart the server.

37902

Error

The server was unable to determine the number of parameters to the referential integrity plug-in.

Restart the server.

37903

Error

The server was unable to retrieve the parameters associated with the referential integrity plug-in.

Restart the server.

37904

Error

No arguments were provided for the referential integrity plug-in.

Check the configuration of the referential integrity plug-in.

37905

Error

The server was unable to create the thread to perform integrity updates.

Restart the server.

37906

Error

Insufficient arguments were provided to the referential integrity plug-in to determine the update delay.

Check the configuration of the referential integrity plug-in.

37907

Error

The server was unable to retrieve the parameters associated with the referential integrity plug-in.

Restart the server.

37908

Error

The referential integrity log file could not be deleted.

Check the permissions on the specified file and restart the server.

37909

Error

The referential integrity log file could not be opened for writing.

Check the permissions on the specified file and restart the server.

37910

Error

The change to be written to the integrity log file was longer than the maximum length allowed.

Check for references to the specified entry and update manually if necessary.

37911

Error

The server was unable to write data to the integrity log file.

  1. Check the integrity log file.

  2. Check the filesystem status.

37912

Error

An error occurred while closing the integrity log file.

  1. Check the integrity log file.

  2. Check the filesystem status.

38913

Error

The mandatory SASL configuration entry (cn=SASL,cn=security,
cn=config) could not be retrieved from the configuration file.

Check the existence of this entry in the configuration file and add it if it is not present. (The entry contains the dsDaslConfig object class.)

38917

Error

The local host name is absent from the naming service.

Add the local host name to the naming service.

38918

Error

Incorrect or missing information in the SASL configuration entry in the dse.ldif file (under cn=sasl.)

  1. Check that the entry exists in the configuration file.

  2. Check that the information in the configuration entry is valid (authentication mechanism names are correct.)