|
| Sun ONE Directory Server 5.2 Reference Manual |
This appendix provides an extensive list of the error messages generated by Sun ONE Directory Server. While this list is not exhaustive, the information presented in this chapter will serve as a good starting point for common problems.
Common Error Codes
The following table describes the error codes displayed in the error log and the appropriate action to take should these errors occur.
Errors are defined according to their severity:
- Error - The error is severe. Immediate action should be taken to avoid the loss or corruption of directory data.
- Warning - Action should be taken at some stage to prevent a severe error occurring in the future.
- Info - An informative message, usually describing server activity. No action is necessary.
In this release, only the severe Error codes are documented. If you require further assistance in diagnosing errors, please contact Sun ONE Technical Support: http://www.sun.com/service/sunone/software/index.html
Table A-1 Directory Server Error Codes
Code
Severity
Error Text
Probable Cause
Action
4104
Error
No backend has been defined to do the import.
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
Bulk import not supported by this backend.
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
Ignoring extremely large value for configuration attribute attribute_name.
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 given file filename could not be accessed.
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 given file filename could not be opened for reading.
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
Could only read value of value bytes from configuration file filename.
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 default password storage scheme SSHA could not be read or was not found in the file filename. It is mandatory. Server exiting.
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
Skipping plugin plugin - no valid signature.
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
Unable to load plugin plugin_name.
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 password storage scheme plugins defined in the configuration.
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
Invalid scheme to hash password: scheme. Valid values are: scheme values.
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
Invalid scheme: scheme. No password storage scheme loaded.
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
The configuration files in directory directory could not be read or were not found. Please refer to the error log or output for more information.
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
The configuration file dse.ldif in directory directory could not be read or was not found. Please refer to the error log or output for more information.
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
Unknown attribute attribute_name will be ignored
An attempt was made to set an unknown attribute in the configuration file.
Check and correct the attribute name.
4125
Error
The configuration file filename was not restored from backup.
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
Failed to create lock. Cannot register supported SASL mechanism. Server exiting.
This indicates a resource problem on the machine.
Restart the server.
4127
Error
Failed to create lock. Cannot register supported extended operations. Server exiting.
This indicates a resource problem on the machine.
Restart the server.
4128
Error
Could not load configuration file filename.
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
Bad configuration file. Edit the configuration file to correct the reported problems and then restart the server. Server exiting.
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
Cannot copy DSE file filename to path.
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 entry entry_name in file filename is invalid.
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
Cannot parse dse entry entry_name.
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
Cannot write temporary DSE file filename.
System error (file system full, incorrect permissions, etc.)
Check the log file for more information and restart the server.
4134
Error
Cannot backup DSE file filename.
The server cannot write to the specified DSE file.
Check the specified path and ensure that you have the appropriate write permissions.
4135
Error
Cannot rename temporary DSE file filename.
The server cannot rename the specified DSE file.
Check the specified path and ensure that you have the appropriate write permissions.
4136
Error
Invalid plugin action plugin_name.
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
Attempting to delete a child entry whose existence is unknown to the parent. Deletion attempt ignored.
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
Failed to start plugin_name plug-in.
Plug-in dependencies have not been configured correctly.
Check that the dependencies are valid and that they are enabled.
4139
Error
Failed to resolve plug-in dependencies.
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
Could not load symbol symbol_name from library library_name for plug-in plugin_name.
This may be due to:
4152
Error
Unknown plugin type type.
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
Only one instance allowed for plugin type type.
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
UNBIND
Invalid unbind PDU. This is an error in the client code.
Correct the error in the client code.
4159
Error
Bad controls in the UNBIND.
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
ldapu_get_cert_subject_
dn_failsThe server is unable to obtain the subject in the client certificate.
Check the message in the error log for more information.
4163
Error
ldapu_get_cert_issuer_
dn_failsThe server is unable to obtain the certificate issuer of the client certificate.
Check the message in the error log for more information.
4164
Error
Bad BER decoding of an attribute value assertion.
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
BER decoding: found id instead of id for MessageId.
The MessageID tag was not found in the LDAP request.
The request is invalid. Check the application that created the request.
4166
Error
BER decoding: ber_peek_tag returns no Operation tag.
An error occurred while decoding the operation tag.
The request is invalid. Check the application that created the request.
4167
Error
Load library 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
Could not open lockfile filename in write mode.
The specified lock file could not be opened.
Check that the lock file exists and is accessible.
4178
Error
Could not open file filename in mode mode.
The specified file could not be opened.
Check that the file exists and is accessible.
4191
Error
Failed to change user and group identity to that of user.
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 as process process.
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 the process process is importing the database
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.
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 the process process is importing the database
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 the process process is importing the database
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
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
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
Pathname path too long.
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
Cannot determine current directory.
When trying to convert the absolute path, the server was unable to determin the current directory.
Contact Sun ONE Technical Support.
4626
Error
slapi_add_internal: add_values for type type failed.
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
Unable to test the database because it is being used by another slapd process.
Stop the running process and retry.
4629
Error
Unable to create directory.
System error - the directory could not be created.
Check that your file system is valid and retry.
4631
Error
ref_adjust: referrals suppressed (could not get target DN operation or scope from pblock).
Referrals have been suppressed. The server was unable to obtain the target DN and operation structure.
Contact Sun ONE Technical Support.
4633
Error
Suffix to be imported contains encrypted attributes.
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
Security initialisation for attribute encryption failed.
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: unable to read configuration from dn.
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: Failed to retrieve SSL configuration attribute nscertfile from filename
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: Failed to retrieve SSL configuration information (error error): nskeyfile: filename nscertfile: filename
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: NSS initialization failed (error error): path: path certdb prefix: prefix keydb prefix: prefix.
Security initialization error. NSS initialization failed.
Check the NSS configuration and retry.
4741
Error
Security Initialization: NSS initialization failed (error error)
Security initialization error. NSS initialization failed.
Contact Sun ONE Technical Support.
4742
Error
Security Initialization: Failed to retrieve SSL configuration information (error error): nssslSessionTimeout: variable
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: Unable to get token for variable cipher family (error 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: Unable to find slot for variable cipher family (error 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
slapd_get_tmp_dir mkdir(variable) Error: 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: Unable to set SSL export policy (error 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.
4749
Error
Security Initialization: Failed to import NSPR fd into SSL (error 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: Unable to get internal slot (error error)
Security initialization error. The server was unable to obtain the internal slot?
Contact Sun ONE Technical Support.
4751
Error
Security Initialization: Unable to authenticate (error error)
Security initialization error. The server was unable to authenticate.
Contact Sun ONE Technical Support.
4756
Error
None of the ciphers are valid.
The ciphers are invalid.
Check the ciphers and retry.
4757
Error
Config of SSL session cache failed: out of disk space! Make more room in the temp directory and try again.
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
Config of SSL session cache failed (error error).
The configuration of the SSL session cache failed.
Contact Sun ONE Technical Support.
4759
Error
Security Initialization: Failed to enable security on the imported socket (error error)
Security initialization error. The server could not enable security on the imported socket.
Contact Sun ONE Technical Support.
4760
Error
Security Initialization: Failed to enable SSLv3 on the imported socket (error error)
Security initialization error. The server could not enable SSLv3 on the imported socket.
Contact Sun ONE Technical Support.
4761
Error
Security Initialization: Failed to enable TLS on the imported socket (error error)
Security initialization error. The server could not enable TLS on the imported socket.
Contact Sun ONE Technical Support.
4766
Error
Encryption alias not configured.
The encryption alias has not been configured.
Contact Sun ONE Technical Support.
4769
Error
Failed to set SSL client ready for client authentication: certificate db: database returned code return_code (error 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 (no password) (error 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
ldapssl_enable_
clientauth (variable) (error error)SSL error - the server cannot enable client authentication.
Check that the password given to the server is correct.
4774
Error
ldap_simple_bind_s
(variable) (error error)Simple bind over SSL failed. The password may be incorrect.
Check that the password for the DN is correct.
4775
Error
ldap_sasl_bind(""LDAP_SASL_EXTERNAL) (error 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 message
SASL error. The details of the error are logged in the error log.
Check the error log for more information.
4779
Error
Security initialization: Unable to create PinObj (error 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: Unable to authenticate to slot for variable cipher family (error 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
SSL is misconfigured. Client authentication is enabled but no certificate authority is trusted for SSL client authentication.
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
Failed to create context for cipher operation.
NSS context creation failed.
Ensure that a valid certificate is available so that the key may be generated.
4785
Error
Cipher operation failed.
The server was unable to accomplish the cipher operation.
It is likely that the context is incorrect. Restart the server.
4786
Error
Crypto mechanism not supported by this server.
The cryptography mechanism is invalid or unsupported.
Generate a symmetric key for the cryptography mechanism or choose a supported mechanism.
4793
Error
Failed to generate symmetric key.
The server was unable to generate the symmetric key.
Check that a security token is available to the server (as a certificate.)
4795
Error
Failed to map key generation parameters into crypto operation ones.
The server was unable to map the key generation mechanism to the cryptography mechanism.
Restart the server.
4796
Error
Unable to retrieve private key for certificate.
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
Signature failed.
The signature required for attribute encryption failed.
Restart the server.
4798
Error
Key database password was rejected.
The password for the key database has been rejected.
Enter a new password and retry.
4799
Error
Couldn't read key database password.
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 db password was specified.
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
Unable to read key password file from directory.
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
Bad password file syntax: missing `:' preceeding password.
The syntax of the password file is incorrect. The ":" is missing.
Supply a password file with the correct syntax.
4803
Error
Bad token identifier: token.
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
Detected virtual attribute loop in get on entry entry attribute attribute.
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
Out of memory to duplicate a type name.
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
Detected virtual attribute loop in compare on entry entry attribute attribute.
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
Out of memory to allocate a service provider.
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
Out of memory to allocate a service provider handle.
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
Out of memory to create a map for virtual attributes.
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
Out of memory to create a new hash table.
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
Failed to create a new lock for virtual attributes map insert.
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
Multiple backend instances are specified.
More than one backend instance has been specified for the attempted task.
Contact Sun ONE Technical Support.
4995
Error
Cannot perform an import with pre-V3 backend plugin.
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 defined for backend backend
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
Unable to allocate new task for import.
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
Cannot export - backend not found.
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
ldbm2ldif: backend backend export failed (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
No backend instance names are specified.
The database could not be exported because no backend instance names were specified.
Contact Sun ONE Technical Support.
5003
Error
Cannot perform an import with pre-V3 backend plugin.
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 defined for backend backend
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
Unable to allocate new task.
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
Unable to create ldbm2ldif thread for export.
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
db2archive function failed when trying to backup (error error)
The db2archive function failed when attempting to backup.
See the error log for more information and contact Sun ONE Technical Support.
5008
Error
Unable to process backup when no db2archive function defined
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
Cannot perform a backup with pre-V3 backend plugin variable
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
Unable to allocate new task for backup.
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
Unable to create backup thread.
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
Restore failed (error error)
The restore process failed.
See the error log for more information and contact Sun ONE Technical Support.
5014
Error
Cannot perform a restore with pre-V3 backend plugin variable
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
Unable to allocate new task for restore.
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
Unable to create restore thread for restore.
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
db2index function failed when trying to restore (error 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
No db2index function defined for backend backend.
The database could not be indexed because no db2index function was defined for the backend.
Contact Sun ONE Technical Support.
5020
Error
Unable to allocate new task for index.
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
Unable to create index thread.
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
Cannot create task node (error 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
Unable to create global tasks lock.
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
Cannot import. Lookup instance name by suffixes failed.
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
Cannot import. Could not find database for suffix.
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
Cannot import. Backend not found.
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
Cannot import - lookup instance names by suffix failed.
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
Could not find database for suffix.
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
No archive2db function defined.
The database could not be restored because the archive2db function was not defined.
None - this type of database cannot be restored.
5031
Error
Cannot index - backend not found.
The server cannot index the database because the specified backend was not found.
Contact Sun ONE Technical Support.
5034
Error
Incompatible options nsExportReplica=true and dsDecryptAttrs=false: cannot dump replica with encrypted attributes.
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
reslimit_init: slapi_register_object_
extension() failed.The server cannot register an object extension (during resource limit initialization).
Contact Sun ONE Technical Support.
5122
Error
PR_NewRWLock() failed for reslimit.
System error - the server cannot create a new lock for the resource limit.
Contact Sun ONE Technical Support.
5123
Error
error: Resource limit initialization failed.
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
error: slapi_get_object_
extension() returned NULLThe server could not obtain the object extension (for the resource limit).
Contact Sun ONE Technical Support.
5126
Error
error: parameter error (attribute already registered)
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
error: parameter error
A parameter error occurred when registering a new resource to be tracked.
5127
Error
error: parameter 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
error: unknown handle handle
Parameter error. The handle used to identify a resource is unknown.
Contact Sun ONE Technical Support.
5129
Error
Cannot malloc bytes.
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
malloc of bytes bytes failed; errno 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
realloc of bytes bytes failed; errno 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
calloc of bytes bytes failed; errno 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
strdup of chars chars failed; errno 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_bvdup of bytes bytes failed; errno 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
The entry entry in the configfile filename was empty or could not be parsed.
An entry in the configuration file was empty or could not be parsed.
Check the entry syntax in the configuration file.
5250
Error
Invalid value
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
Cannot set error log filename.
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
Undefined value for errorlog level.
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
Bad value for nsslapd-maxdescriptors.
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
Ignoring attribute (since -d option was given on the command line) nsslapd-errorlog-level.
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
The plugin entry entry in the configfile filename was invalid.
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
Convert LDIF entry into LDAP entry fast method. Error: entry has no dn.
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
str2entry_dupcheck: entry has no dn.
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
Error occurs while removing attribute values. Possible existing duplicate value for attribute type attribute found in entry entry.
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
str2entry_dupcheck: unexpected failure constructing the value tree.
The server failed to add a value to the value tree.
Check the error log for more information.
5395
Error
Attribute `nscpEntryWSI' can only be computed by root user.
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
Registration of extension failed.
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
Could not find parent node for entry entry. Node parent is defaulting to root node.
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
Node node is either a 'backend' or 'referral on update' node therefore it must define a backend (attribute 'nsslapd-backend').
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
Node node is either a 'referral' or 'referral on update' node therefore it must define a referral (attribute 'nsslapd-referral').
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
Cannot load distribution plugin lib library for node node.
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
Node node wants to define a distribution plugin but either nsslapd-distribution-
plugin' or 'nsslapd-distribution-
funct' attribute is missing in the configuration file (dse.ldif).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
Could not create mapping tree node for entry entry.
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
Cannot find distribution function function in distribution plugin lib library for node node.
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 were found in the directory directory_name.
No schema files are present in the schema directory.
Restore the default schema files from a backup or CD image.
5893
Error
Entry entry required attribute objectclass is missing.
The specified entry was added without an objectclass attribute.
Check the application that added the entry.
5894
Error
Entry entry has unknown objectclass.
The entry was added or modified with an unknown objectclass.
Check the application that added or modified the entry.
5895
Error
Entry entry single-valued attribute has multiple values.
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
Entry entry attribute attribute required by objectclass objectclass is missing.
The entry that was added or modified is missing a required attribute.
Check the application that added or modified the entry.
5897
Error
Entry entry attribute attribute is not allowed.
The entry that was added or modified contains an invalid attribute.
Check the application that added or modified the entry.
5900
Error
Missing value for objectClasses attribute.
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
Replication session aborted for agreement agreement_name because consumer replica is disabled.
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
Pending changes: error value.
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
Bad Window size value for agreement agreement_name.
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
Bad Group size value for agreement agreement_name.
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
Bad Compression Level value for agreement agreement_name.
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
Modification of attribute_name attribute is not allowed - agreement agreement_name.
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
Failed to update flag to force 5.1 Replication protocol for agreement agreement_name.
The replication agreement is being stopped.
Wait until the agreement has been stopped and retry.
8202
Error
Unknown replication agreement
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
Refusing to update partial replication checksum for agreement agreement_name permission denied.
The server received an update operation that is permitted for internal operations only.
Check the client that sent the forbidden update operation.
8212
Error
Failed to update replication schedule for agreement agreement_name.
8213
Error
Failed to update Partial Replication Configuration for agreement agreement_name. The agreement needs to be disabled first.
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 not started for agreement agreement_name.
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
Partial replication pointed to by this entry has been modified. Please update the current configuration on this supplier or re-initialize consumer accordingly.
The partial replication configuration has been modified.
Update the current configuration on the supplier, or reinitialize the consumer.
8218
Error
Replication protocol v5.0 not supported for consumer.
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
Could not parse update vector for replica replica_name. The replica must be reinitialized.
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
Too much time skew between replicas for [consumer:port]
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
Failed and requires administrator action.
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
Replica_write_partial_
repl_checksum: failed to update partial repl checksum with value value for replica replica. LDAP 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
replica_write_last_init_
time: failed to update last init timestamp with value value for replica replica. LDAP 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
Unable to read user schema.
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
Bind error for agreement: .agreement.
A replication protocol bind error has occurred.
Check that the consumer is up and running.
8229
Error
Failed to start a total update session.
The server was unable to start a total replication update session.
Check that the consumer is up and running.
8230
Error
Failed to create directory for changelog changelog error 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
Removal of changelog file filename failed.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8234
Error
Changelog is not initialized.
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
Failed to open changelog.
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
Change record has an invalid data version
A change record in the database has an invalid version number.
8242
Error
Change record has an invalid operation type.
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
Failed to begin transaction for trimming DB 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
Failed to abort transaction for trimming DB 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
Failed to commit transaction for trimming DB 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
Failed to begin transaction for writing changelog changelog RUV DB 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
Failed to abort transaction for writing changelog changelog RUV DB 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
Failed to commit transaction for writing changelog changelog RUV DB 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
Writing the changelog changelog RUV in the file filename failed DB 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
Failed to begin transaction for writing change count entry DB 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
Failed to abort transaction for writing change count entry DB 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
Failed to commit transaction for writing change count entry DB 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
Failed to write change count entry to the file filename DB 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
Failed to begin transaction for writing change operation DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8257
Error
Failed to abort transaction for writing change operation DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8258
Error
Failed to commit transaction for writing change operation DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8259
Error
Failed to write change operation with CSN number. DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8260
Error
Failed to create cursor for retrieving first change DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8261
Error
Failed to retrieve first change DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8262
Error
Failed to retrieve the next change DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8263
Error
Failed to delete the current change DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8264
Error
Failed to position in db at CSN number. DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8266
Error
Failed to open changelog file for replica replica. DB error.
An internal database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8267
Error
Failed to retrieve change count from changelog for replica replica.
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
Failed to close changelog file filename. DB error.
A database error occurred.
Check the corresponding database error code, and take action according to the database problem.
8271
Error
Consumer replica replica_name has an invalid RUV.
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
Replication session aborted for agreement agreement_name because consumer replica is disabled.
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
Failed to start Replication Session for suffix suffix_name.
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
Failed to start Replication Session for suffix suffix_name.
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
Failed to start Replication Session for suffix suffix_name.
The consumer is configured as a legacy replica and can therefore not accept multimaster replication.
Correct the replication topology.
8279
Error
Failed to start Replication Session for suffix suffix_name.
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
Failed to start Replication Session for suffix suffix_name.
The consumer is not yet initialized and can therefore not accept changes.
Initialize the consumer, either online or offline.
8282
Error
Failed to start Replication Session for suffix suffix_name.
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
Failed to start Replication Session for suffix suffix_name.
The consumer replica is already busy with a replication session.
Wait and try later. If this error persists, restart the server.
8284
Error
Failed to start Replication Session for suffix suffix_name.
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
Bad Group Packet size value for agreement agreement_name.
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
Bad Concurrency Level value for agreement agreement_name.
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
Total update of a consumer consumer with an empty database is not allowed.
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 occurred on the consumer side: consumer with error 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
_cl5TrimFile: Removing changelog file filename as it belongs to an unexisting replica.
The changelog file contains data changes from a replica that has been unconfigured.
No action is necessary - this is an informational message.
8302
Error
Decoding replicate entry failed.
A protocol error occurred. The entry was incorrectly encoded.
Check the error code and contact Sun ONE Technical Support.
8303
Error
Failed with error code error.
Schema replication failed locally on the consumer.
Check error code and contact Sun ONE Technical Support.
8307
Error
Failed to import database entry.
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
Invalid change_operation: entry_UUID entry CSN CSN_value.
A badly formed change was received.
Contact Sun ONE Technical Support.
8311
Error
Unexpected operation sequence number value (expecting value).
An internal error occurred in the sequencing of replicated operations.
Contact Sun ONE Technical Support.
8312
Error
Replay of pending changes failed returning.
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
[S] Bind failed with response: error_code.
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
[S] Start Failed with response: error_code.
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
[S] End Failed with response: error_code.
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
PR_Accept() failed error variable (variable)
The TCP port to which you are attempting to bind is already in use.
12290
Error
PR_GetIPNodeByName() failed errno variable (variable)
There is an error in the naming service configuration.
Add listen host (variable) to the naming service.
12291
Error
No port to listen on.
The LDAP port is missing from the configuration.
Add an LDAP port to the configuration file or use the command line.
12292
Error
Unable to create time thread (variable - variable) - shutting down.
System error, probably due to a resource problem.
Free up resources on the machine and restart the server.
12293
Error
Too many open file descriptors - not listening on new connection.q
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
Not enough descriptors to accept any additional connections.
There are insufficient file descriptors to accept new connections. This may be because:
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
Cannot initialize lock. The server is terminating
Probably due to a resource problem on the system.
Restart the directory server.
12296
Error
Cannot create lock. The server is terminating.
Probably due to a resource problem on the system.
Restart the directory server.
12297
Error
Cannot create condvar. The server is terminating.
Probably due to a resource problem on the system.
Restart the directory server.
12298
Error
PR_SetNetAddr(PR_IpAddrAny) failed errno
Internal error.
Contact Sun ONE Technical Support.
12299
Error
PR_EnumerateHostEnt() failed.
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
gethostname host failed error error (variable).
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
NSS Initialization failed.
The server was unable to initialize the security library.
Contact Sun ONE Technical Support.
12302
Error
Shutting down due to possible conflicts with other slapd processes.
More than one directory server is running.
Stop the directory servers that should not be running.
12304
Error
Shutting down due to inability to find user in system account database.
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
ber encoding failed.
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
Call to _base64Decode fails.
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
connection_push_back_
data has failed.The request has been aborted due to an internal error.
Please contact Sun ONE Technical Support.
12320
Error
Invalid arguments: entry.
Configuration error. The server failed to obtain the frontend configuration entry.
Correct the frontend configuration entry and restart the server.
12321
Error
Failure during frontend sanity check.
Configuration error. The server failed the frontend sanity check.
Correct the frontend declaration and restart the server.
12322
Error
Start parse of DSML operation fails, operation aborted.
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
Could not store worker context in Batch operation.
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
Can't register HTTP port port.
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
Can't register HTTPS port port.
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
Max size value of parser pool is lower than current size value.
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
Cannot create XMLCh to UTF8 Transcoder.
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
Can't initialize DSML Worker.
Internal error. The server failed during the initialization of the DSML worker.
Please contact Sun ONE Technical Support.
12329
Error
Extra datacopy failed.
A request has not been processed due to a connection closure.
Check the connection and retry.
12330
Error
Operation Key creation for HTTP context failed.
An internal memory management error has occurred.
Please contact Sun ONE Technical Support.
12332
Error
HTTP/DSML frontend initialization failed.
Initialization error. The server failed to set the plug-in functions.
Correct the frontend configuration and restart the server.
12333
Error
HTTP frontend instance creation failed.
Internal error. The server failed to instantiate the frontend plug-in.
Please contact Sun ONE Technical Support.
12334
Error
Unknown internal error has been raised.
Unknown internal error.
Please contact Sun ONE Technical Support.
12335
Error
Error with config attribute attribute.
Configuration error. A configuration attribute is invalid.
Correct the specified attribute and restart the server.
12336
Error
Invalid attribute syntax.
Configuration error. The syntax of a configuration attribute is invalid.
Correct the syntax of the specified attribute and restart the server.
12337
Error
System I/O error.
Internal I/O error.
Please contact Sun ONE Technical Support.
12338
Error
Memory allocation error.
System error, probably due to insufficient resources (lack of memory).
Please contact Sun ONE Technical Support.
12339
Error
Memory usage error.
Memory management system error.
Please contact Sun ONE Technical Support.
12340
Error
DSML schema location is not defined.
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
DSML schema URN is not defined.
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
SOAP schema location is not defined.
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
SOAP schema URN is not defined.
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
Lock for concurrent access to _freeList does not exist.
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
No more parser in the pool, operation aborted.
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
Bad Dsml request - SOAP fault code.
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
Error with secure identity method.
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
httpBasicOnly12348
Error
Exception raised when calling XMLString::transcode.
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
Bad Dsml request -
SOAP error message.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
Parse of fake request fails 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-
dsmlschemalocation12354
Error
Parse of fake request fails.
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
The XML schema file filename is missing.
Configuration error: an XML schema is missing.
Insert the missing schema in the specified location and restart the server.
12356
Error
SOAPAction header is missing.
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
PR_Bind() on address host port port failed.
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 process FAILED. The database is not recoverable.
Database recovery has failed.
This is a serious database error. Please contact Sun ONE Technical Support.
20492
Error
Failed to create thread (NSPR error).
The Netscape Portable Runtime (NSPR) was unable to create one or more threads. This may be due to insufficient resources.
- 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.
- 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
Instance instance_name does not have the expected version version_number.
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
dblayer_instance_
start_fail: backend instance_name has no IDs left. Database must be rebuilt.The internal NEXTID counter has reached the limit.
Rebuild the database.
20501
Error
Serious failure in dblayer_txn_begin. Err=value.
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
Serious failure in dblayer_txn_commit. Err=value.
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
Serious failure in dblayer_txn_abort. Err=value.
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
Serious failure in deadlock detect (aborted at address). Err=value.
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
Serious failure during database checkpointing. Err=value.
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
Serious failure during trickle. Err=value.
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
Failed to create guardian file. Database corruption possible.
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
Database database is corrupt and being marked unavailable. Either re-import or delete the database.
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
Failed to write guardian file. Database corruption possible.
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
Failed to delete guardian file. Database corruption possible.
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
ldbm backend instance: nextid not initialized.
This is a software problem.
Please contact Sun ONE Technical Support.
20738
Error
ldbm backend instance: FATAL ERROR: backend name has no IDs left. DATABASE MUST BE REBUILT.
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
ldbm backend instance: WARNING: backend backend_name may run out of IDs.
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
Numsubordinates assertion failure.
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
ldbm_back_seq : id2entry err 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
ldbm_back_seq: could not open index file for attribute attribute.
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
compare_entries db err error_number while loading entry entry.
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
start : Resource limit registration failed.
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
start : Failed to init database err=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
start : Failed to start databases err=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
Database version mismatch (expecting version but found version in directory directory.)
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
VLV : can't get index file file (err 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
vlv_build_idl: can't follow db cursor (err error).
The database is incoherent.
Rebuild the database, using db2ldif, then ldif2db.
20754
Error
nomem: wants value key value data.
The system is out of memory
Check the configuration.
20755
Error
VLV : can't get index file file (err 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
VLV : couldn't get cursor (err 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
vlv_filter_candidates: Candidate id not found err=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
vlv_trim_candidates_
byvalue: Candidate ID id not found err 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
vlv find index: err error.
The server could not locate an index used in virtual list view (VLV).
Check the VLV configuration.
20760
Error
Couldn't generate valid filename from Virtual List View Index Name name. Need some alphabetical characters.
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
Add: maximum ID reached cannot add entry to backend backend.
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
Add: attempt to index entry failed.
The server was unable to index the entry being added.
Check the previous errors in the log for additional information.
20763
Error
Retry count exceeded in add.
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
Line line_number: Fatal Error: Failed to initialize attribute structuring.
The server was unable to initialize the attribute structure. This is probably a memory error.
Check the available memory.
20765
Error
Attempt to delete a non-tombstone entry entry.
An attempt was made to delete an entry that was not a tombstone entry.
Please contact Sun ONE Technical Support.
20766
Error
Attempt to tombstone again a tombstone entry entry.
An attempt was made to tombstone an entry that is already a tombstone entry.
Please contact Sun ONE Technical Support.
20768
Error
Retry count exceeded in delete.
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
Retry count exceeded in modify.
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
Retry count exceeded in modrdn.
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
modrdn: could not add new value to index err=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
Database error 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
Null referral in entry.
The candidate entry has a NULL referral.
Update the referral in the entry or remove the ref attribute.
20777
Error
Filter bypass error on entry entry.
The server failed to bypass the filter test.
Please contact Sun ONE Technical Support.
20778
Error
Unable to add config entries to the DSE.
The server was unable to add configuration entries to the DSE.
Ensure that there is no inconsistency within the entries.
20779
Error
ERROR: ldbm plugin unable to read cn=config.
The configuration information under cn=config could not be read.
Please contact Sun ONE Technical Support.
20780
Error
ERROR: ldbm plugin unable to read attribute nsslapd-instancedir from cn=config.
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
Invalid value for attribute. Must be between 0 and 100.
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 attribute20787
Error
Attribute can't be modified while the server is running.
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
Value value for attribute attribute is not a number.
The attribute value must be numerical.
Ensure that the attribute has a numerical value.
20789
Error
Value value for attribute attribute is greater than the maximum value.
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
Value value for attribute attribute is less than the minimum value.
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
Value value for attribute attribute is outside the range of representable values.
The value specified for the attribute is outside the permissible range.
Ensure that the attribute value is within the representable range.
20792
Error
Could not set instance config attr attribute to value.
The server failed to set the instance configuration attribute.
Ensure that both the syntax and the value of the attribute are correct.
20793
Error
Could not retrieve ldbm config info from DSE.
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
ldbm: instance instance does not exist!
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
ldbm: instance is in the middle of a task. Cancel the task or wait for it to finish then try again.
The specified instance is currently processing a task.
Cancel the current task or wait for it to finish and retry.
20797
Error
ldbm: modify attempted to change the root suffix of a backend (which is not allowed).
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
System info mismatch (expecting variable but found variable in directory directory_name).
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
Failed to read server system information
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
Disk full under variable.
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
Cannot parse entry from database for id id string =variable.
Database corruption.
Restore the database from a backup.
20997
Error
Inconsistent database: entrydn for entry refers to id id missing from id2entry.
Database corruption.
Restore the database from a backup.
21005
Error
Could not open index index for update.
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
Could not open index index for range query.
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
Backend initialization failed: could not allocate a lock.
Insufficient system resources.
Check the available memory.
21009
Error
Backend initialization failed: could not allocate a condition variable.
Insufficient system resources.
Check the available memory.
21010
Error
Backend initialization failed: could not set plugin functions.
Insufficient system resources.
Check the available memory.
21011
Error
Backend initialization failed on instance instance: could not allocate a lock.
Insufficient system resources.
Check the available memory.
21012
Error
Backend initialization failed on instance instance: could not allocate a condition variable.
Insufficient system resources.
Check the available memory.
21016
Error
Failed to create ancestorid index.
An index could not be created on the disk.
Check the error log for previous messages that should isolate the problem.
21017
Error
Incomplete parentid index suspected (value extra keys in ancestorid)
Database corruption.
Rebuild the parentid index or restore the database from a backup.
21018
Error
Entry cache initialization failed: could not allocate lock.
Insufficient system resources.
Check the system free memory.
21022
Error
variable is configured to use more than the available physical memory.
The cachesize as defined in the configuration file exceeds database limits.
Lower the value of the cachesize attribute in the configuration file.
21023
Error
Index index is inconsistent.
Database corruption.
Rebuild the affected index or restore the database from a backup.
21249
Error
Failed to encrypt some attribute inside the entry entry before writing it to the database.
The server was unable to encrypt the specified attribute inside the entry.
Check the attribute encryption configuration.
21250
Error
Failed to decrypt some attribute inside the entry entry when when reading it from the database.
The server was unable to decrypt the specified attribute inside the entry.
Check the attribute encryption configuration.
21251
Error
Encrypted value's prefix doesn't match the corresponding algorithm algorithm in the attribute encryption configuration.
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
Server didn't find plug-in for algorithm algorithm.
The server was unable to locate the plug-in for the specified algorithm.
Enable the encryption plug-in.
21253
Error
Failed to encrypt index keys.
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
Attribute encryption: failed to encrypt/decrypt attribute attribute with algorithm algorithm.
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
Encryption plugin (plugin): failed to encrypt.
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
Encryption plugin (plugin): failed to decrypt.
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
Bulk import process failed: state=state, error code=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
filter_sp_replace_or_add_checksum: failed to update attribute attribute from entry entry; LDAP error - errnum.
The attribute filterspconfchecksum could not be updated with a new value.
32769
Error
Unable to allocate memory. Cannot start Roles plugin.
There is not enough memory to register the roles plug-in into the service provider broker.
Restart the server.
32770
Error
Unable to allocate memory. Cannot start Roles plugin.
There is not enough memory to register the nsrole attribute.
Restart the server.
32771
Error
Unable to allocate memory. Cannot create Roles cache.
This error indicates a resource problem on the machine.
Restart the server.
32772
Error
Lock creation failed. Cannot create Roles cache.
This error indicates a resource problem on the machine.
Restart the server.
32773
Error
Conditional variable creation failed. Cannot create Roles cache.
This error indicates a resource problem on the machine.
Restart the server.
32774
Error
Thread creation failed. Cannot create Roles cache.
This error indicates a resource problem on the machine.
Restart the server.
32775
Error
Failed to get objectclass from entry.
The specified entry does not contain an objectclass.
Check the entry and add the required objectclass.
32776
Error
Unsupported operation operation.
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
Maximum number of nested roles exceeded (max value current value). Not retrieving roles from entry entry. Probable circular definition.
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
Nested role entry does not exist.
The entry corresponding to the DN does not exist.
Check the role definition.
32780
Error
Cannot initialize Roles plugin.
The server is unable to update the pblock parameters.
Restart the server.
32781
Error
Unknown role type type.
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
Could not allocate PB.
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 PBG error.
Internal error.
Please contact Sun ONE Technical Support.
33027
Error
Internal search error in Attribute Uniqueness plugin.
Internal error.
Please contact Sun ONE Technical Support.
33028
Error
Internal PB error.
Internal error.
Please contact Sun ONE Technical Support.
33029
Error
Could not find plugin argument number.
Memory corruption or invalid configuration.
Check the plug-in configuration. If it is valid, please contact Sun ONE Technical Support.
33030
Error
Could not find plugin arguments.
Memory corruption or invalid configuration.
Check the plug-in configuration. If it is valid, please contact Sun ONE Technical Support.
33031
Error
Could not find a valid argument.
Configuration error.
Check the plug-in configuration parameters in the dse.ldif file. Make sure that the syntax and values are correct.
33032
Error
ADD/MOD/MODRDN: unable to get replication flag.
Internal error.
Please contact Sun ONE Technical Support.
33033
Error
ADD/MOD/MODRDN: unable to get target DN.
Internal error.
Please contact Sun ONE Technical Support.
33034
Error
Unable to get entry data.
Internal error.
Please contact Sun ONE Technical Support.
33035
Error
Could not get MODIFY data.
Internal error.
Please contact Sun ONE Technical Support.
33036
Error
Error while retrieving mod values.
Internal error.
Please contact Sun ONE Technical Support.
33037
Error
Unable to get new superior DN.
The new superior DN does not exist.
Check the validity of the intended operation.
33038
Error
Unable to get new DN.
The new rdn is invalid or is not correctly specified.
Check the validity of the intended operation.
33039
Error
Unable to allocate a new entry.
Internal error.
Please contact Sun ONE Technical Support.
33040
Error
ADD parameter untagged: 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
ADD result result.
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
MODIFY result result.
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
MODRDN bad rdn value=value.
Internal error.
Please contact Sun ONE Technical Support.
33044
Error
MODRDN result result
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
NSUniqueAttr_Init Error: error
Configuration error.
Check the plug-in configuration parameters in the dse.ldif file.
33793
Error
cos_cache_init: cannot create mutexes
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
cos_cache_init: cannot register as service provider
The server was unable to register a virtual attribute service provider.
Free up resources on the machine and restart the server.
33795
Error
cos_cache_init: PR_CreateThread failed
The server was unable to create a CoS thread.
Free up resources on the machine and restart the server.
33796
Error
cos_cache_create: failed to cache the schema
The server was unable to create the CoS schema cache.
33797
Error
cos_cache_create: failed to index cache
The server was unable to index the CoS cache.
33798
Error
COS memory allocation failure: variable
The server was unable to allocate memory for the CoS cache.
33799
Error
cos_cache_build_
definition_list: failed to find suffixes in the rootDSE.The server was unable to read the suffix list from the rootDSE entry.
Restart the server.
33801
Error
COS Definition error 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
cos_cache_add_dn_
tmpls: could not cache cos template variableThe server was unable to add the specified template to the CoS cache.
33803
Error
cos_cache_query_atr: failed to get entry dn
The server was unable to locate the dn of the target entry during a search operation. This error should not occur under normal circumstances.
33804
Error
COS failed to get objectclass from entry (entry)
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.
33806
Error
cos_start: failed to initialise
The server was unable to start the CoS plug-in. This is probably due to a memory problem.
33807
Error
cos_init: failed to register plugin
The server was unable to register the CoS plug-in. This is probably due to a memory problem.
33808
Error
COS Definition error (no DN)
There is an error in the definition of the specified CoS.
Check and correct the CoS definition.
33809
Error
cos_cache_change_notify: failed to get dn of changed entry
The server was unable to obtain the dn of the target entry during an update operation. This error should not occur under normal circumstances.
34817
Error
ACL library initialization failed.
The server is unable to initialize the ACL plug-in. This is usually an indication of memory problems.
34818
Error
ACL failed to allocate locks.
The server is unable to allocate mutex or reader/writer locks for the ACL plug-in at initialization time.
34819
Error
ACL malloc fail: 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
ACL internal error: error.
This is an internal error and should not occur under normal circumstances.
34822
Error
Unable to initialize the plugin: plugin_name
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
Error: ACIs not deleted from entry.
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
ACL internal init fail: 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
ACL error adding aci: aci.
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: 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: failed to make filter for string string.
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 PARSE ERR(rv=error_code): aci.
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
Can't add the rest of the acls for entry: entry after delete.
The server failed to update ACIs in the specified entry, when an ACI was deleted.
34831
Error
ACL failed to allocate locks.
The server is unable to allocate mutex or reader/writer locks for the ACL plug-in at operation time.
- Free up resources on the machine.
- Attempt the LDAP operation again.
- Restart the server.
34832
Error
Operation extension allocation failed.
The server is unable to get/create an operation extension structure at operation time.
- Free up resources on the machine.
- Attempt the LDAP operation again.
- Restart the server.
34834
Error
acl_get_aclpb: Invalid aclpb type
An invalid ACL operation extension was found. This is an internal error and should not occur under normal circumstances
- Attempt the LDAP operation again.
- Restart the server.
- Copy the errors log file and contact Sun ONE Technical Support.
34835
Error
ACLPB parameter parameter value value exceeded allowed value value.
This is an internal error and should not occur under normal circumstances.
- Attempt the LDAP operation again.
- Restart the server.
34838
Error
ACL parent[ ] exceeded the levels limit max_limit: function.
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
collation_unlock: PR_ExitMonitor (variable)=variable; collation_monitor = variable
An error occurred while releasing the collation lock.
Restart the server.
36866
Error
collation_init: PR_NewMonitor failed
An error occurred while creating the collation lock.
Restart the server.
36867
Error
variable: line line_no: missing directory name in directory directory (ignored)
No argument was provided for the NLS parameter.
Check the configuration variable.
36868
Error
variable: line line_no ignored: only variable arguments (expected collation language country variant strength decomposition oid...)
Insufficient arguments were provided for the collation parameter.
Check the configuration variable.
36869
Error
variable: line line_no: strength value not supported (will use 2)
An invalid value was specified for the collation strength.
Check the configuration variable.
36870
Error
variable: line line_no: decomposition value not supported (will use 2)
An invalid value was specified for the collation decomposition.
Check the configuration variable.
36871
Error
Too many tokens (max max_tokens)
Too many items have been specified on the configuration line.
Check the configuration variable.
36872
Error
Could not open config file filename - absolute path.
The server was unable to open the collation configuration file.
Check the path to the collation configuration file.
36873
Error
variable: line line_no: bad config line (ignored)
The server was unable to parse a line in the collation configuration file.
Check the collation configuration file.
36874
Error
Unable to retrieve slapd configuration pathname; using default.
The location of the collation configuration file was not provided to the plug-in.
Check the path to the collation configuration file.
37121
Error
Not enough pattern space.
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
re_comp filter failed.
The regular expression being constructed for the substring filter could not be compiled.
Check the substring filter being provided to the server.
37123
Error
dn_assertion2keys_ava: unknown ftype.
A filter containing an unknown type was provided to the server.
Check the filter being provided to the server.
37377
Error
statechange_init: failed to register plugin.
The state change plug-in could not be registered with the server.
Restart the server.
37378
Error
statechange: failed to create lock.
The server was unable to create a mutex for the state change subsystem.
Restart the server.
37379
Error
statechange: failed to publish state change interface.
The server was unable to publish the interface to the state change plug-in API.
Restart the server.
37380
Error
statechange_post_op: failed to get dn of changed entry.
The server was unable to determine the DN of the modified entry.
Restart the server.
37633
Error
Only one pass through plugin instance can be used
An attempt was made to configure multiple instances of the passthrough authentication plug-in.
Check the pass-through authentication plug-in configuration.
37634
Error
No pass through servers found in configuration (at least one must be listed)
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
Server parameters should be in the form "maxconnections maxconcurrency timeout ldapversion connlifetime" (got "error")
The set of parameters specified for the remote server was invalid.
Check the pass-through authentication plug-in configuration.
37636
Error
LDAP protocol version should be version or version (got error)
The LDAP version specified for the remote server was invalid.
Check the pass-through authentication plug-in configuration.
37637
Error
Maximum connections must be greater than zero (got 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
Maximum concurrency must be greater than zero (got error)
The maximum concurrency is specified as less than or equal to zero.
Check the pass-through authentication plug-in configuration.
37639
Error
Unable to parse LDAP URL "url" (error)
An error occurred while parsing the LDAP URL.
Check the pass-through authentication plug-in configuration.
37640
Error
Missing suffix in LDAP URL "url"
The pass-through suffix was not specified in the LDAP URL.
Check the pass-through authentication plug-in configuration.
37641
Error
Unable to parse suffix string "suffix" within variable
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
Suffix "suffix" is handled by a database backend and therefore will not be subject to pass through authentication
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
ldap_charray_add() failed when building suffix list
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 found
No active suffixes could be located in the local server.
Check the server configuration and/or restart the server.
37646
Error
passthruauth_init failed
The pass-through authentication plug-in could not be registered.
Restart the server.
37647
Error
Unable to get arguments
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
configuration failed (variable)
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
Operation not handled (unable to retrieve bind parameters)
The server was unable to determine the required information regarding the bind operation.
Check the bind request.
37650
Error
error
The server was unable to retrieve the set of controls associated with the bind request.
Check the bind request.
37651
Error
error
The server was unable to set the DN or authentication type associated with this connection.
Restart the server.
37889
Error
referint_postop_init failed
A failure occurred while registering the referential integrity plug-in.
Restart the server.
37890
Error
referint_postop_del: could not get parameters
The server was unable to retrieve the required information about a delete operation.
Check the delete request.
37891
Error
referint_postop failed to get argc
The server was unable to determine the number of parameters to the referential integrity plug-in.
Restart the server.
37892
Error
referint_postop failed to get argv
The server was unable to retrieve the parameters associated with the referential integrity plug-in.
Restart the server.
37893
Error
referint_postop_del args are NULL
No arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37894
Error
referint_postop insufficient arguments supplied
Insufficient arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37895
Error
referint_postop_modrdn: could not get parameters
The server was unable to retrieve the required information about a modrdn operation.
Check the delete request.
37896
Error
referint_postop failed to get argc
The server was unable to determine the number of parameters to the referential integrity plug-in.
Restart the server.
37897
Error
referint_postop failed to get argv
The server was unable to retrieve the parameters associated with the referential integrity plug-in.
Restart the server.
37898
Error
referint_postop_modrdn args are NULL
No arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37899
Error
referint_postop_modrdn insufficient arguments supplied
Insufficient arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37900
Error
update_integrity required config file arguments missing
No arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37901
Error
referint_postop search (base=base filter=filter) returned error error.
An error occurred while searching for references to the deleted/renamed entry.
- Check the error log for details of the error.
- Restart the server.
37902
Error
referint_postop failed to get argc
The server was unable to determine the number of parameters to the referential integrity plug-in.
Restart the server.
37903
Error
referint_postop failed to get argv
The server was unable to retrieve the parameters associated with the referential integrity plug-in.
Restart the server.
37904
Error
args were null in referint_postop_start
No arguments were provided for the referential integrity plug-in.
Check the configuration of the referential integrity plug-in.
37905
Error
referint_postop_start PR_CreateThread failed.
The server was unable to create the thread to perform integrity updates.
Restart the server.
37906
Error
referint_postop_start insufficient arguments supplied
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
referint_thread_func could not get args
The server was unable to retrieve the parameters associated with the referential integrity plug-in.
Restart the server.
37908
Error
referint_postop_close could not delete filename
The referential integrity log file could not be deleted.
Check the permissions on the specified file and restart the server.
37909
Error
referint_postop could not open integrity log filename
The referential integrity log file could not be opened for writing.
Check the permissions on the specified file and restart the server.
37910
Error
referint_postop could not write integrity log: line length exceeded. It will not be able to update references to the entry entry.
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
writeintegritylog: PR_Write failed : The disk may be full or the file is unwritable :: NSPR error - error.
The server was unable to write data to the integrity log file.
- Check the integrity log file.
- Check the filesystem status.
37912
Error
writeintegritylog: failed to close the file descriptor prfd; NSPR error - error.
An error occurred while closing the integrity log file.
- Check the integrity log file.
- Check the filesystem status.
38913
Error
The default SASL configuration entry could not be read or was not found in the dse.ldif file. It is mandatory.
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
Can't find localhost name.
The local host name is absent from the naming service.
Add the local host name to the naming service.
38918
Error
Sasl initialization failed.
Incorrect or missing information in the SASL configuration entry in the dse.ldif file (under cn=sasl.)
- Check that the entry exists in the configuration file.
- Check that the information in the configuration entry is valid (authentication mechanism names are correct.)