Chapter 9 Directory Server Error
Log Message Reference (Sun Directory Server Enterprise Edition 7.0 Troubleshooting Guide)
&& Chapter 9 Directory Server Error
Log Message ReferenceSun Directory Server Enterprise Edition 7.0 Troubleshooting GuideChapter&9 Directory Server Error
Log Message Reference
This chapter lists messages logged by Directory Server. While this
list is not exhaustive, the information presented in this chapter serves as
a good starting point for resolving common problems.
This chapter includes the following sections:
Log messages are defined according to their severity.
The error is severe. Immediate action should be taken to avoid
the loss or corruption of directory data.
Action should be taken at some stage to prevent a severe error
occurring in the future.
An informative message, usually describing server activity.
No action is necessary.
Note & When using the error log for debugging, increase the log level
progressively until the debugging data you need becomes evident in the log.
Do not enable error logging for all Directory Server components at once, especially
on a production system, to avoid severely impacting performance.
the case of internal errors, plug-in writers should check their parameters
to slapi_*() functions first.
Common Error Codes
This section describes the error codes displayed in the instance-path/logs/errors log and the appropriate
action to take should these errors occur.
4104: 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 Technical Support.
4105: 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 Technical Support.
4107: 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. Refer to the attribute description for the acceptable value range.
4108: 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: The given file filename could
not be opened for reading.
The server is unable to open the specified configuration
Check that the file exists and that it has
the appropriate access rights.
4110: Could only read value of value bytes from configuration file filename.
The server is unable to read the specified configuration
Check that the file exists and that it has
the appropriate access rights.
4111: 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
Check that the password storage scheme SSHA
exists in the configuration file. If it is not present, add it.
4112: 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: 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: No password storage scheme plug-ins defined
in the configuration.
No encoding scheme was found in the configuration
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: 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: 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: 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.
Refer to the log files for more information.
4123: 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 Directory Server configuration
file. The specific cause for the error is logged in the log files.
Refer to the log files for more information.
4124: 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: 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: Failed to create lock. Cannot register supported
SASL mechanism. Server exiting.
This indicates a resource problem on the machine.
Restart the server.
4127: Failed to create lock. Cannot register supported
extended operations. Server exiting.
This indicates a resource problem on the machine.
Restart the server.
4128: 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. Refer to the error log
for more details.
4129: Bad configuration file. Edit the configuration
file to correct the reported problems and then restart the server. Server
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: 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: 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: 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: Cannot write temporary DSE file filename.
System error (file system full, incorrect permissions,
Check the log file for more information and
restart the server.
4134: Cannot backup DSE file filename.
The server cannot write to the specified DSE
Check the specified path and ensure that
you have the appropriate write permissions.
4135: 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: 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: 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: 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: Failed to resolve plug-in dependencies.
An error occurred while resolving dependencies
(usually the consequence of an earlier problem such as a disabled plug-in,
Check that the dependencies are valid and
that they are enabled.
4140: Could not load symbol symbol_name from
library library_name for plug-in plugin_name.
This may be due to:
Incorrect configuration of the plug-in entry
A plug-in library missing or in the wrong location
The expected symbol corresponding to the init function
not found in the plug-in library
Perform the following steps:
Check the plug-in configuration.
Check that the library path and the init function
name are correct.
4152: 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: 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: UNBIND
Invalid unbind PDU. This is an error in the
client code.
Correct the error in the client code.
4159: 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.
4160: Cannot retrieve internal operation result for
search operation (&operation& subtree subtree)
While performing an internal search, Directory
Server could not retrieve the operation from the parameter block.
Contact Sun Technical Support.
4161: Cannot allocate pblock for an internal search
(&baseDN& scope filter)
While performing an internal search, Directory
Server could not allocate space for the parameter block structure.
Check that sufficient memory is available
on the system.
4162: ldapu_get_cert_subject_dn_fails
The server is unable to obtain the subject in
the client certificate.
Check the message in the error log for more
information.
4163: ldapu_get_cert_issuer_dn_fails
The server is unable to obtain the certificate
issuer of the client certificate.
Check the message in the error log for more
information.
4164: 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: BER decoding: found id instead
of id for MessageId.
The Message ID tag was not found in the LDAP
The request is invalid. Check the application
that created the request.
4166: BER decoding: ber_peek_tag returns no Operation
An error occurred while decoding the operation
The request is invalid. Check the application
that created the request.
4167: 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.
4168: Compute hash of a node in a filter but the
filter choice is not valid type
While attempting to calculate the hash for a
filter node, Directory Server encountered an invalid type.
Contact Sun Technical Support.
4169: Compare two filters but the filter choice is
not valid type
While attempting to compare two filters, Directory
Server encountered an invalid type.
Contact Sun Technical Support.
4170: slapi_filter_test_ext: found unknown filter
While attempting to test whether an entry matches
a filter, Directory Server encountered an invalid type.
Contact Sun Technical Support.
4171: slapi_vattr_filter_test_ext: found unknown
filter type type
While attempting to test whether an entry matches
a filter, Directory Server encountered an invalid type.
Contact Sun Technical Support.
4173: slapd_init: could not create one or more locks
for communication purpose (operations connections...)
Directory Server could not create locks due
to resource constraints.
Check that Directory Server is not having
to contend for system resources with other applications.
Directory Server.
4175: FrontendConfig_init: failed to initialize read-write
lock structure.
Directory Server could not create locks due
to resource constraints.
Check that Directory Server is not having
to contend for system resources with other applications, and that sufficient
memory is available on the system.
Restart Directory Server.
4176: config_set: the attribute attribute is
ignoring new value value
A read-only attribute value has been changed.
Do not change the attribute value.
4177: 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: Could not open file filename in
mode mode.
The specified file could not be opened.
Check that the file exists and is accessible.
4185: Cannot allocate lock and/or conditional variable
to handle slapd_started variable.
Directory Server could not create locks or conditional
variables due to resource constraints.
Check that Directory Server is not having
to contend for system resources with other applications, and that sufficient
memory is available on the system.
4186: *** DISK FULL *** Attempting to shut down gracefully.
One of the following:
Directory Server ran out of disk space.
Directory Server is not properly configured to access data
in a backend.
Provide more local disk space to Directory
Server, if necessary.
Check that nsslapd-backend is
correctly set in the appropriate mapping tree entry under cn=config.
Check that the backend state is set correctly.
Check that the backend is not offline.
4187: Trying to get a block element but the element
identifier ID is unknown.
Directory Server tried to access a parameter
block field that does not exist.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
4188: Trying to set a block element but the element
identifier ID is unknown.
Directory Server tried to modify a parameter
block field that does not exist.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
4189: sequence error in error strings at item index. Error error (string)
should come after error error (string)
Directory Server encountered a problem encoding
Contact Sun Technical Support.
4190: Internal search base=&base&
scope=scope filter=filter Result: code (message)
An internal search used for authentication failed.
Check that the client credentials allow it
to access the entry to be used for authentication.
4191: 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.
4197: MODRDN invalid new RDN ("RDN")
The modify RDN operation on the specified entry
did not succeed.
Try again with a valid new RDN.
4197: MODRDN invalid new superior ("DN")
The modify RDN operation on the specified entry
did not succeed.
Try again with a valid new parent entry.
4210: Protocol error Account Usable control MUST
be marked critical
The account usability control was not marked
Notify the maintainer of the client application.
4211: error-code occurred
while changing state of backend backend-name. Resetting
An error occurred while putting backends off
Verify all backends are in a correct and
functional state.
4212: Server is already suspending all operations.
An administrator tried to put the already frozen
server in frozen mode.
4213: error-code while
stopping databases. Please make sure suffixes are online.
An error occurred while putting the server in
frozen mode.
Check that all suffixes supported by the
server respond to read and write operations then try again.
4612: Unable to start slapd because it is already
running as process process.
Unable to start Directory Server because it
is already running.
Stop the running server instance before launching
a new server.
4613: Unable to start slapd because the process process is importing the database
Unable to start Directory Server because a process
is currently importing the database.
Stop the running import process instance
before launching a new server.
4614: 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
Directory Server 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: 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: 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: 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 Directory Server before importing.
4618: 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 Directory Server before creating indexes.
4623: Pathname path too
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
4625: Cannot determine current directory.
When trying to convert the absolute path, the
server was unable to determine the current directory.
Contact Sun Technical Support.
4626: slapi_add_internal: add_values for type type failed.
Internal error when converting from a set of
modifications to an entry.
Contact Sun Technical Support.
4627: 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 Directory Server process.
Stop the running process and retry.
4629: Unable to create directory.
System error - the directory could not be created.
Check that your file system is valid and
4630: ref_array_init: new lock creation failed
Directory Server could not create locks due
to resource constraints.
Check that Directory Server is not having
to contend for system resources with other applications.
Directory Server.
4631: 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 Technical Support.
4633: 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: Security initialization for attribute encryption
The security initialization 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 (certificate file ciphers.)
4737: 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: 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: 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: Security Initialization: NSS initialization
failed (error error): path: path certdb
prefix: prefix keydb prefix: prefix.
Security initialization error. NSS initialization
Check the NSS configuration and retry.
4741: Security Initialization: NSS initialization
failed (error error)
Security initialization error. NSS initialization
Contact Sun Technical Support.
4742: Security Initialization: Failed to retrieve
SSL configuration information (error error): nssslSessionTimeout:
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: 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: 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: slapd_get_tmp_dir mkdir(variable) Error: error
System error. The server was unable to create
a temporary directory.
Check that the current user has sufficient
access rights to create the temporary directory and try again.
4747: 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 Technical Support.
4748: Security Initialization: Failed to set SSL
cipher preference information: cipher (error code - message)
Security initialization error. The server was
unable to set SSL cipher preference information.
Perform the following steps:
Check the syntax of the ciphers in the configuration.
Make sure that all the ciphers are supported by the server.
4749: 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 Technical Support.
4750: Security Initialization: Unable to get internal
slot (error error)
Security initialization error. The server was
unable to obtain the internal slot.
Contact Sun Technical Support.
4751: Security Initialization: Unable to authenticate
(error error)
Security initialization error. The server was
unable to authenticate.
Contact Sun Technical Support.
4756: None of the ciphers are valid.
The ciphers are invalid.
Check the ciphers and retry.
4757: 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 space in the /tmp directory
and try again.
4758: Config of SSL session cache failed (error error).
The configuration of the SSL session cache failed.
Contact Sun Technical Support.
4759: 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 Technical Support.
4760: 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 Technical Support.
4761: 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 Technical Support.
4766: Encryption alias not configured.
The encryption alias has not been configured.
Contact Sun Technical Support.
4769: 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: 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: 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: 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: 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: sasl error message
SASL error. The details of the error are logged
in the error log.
Check the error log for more information.
4779: 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: 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: 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 Directory Service Control Center.
Ensure that the trust attributes of CA certificates installed with certutil include the T trust attribute.
4782: 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.
4783: Out of memory to create a buffer to hold the
encrypted output (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4784: Out of memory to create a buffer to hold the
cleartext input (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4785: Cipher operation failed.
The server was unable to accomplish the cipher
operation.
It is likely that the context is incorrect.
Restart the server.
4786: 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.
4787: Out of memory to create a buffer to hold the
cleartext output (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4788: Out of memory to create a buffer to hold the
encrypted input (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4789: Out of memory to create a pwd item. (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4790: Out of memory to create a buffer to hold the
pwd item data (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4791: Out of memory to create the salt (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4792: Out of memory to create a buffer to hold the
salt data (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4793: Failed to generate symmetric key.
The server was unable to generate the symmetric
Check that a security token is available
to the server (as a certificate.)
4794: Out of memory to create a buffer to hold the
parameter data (error code - string).
Directory Server could not allocate memory needed
to encrypt attributes.
Make more memory available to Directory Server.
4795: 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: 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: Signature failed.
The signature required for attribute encryption
Restart the server.
4798: Key database password was rejected.
The password for the key database has been rejected.
Enter a new password and retry.
4799: 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: 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: 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: Bad password file syntax: missing &:&
preceding password.
The syntax of the password file is incorrect.
The colon, :, is missing.
Supply a password file with the correct syntax.
4803: 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.
4804: Missing security initialization required by
attribute encryption.
Security configuration has not been completed.
Make sure certificate and key database security
has been enabled, nsslapd-security: on.
4805: Failed to check whether attribute encryption
is configured or not.
An internal search for attribute encryption
configuration elements failed.
Make sure attribute encryption is properly
configured, then restart Directory Server.
4807: Security Initialization: Unable to register
PIN callback(error code - message)
Security Initialization: Unable to register
PIN callback
NSS refused the operation: check library
compatibility and requirements.
4808: Security Initialization: certificate database
file name should look like 'slapd-[serverId-]cert'
Security Initialization: badly formed certificate
database name
Check the value of the nsCertfile attribute
on cn=encryption. It should be of the form nsCertfile:
slapd-cert8.db.
4865: 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: 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: 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: 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: Out of memory to allocate a service provider
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: 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: 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: 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: Multiple backend instances are specified.
More than one backend instance has been specified
for the attempted task.
Contact Sun Technical Support.
4995: Cannot perform an import with pre-V3 backend
You are using 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: 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: 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: 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: ldbm2ldif: backend backend export
failed (error)
The db2ldif function failed
when attempting to export the database.
Refer to the error log for more information
and contact Sun Technical Support.
5000: No backend instance names are specified.
The database could not be exported because no
backend instance names were specified.
Contact Sun Technical Support.
5003: Cannot perform an import with pre-V3 backend
You are using 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.
5004: 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: 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: 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: db2archive function failed when trying to backup
(error error)
The db2archive function failed
when attempting to backup.
Refer to the error log for more information
and contact Sun Technical Support.
5008: 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
5009: Cannot perform a backup 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 backup.
Upgrade to a newer version of the backend
plug-in API (at least version 3), recompile, and add the backup functionality.
5010: 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: 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: Restore failed (error error)
The restore process failed.
Refer to the error log for more information
and contact Sun Technical Support.
5014: 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: 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: 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: db2index function failed when trying to restore
(error error)
The db2index function failed
when attempting to restore the database.
Refer to the error log for more information
and contact Sun Technical Support.
5019: No db2index function defined for backend backend.
The database could not be indexed because no db2index() function was defined for the backend.
Contact Sun Technical Support.
5020: 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: 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: Cannot create task node (error error)
The server is unable to create a task node.
Refer to the error log for more information
and contact Sun Technical Support.
5024: 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: Cannot import. Lookup instance name by suffixes
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: Cannot import. Could not find database for
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: 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: Cannot import - lookup instance names by suffix
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: 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: 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: Cannot index - backend not found.
The server cannot index the database because
the specified backend was not found.
Contact Sun Technical Support.
5034: 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, dsDecryptAttrs: true,
if you want to export the database for replication purposes.
5035: Unknown Password Compatibility task: state
Unknown password policy compatibility action.
Move the server to the correct compatibility
5036: Can not modify Password Policy compatibility
state. Task aborted.
The server could not move to the specified compatibility
See additional information returned to the
client application.
5036: Password Compatibility task and Password
Policy state are incompatible. Can not change Password Policy state.
The server could not move to the specified compatibility
See additional information returned to the
client application.
5037: Unable to allocate new task for changing
password compatibility state !"
Unable to allocate new task for backup.
Make more resources available for the server
and restart the server.
5038: Unable to create Password Policy compatibility
task thread !
Unable to create backup thread.
Make more resources available to the server
and try again.
5039: Password Policy compatibility state is
already state. Task aborted.
Nothing to do as the action required would not
change the compatibility state.
Change to a different compatibility state.
5040: Unknown log rotate task: type.
The server did not recognize the log type set
for the log rotation attribute.
Use a valid log type.
5041: Unable to allocate new task for log rotation
The server was unable to allocate a new task
for log rotation.
Make more system memory available by restarting
the server.
5042: Unable to create log rotation task thread!
The server was unable to allocate a new task
for log rotation.
Make more system memory available by restarting
the server.
5121: reslimit_init: slapi_register_object_extension()
The server cannot register an object extension
(during resource limit initialization).
Contact Sun Technical Support.
5122: PR_NewRWLock() failed for reslimit.
System error - the server cannot create a new
lock for the resource limit.
Contact Sun Technical Support.
5123: 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 Technical Support.
5124: error: slapi_get_object_extension()
returned NULL
The server could not obtain the object extension
(for the resource limit).
Contact Sun Technical Support.
5126: 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: parameter
A parameter error occurred when registering
a new resource to be tracked.
Perform the following tasks:
Check that the type is SLAPI_RESLIMIT_TYPE_INT
Check that attrname is an LDAP attribute
type that can be consulted in the bound entry to determine the limit&s
5127: error: parameter
Internal error. When retrieving the integer
limit associated with a connection and a resource, a parameter with a NULL
value was found.
Contact Sun Technical Support.
5128: error: unknown handle handle
Parameter error. The handle used to identify
a resource is unknown.
Contact Sun Technical Support.
5129: 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 Technical Support.
5130: malloc of bytes bytes
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.
5131: cannot realloc number
trying to allocate 0 or a negative number of bytes is not portable and gives
different results on different platforms. Please check the code and change
it to avoid the attempt to allocate number bytes.
Memory reallocation of number bytes
is not allowed.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5132: realloc of bytes bytes
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.
5133: cannot calloc number
trying to allocate 0 or a negative number of bytes is not portable and gives
different results on different platforms. Please check the code and change
it to avoid the attempt to allocate number bytes.
Memory allocation of number bytes
is not allowed.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5134: cannot calloc number
trying to allocate 0 or a negative number of elements is not portable and
gives different results on different platforms. Please check the code and
change it to avoid the attempt to allocate number elements.
Memory allocation of number elements
is not allowed.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5135: calloc of bytes bytes
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: strdup of chars chars
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: ber_bvdup of bytes bytes
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: 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
5250: Invalid value
The specified configuration attribute in the Directory Server configuration
file has no value or the value is invalid.
Check that the value of the attribute under cn=config in the Directory Server configuration file is either on or off.
5251: 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 is valid, and that the path
5252: 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 is set, and is correct.
5253: 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 Directory Server configuration is not higher than the RLIMIT_NOFILE parameter, and is not lower than 1.
5254: Ignoring attribute (since
-d option was given on the command line) nsslapd-errorlog-level.
The attribute nsslapd-errorlog-level in
the Directory Server configuration 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: 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 -d is invalid.
Check and correct the faulty plug-in configuration.
5256: file: max_descriptors: error
The request to set the maximum number of connections
failed either because the value was NULL or the value was
not in the allowed range [1..max] where max is the maximum number of file descriptors a process may create.
Check nsslapd-maxconnections on cn=config to ensure its value is not higher than the SC_OPEN_MAX system parameter, nor lower than 1.
5385: 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
5390: 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
5392: 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: str2entry_dupcheck: unexpected failure constructing
the value tree.
The server failed to add a value to the value
Check the error log for more information.
5394: Error occurs while removing attribute values.
Possible existing duplicate value for attribute type type found
in entry DN
The entry contains duplicate values for the
attribute.
Delete the attribute and add a new set of
5395: 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.
5396: Cannot compute &nscpEntryWSI& attribute
because there is no pblock in the context
A required parameter block structure was not
available.
Contact Sun Technical Support.
5397: Existing duplicate values found in attribute &type& of entry &DN&
The entry contains duplicate values for the
attribute.
Delete the attribute and add a new set of
5398: Duplicate value addition in attribute &type& of entry &DN&
A client is trying to add duplicate values for
the attribute.
Fix the client application.
5399: occurred while removing attribute values.
Could not find value number for attribute type (message).
Error occurs while trying to remove attribute
values. The value could not be found.
Check the attribute values to remove.
5505: Registration of extension failed.
A plug-in 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 plug-in code.
5506: Registration of extension extension
by plug-in failed: number extensions
already registered (max is max_ext).
Directory Server tried to register too many
object extensions.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5507: Number of extension users for extension is negative number.
Directory Server encountered a negative number
of object extensions.
Contact Sun Technical Support.
5508: Registration of type object
type failed. There is no more free slot in factory array for object type (current
in use number max is number).
Directory Server tried to register an object
type other than Connection, Operation, Entry, or Mapping Tree Node.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5509: Trying to get extension on unregistered object
type (object type identifier ID).
Directory Server tried to extend an unregistered
object type.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5510: Release extension on unregistered object type
(object type identifier ID).
Directory Server tried to release an extension
for an unregistered object type.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5511: Plugin plug-in tries
to register extension for object type that does not exist type.
Directory Server tried to extend a nonexistent
object type.
Unless you are developing a plug-in and broke
this yourself, contact Sun Technical Support.
5635: Backend backend is
already pointed to by another mapping tree node. Only one mapping tree node
can point to a backend.
Errors exist in the mapping tree node configuration.
Check nsslapd-backend values
in the mapping tree entry.
Check that the mapping tree node state
has a legal value, and that nsslapd-referral is appropriately
set if necessary.
5641: 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 Directory Server configuration.
5642: 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 Directory Server configuration.
5643: 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 Directory Server configuration.
5644: Cannot load distribution plugin lib library for node node.
The distribution plug-in 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: 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
plug-in or the distribution function name.
Check the values for the nsslapd-distribution-plugin and nsslapd-distribution-func attributes in
the plug-in configuration entry.
5648: 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 contact Sun Technical Support.
5650: Modify (add or replace) callback for mapping
tree: could not find parent for mapping tree node DN
One of the following:
The mapping tree parent is not a suffix of a mapping tree
While modifying the CN or nsslapd-parent-suffix, Directory Server could not find the new parent.
If the modification originated in a client
request, fix the client. Otherwise, contact Sun Technical Support.
5653: Distribution plugin returned wrong backend:
backend index index (range 0..max)
for entry DN at node DN
One of the following:
No attribute value exists for nsslapd-distribution-func.
The distribution plug-in returned a bad backend index value.
Perform the following steps:
Check the configuration for the distribution plug-in.
Fix the distribution plug-in.
If neither remedy
works, contact Sun Technical Support.
5654: Distribution plugin not configured for mapping
tree node DN
Directory Server tried to use a distribution
plug-in, but the distribution plug-in was not appropriately configured.
Check the configuration for the distribution
5659: Cannot find distribution function function in distribution plugin lib library for
node node.
The distribution function in the plug-in 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.
5889: Could not create lock for Schema DSE
Directory Server could not create a lock for
the schema subentry.
Check that Directory Server is not having
to contend for system resources with other applications.
5890: 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.
5891: Could not add attribute type &objectClass&
to the schema: message
Directory Server could not create the default objectclass schema definition.
Contact Sun Technical Support.
5892: Could not add attribute type &aci&
to the schema: message
Directory Server could not create the default aci schema definition.
Contact Sun Technical Support.
5893: Entry entry required
attribute objectclass is missing.
The specified entry was added without an objectclass attribute.
Check the application that added the entry.
5894: 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: 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: Entry entry attribute attribute required by objectclass objectclass is
The entry that was added or modified is missing
a required attribute.
Check the application that added or modified
the entry.
5897: 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.
5898: No attribute types to iterate through internally
Directory Server got an empty attribute type
Contact Sun Technical Support.
5899: No OID found in schema for syntax syntax
Directory Server could not match the OID with
any OID in the schema.
Fix the schema, or the client. If neither
fix solves the problem, contact Sun Technical Support.
5900: 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.
5901: No name or OID specified for checking schema
Internal error
Contact Sun Technical Support.
5906: Value has invalid syntax (not syntax): attr=value
Entry was added or modified with invalid attribute
Check application that added or modified
the entry.
8194: 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 initialize the consumer again.
8195: 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: Bad Window size value for agreement agreement_name.
The value of the ds5ReplicaTransportWindowSize attribute is invalid.
Check the Directory Server configuration
defining the Replication Agreement.
Check the modification operation attempted
on the replication agreement.
8197: Bad Group size value for agreement agreement_name.
The value of the ds5ReplicaTransportGroupSize attribute is invalid.
Check the Directory Server configuration
defining the Replication Agreement.
Check the modifications attempted on the
replication agreement.
8198: Bad Compression Level value for agreement agreement_name.
The value of the ds5ReplicaTransportCompressionLevel attribute is invalid.
Check the Directory Server configuration
defining the Replication Agreement.
Check the modifications attempted on the
replication agreement.
8199: 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 Directory Server configuration
defining the Replication Agreement.
Check the modifications attempted on the
replication agreement.
8200: 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.
8201: Failed to update the state (enable/disable)
of the agreement agreement
Replication is stopping for this agreement.
Wait until the agreement has stopped and
try again.
8202: 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.
8203: Failed to update partial replication checksum
for agreement agreement
One of the following:
The checksum value provided for partial replication was not
Replication is stopping for this agreement.
Wait until the agreement has stopped and
try again.
8204: 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.
8205: Failed to update Bind Method for agreement agreement
The replication agreement is stopping.
Wait until the agreement has stopped and
try again.
8206: Failed to update Transport Information for
agreement agreement
The replication agreement is stopping.
Wait until the agreement has stopped and
try again.
8207: Failed to update Bind DN for agreement agreement
The replication agreement is stopping.
Wait until the agreement has stopped and
try again.
8208: Failed to update TimeOut value for agreement agreement
One of the following:
A client attempted to set an invalid attribute type or value.
Replication is stopping for this agreement.
Perform the following steps:
Check the client application.
Wait until the agreement has stopped and try again.
8209: Failed to update Credentials for agreement agreement
One of the following:
A client attempted to set an invalid attribute type or value.
Replication is stopping for this agreement.
Perform the following steps:
Check the client application.
Wait until the agreement has stopped and try again.
8210: No value supplied for attr attribute
No value was supplied for the specified attribute.
Perform the following steps:
Check the client application.
Wait until the agreement has stopped and try again.
8211: Invalid value value supplied
for attr attribute
The value supplied for the specified attribute
is not a valid value.
Perform the following steps:
Check the client application.
Wait until the agreement has stopped and try again.
8212: Failed to update replication schedule for agreement agreement_name.
One of the following:
The replication schedule format is invalid.
The replication agreement is stopping.
Perform the following steps:
Check the client application.
Wait until the agreement has stopped and try again.
8213: 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: 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 Directory Service Control Center.
8216: 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
Update the current configuration on the supplier,
or initialize the consumer again.
8218: Replication protocol v5.0 not supported for consumer.
The version 5 replication protocol is not supported
for this consumer.
Check the version of Directory Server running
on the specified consumer.
8219: 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: Too much time skew between replicas for [consumer:port]
The time difference betw