Category: Configuration Management
Access and audit logs concern client operations rather than the server and tools, and so are not listed here. Instead, this document covers severe and fatal error messages for the server and its tools, such as those logged in logs/errors, and logs/replication.
- ID: 7
Severity: ERROR
Message: Unable to set the value for Boolean configuration attribute %s because the provided value %s was not either 'true' or 'false'.
- ID: 11
Severity: ERROR
Message: Unable to set the value for integer configuration attribute %s because the provided value %s cannot be interpreted as an integer value: %s.
- ID: 12
Severity: ERROR
Message: Unable to set the value for configuration attribute %s because the provided value %d is less than the lowest allowed value of %d.
- ID: 13
Severity: ERROR
Message: Unable to set the value for configuration attribute %s because the provided value %d is greater than the largest allowed value of %d.
- ID: 26
Severity: ERROR
Message: The specified configuration file %s does not exist or is not readable.
- ID: 27
Severity: ERROR
Message: An unexpected error occurred while attempting to determine whether configuration file %s exists: %s.
- ID: 28
Severity: ERROR
Message: An error occurred while attempting to open the configuration file %s for reading: %s.
- ID: 33
Severity: ERROR
Message: The first entry read from LDIF configuration file %s had a DN of "%s" rather than the expected "%s" which should be used as the Directory Server configuration root.
- ID: 34
Severity: ERROR
Message: An unexpected error occurred while attempting to process the Directory Server configuration file %s: %s.
- ID: 38
Severity: ERROR
Message: Unable to determine the Directory Server instance root from either an environment variable or based on the location of the configuration file. Please set an environment variable named %s with a value containing the absolute path to the server installation root.
- ID: 39
Severity: ERROR
Message: An unexpected error occurred while trying to write configuration entry %s to LDIF: %s.
- ID: 41
Severity: ERROR
Message: The Directory Server configuration may not be altered by importing a new configuration from LDIF.
- ID: 49
Severity: ERROR
Message: An error occurred while attempting to create a Directory Server logger from the information in configuration entry %s: %s.
- ID: 50
Severity: ERROR
Message: Configuration entry %s does not contain a valid objectclass for a Directory Server access, error, or debug logger definition.
- ID: 54
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server access logger: %s.
- ID: 55
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server error logger: %s.
- ID: 56
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server debug logger: %s.
- ID: 74
Severity: ERROR
Message: Configuration entry %s does not contain attribute %s (or that attribute exists but is not accessible using JMX).
- ID: 78
Severity: ERROR
Message: There is no method %s for any invokable component registered with configuration entry %s.
- ID: 83
Severity: ERROR
Message: The Directory Server could not register a JMX MBean for the component associated with configuration entry %s: %s.
- ID: 84
Severity: ERROR
Message: An unexpected error occurred while trying to export the Directory Server configuration to LDIF: %s.
- ID: 94
Severity: ERROR
Message: Worker thread "%s" has experienced too many repeated failures while attempting to retrieve the next operation from the work queue (%d failures experienced, maximum of %d failures allowed). This worker thread will be destroyed.
- ID: 95
Severity: ERROR
Message: A problem occurred while trying to create and start an instance of class %s to use as a monitor provider for the Directory Server work queue: %s. No monitor information will be available for the work queue.
- ID: 103
Severity: ERROR
Message: An unexpected error occurred while trying to register the configuration handler base DN "%s" as a private suffix with the Directory Server: %s.
- ID: 105
Severity: ERROR
Message: The entry cn=Backends,cn=config does not appear to exist in the Directory Server configuration. This is a required entry.
- ID: 107
Severity: ERROR
Message: An unexpected error occurred while interacting with backend configuration entry %s: %s.
- ID: 112
Severity: ERROR
Message: An unexpected error occurred while attempting to determine whether the backend associated with configuration entry %s should be enabled or disabled: %s. It will be disabled.
- ID: 115
Severity: ERROR
Message: The Directory Server was unable to load class %s and use it to create a backend instance as defined in configuration entry %s. The error that occurred was: %s. This backend will be disabled.
- ID: 116
Severity: ERROR
Message: An error occurred while trying to initialize a backend loaded from class %s with the information in configuration entry %s: %s. This backend will be disabled.
- ID: 154
Severity: ERROR
Message: An error occurred while trying to initialize a connection handler loaded from class %s with the information in configuration entry %s: %s. This connection handler will be disabled.
- ID: 188
Severity: ERROR
Message: Unable to read the Directory Server schema definitions because the schema directory %s does not exist.
- ID: 189
Severity: ERROR
Message: Unable to read the Directory Server schema definitions because the schema directory %s exists but is not a directory.
- ID: 190
Severity: ERROR
Message: Unable to read the Directory Server schema definitions from directory %s because an unexpected error occurred while trying to list the files in that directory: %s.
- ID: 200
Severity: ERROR
Message: An unexpected error occurred that prevented the server from installing its default entry cache framework: %s.
- ID: 202
Severity: ERROR
Message: An error occurred while attempting to initialize an instance of class %s for use as the Directory Server entry cache: %s. As a result, the entry cache will be disabled.
- ID: 203
Severity: ERROR
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: %s.
- ID: 204
Severity: ERROR
Message: The configuration for the entry cache defined in configuration entry %s was not acceptable: the entry cache level %d is already in use.
- ID: 245
Severity: ERROR
Message: An error occurred while attempting to initialize an instance of class %s as a Directory Server plugin using the information in configuration entry %s: %s. This plugin will be disabled.
- ID: 256
Severity: ERROR
Message: Class %s specified in configuration entry %s does not contain a valid extended operation handler implementation: %s.
- ID: 261
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an extended operation handler as defined in configuration entry %s: %s.
- ID: 277
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a SASL mechanism handler as defined in configuration entry %s: %s.
- ID: 278
Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because that DN does not have a parent.
- ID: 280
Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because another configuration entry already exists with that DN.
- ID: 281
Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because that DN does not have a parent.
- ID: 282
Severity: ERROR
Message: Entry %s cannot be added to the Directory Server configuration because its parent entry %s does not exist.
- ID: 283
Severity: ERROR
Message: The Directory Server is unwilling to add configuration entry %s because one of the add listeners registered with the parent entry %s rejected this change with the message: %s.
- ID: 284
Severity: ERROR
Message: An unexpected error occurred while attempting to add configuration entry %s as a child of entry %s: %s.
- ID: 285
Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry does not exist.
- ID: 286
Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the specified entry has one or more subordinate entries.
- ID: 287
Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because the entry does not have a parent and removing the configuration root entry is not allowed.
- ID: 288
Severity: ERROR
Message: Entry %s cannot be removed from the Directory Server configuration because one of the delete listeners registered with the parent entry %s rejected this change with the message: %s.
- ID: 289
Severity: ERROR
Message: An unexpected error occurred while attempting to remove configuration entry %s as a child of entry %s: %s.
- ID: 290
Severity: ERROR
Message: Entry %s cannot be modified because the specified entry does not exist.
- ID: 291
Severity: ERROR
Message: Entry %s cannot be modified because one of the configuration change listeners registered for that entry rejected the change: %s.
- ID: 292
Severity: ERROR
Message: An unexpected error occurred while attempting to modify configuration entry %s as a child of entry %s: %s.
- ID: 300
Severity: ERROR
Message: An error occurred while attempting to export the new Directory Server configuration to file %s: %s.
- ID: 301
Severity: ERROR
Message: An error occurred while attempting to rename the new Directory Server configuration from file %s to %s: %s.
- ID: 302
Severity: ERROR
Message: Modify DN operations are not allowed in the Directory Server configuration.
- ID: 376
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password storage scheme as defined in configuration entry %s: %s.
- ID: 377
Severity: ERROR
Message: Unable to add a new password storage scheme entry with DN %s because there is already a storage scheme registered with that DN.
- ID: 422
Severity: ERROR
Message: The Directory Server was unable to acquire a shared lock for backend %s: %s. This generally means that the backend is in use by a process that requires an exclusive lock (e.g., importing from LDIF or restoring a backup). This backend will be disabled.
- ID: 442
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an identity mapper as defined in configuration entry %s: %s.
- ID: 464
Severity: ERROR
Message: An error occurred while attempting to instantiate class %s referenced in synchronization provider configuration entry %s: %s.
- ID: 465
Severity: ERROR
Message: An error occurred while attempting to initialize the Directory Server synchronization provider referenced in configuration entry %s: %s.
- ID: 489
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password validator as defined in configuration entry %s: %s.
- ID: 505
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a password generator as defined in configuration entry %s: %s.
- ID: 514
Severity: ERROR
Message: No password policies have been defined below the cn=Password Policies,cn=config entry in the Directory Server configuration. At least one password policy configuration must be defined.
- ID: 515
Severity: ERROR
Message: The password policy defined in configuration entry %s is invalid: %s.
- ID: 516
Severity: ERROR
Message: The Directory Server default password policy is defined as %s, but that entry does not exist or is not below the password policy configuration base cn=Password Policies,cn=config.
- ID: 533
Severity: ERROR
Message: An error occurred while attempting to instantiate class %s referenced in the access control configuration entry %s: %s.
- ID: 558
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an account status notification handler as defined in configuration entry %s: %s.
- ID: 559
Severity: ERROR
Message: Unable to add a new account status notification handler entry with DN %s because there is already a notification handler registered with that DN.
- ID: 563
Severity: ERROR
Message: An error occurred while attempting to apply the changes contained in file %s to the server configuration at startup: %s.
- ID: 565
Severity: ERROR
Message: One or more errors occurred while applying changes on server startup: %s.
- ID: 567
Severity: ERROR
Message: Configuration entry %s does not contain a valid value for configuration attribute ds-cfg-db-directory-permissions (It should be an UNIX permission mode in three-digit octal notation.).
- ID: 568
Severity: ERROR
Message: Invalid UNIX file permissions %s does not allow read and write access to the backend database directory by the backend.
- ID: 571
Severity: ERROR
Message: No default password policy is configured for the Directory Server. The default password policy must be specified by the ds-cfg-default-password-policy attribute in the cn=config entry.
- ID: 573
Severity: ERROR
Message: An error occurred while trying to create the configuration archive directory %s.
- ID: 574
Severity: ERROR
Message: An error occurred while trying to create the configuration archive directory %s: %s.
- ID: 575
Severity: ERROR
Message: An error occurred while trying to write the current configuration to the configuration archive: %s.
- ID: 591
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a group implementation as in configuration entry %s: %s.
- ID: 598
Severity: ERROR
Message: You do not have sufficient privileges to perform add operations in the Directory Server configuration.
- ID: 599
Severity: ERROR
Message: You do not have sufficient privileges to perform delete operations in the Directory Server configuration.
- ID: 600
Severity: ERROR
Message: You do not have sufficient privileges to perform modify operations in the Directory Server configuration.
- ID: 601
Severity: ERROR
Message: You do not have sufficient privileges to perform modify DN operations in the Directory Server configuration.
- ID: 602
Severity: ERROR
Message: You do not have sufficient privileges to perform search operations in the Directory Server configuration.
- ID: 603
Severity: ERROR
Message: You do not have sufficient privileges to change the set of default root privileges.
- ID: 614
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a certificate mapper as defined in configuration entry %s: %s.
- ID: 627
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a key manager provider as defined in configuration entry %s: %s.
- ID: 640
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as a trust manager provider as defined in configuration entry %s: %s.
- ID: 643
Severity: ERROR
Message: Unable to retrieve JMX attribute %s associated with configuration entry %s: %s.
- ID: 645
Severity: ERROR
Message: %s.%s returned a result of null for entry %s.
- ID: 646
Severity: ERROR
Message: %s.%s failed for entry %s: result code=%s, admin action required=%b, messages="%s".
- ID: 649
Severity: ERROR
Message: Unable to parse value "%s" from config entry "%s" as a valid search filter: %s.
- ID: 650
Severity: ERROR
Message: An error occurred while trying to load an instance of class %s referenced in configuration entry %s as a virtual attribute provider: %s.
- ID: 651
Severity: ERROR
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but provider %s may generate multiple values.
- ID: 652
Severity: ERROR
Message: The virtual attribute configuration in entry "%s" is not valid because attribute type %s is single-valued but the conflict behavior is configured to merge real and virtual values.
- ID: 653
Severity: ERROR
Message: Configuration entry %s cannot be modified because the change would alter its structural object class.
- ID: 654
Severity: ERROR
Message: An error occurred while attempting to calculate a SHA-1 digest of file %s: %s.
- ID: 656
Severity: ERROR
Message: The Directory Server encountered an error while attempting to determine whether the configuration file %s has been externally edited with the server online, and/or trying to preserve such changes: %s. Any manual changes made to that file may have been lost.
- ID: 657
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log rotation policy: %s.
- ID: 658
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server log retention policy: %s.
- ID: 659
Severity: ERROR
Message: An error occurred while attempting to create a Directory Server log rotation policy from the information in configuration entry %s: %s.
- ID: 660
Severity: ERROR
Message: An error occurred while attempting to create a Directory Server log retention policy from the information in configuration entry %s: %s.
- ID: 661
Severity: ERROR
Message: An error occurred while attempting to create a text writer for a Directory Server logger from the information in configuration entry %s: %s.
- ID: 674
Severity: ERROR
Message: Unable to initialize an instance of class %s as a work queue as specified in configuration entry %s: %s.
- ID: 676
Severity: ERROR
Message: The attempt to apply the configuration add failed. The preliminary checks were all successful and the entry was added to the server configuration, but at least one of the configuration add listeners reported an error when attempting to apply the change: %s.
- ID: 677
Severity: ERROR
Message: The attempt to apply the configuration delete failed. The preliminary checks were all successful and the entry was removed from the server configuration, but at least one of the configuration delete listeners reported an error when attempting to apply the change: %s.
- ID: 678
Severity: ERROR
Message: The attempt to apply the configuration modification failed. The preliminary checks were all successful and the modified entry was written to the server configuration, but at least one of the configuration change listeners reported an error when attempting to apply the change: %s.
- ID: 679
Severity: ERROR
Message: The configuration for the key manager provider defined in configuration entry %s was not acceptable: %s.
- ID: 680
Severity: ERROR
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.
- ID: 681
Severity: ERROR
Message: The configuration for the trust manager provider defined in configuration entry %s was not acceptable: %s.
- ID: 682
Severity: ERROR
Message: The configuration for the account status notification handler defined in configuration entry %s was not acceptable: %s.
- ID: 684
Severity: ERROR
Message: The configuration for the certificate mapper defined in configuration entry %s was not acceptable: %s.
- ID: 686
Severity: ERROR
Message: The configuration for the group implementation defined in configuration entry %s was not acceptable: %s.
- ID: 687
Severity: ERROR
Message: The configuration for the identity mapper defined in configuration entry %s was not acceptable: %s.
- ID: 689
Severity: ERROR
Message: The configuration for the password generator defined in configuration entry %s was not acceptable: %s.
- ID: 690
Severity: ERROR
Message: The configuration for the password storage scheme defined in configuration entry %s was not acceptable: %s.
- ID: 691
Severity: ERROR
Message: The configuration for the password validator defined in configuration entry %s was not acceptable: %s.
- ID: 692
Severity: ERROR
Message: The configuration for the plugin defined in configuration entry %s was not acceptable: %s.
- ID: 693
Severity: ERROR
Message: The configuration for the SASL mechanism handler defined in configuration entry %s was not acceptable: %s.
- ID: 694
Severity: ERROR
Message: The configuration for the virtual attribute provider defined in configuration entry %s was not acceptable: %s.
- ID: 695
Severity: ERROR
Message: The configuration for the alert handler defined in configuration entry %s was not acceptable: %s.
- ID: 696
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an alert handler as defined in configuration entry %s: %s.
- ID: 698
Severity: ERROR
Message: An error occurred while attempting to open the current configuration file %s for reading in order to copy it to the ".startok" file: %s.
- ID: 699
Severity: ERROR
Message: An error occurred while attempting to open file %s in order to write the ".startok" configuration file: %s.
- ID: 700
Severity: ERROR
Message: An error occurred while attempting to copy the current configuration from file %s into temporary file %s for use as the ".startok" configuration file: %s.
- ID: 701
Severity: ERROR
Message: An error occurred while attempting to rename file %s to %s for use as the ".startok" configuration file: %s.
- ID: 704
Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: %s.
- ID: 705
Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property does not follow a singular property=value form.
- ID: 706
Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property shadows configuration attribute %s.
- ID: 707
Severity: ERROR
Message: An error occurred while trying to parse and validate Berkeley DB JE property %s: the property is already defined for this component.
- ID: 709
Severity: ERROR
Message: An error occurred while attempting to open the configured log file %s for logger %s: %s.
- ID: 715
Severity: ERROR
Message: Invalid UNIX file permissions %s does not allow write access to the log file by the log publisher.
- ID: 716
Severity: ERROR
Message: Invalid UNIX file permissions %s: %s.
- ID: 726
Severity: ERROR
Message: The configuration entry '%s' is currently defined to be the default password policy, however it is not a password policy.
- ID: 727
Severity: ERROR
Message: The default password policy value '%s' is invalid because it refers to an authentication policy which is not a password policy.
- ID: 728
Severity: ERROR
Message: The timestamp format string "%s" is not a valid format string. The format string should conform to the syntax described in the documentation for the "java.text.SimpleDateFormat" class.
- ID: 729
Severity: ERROR
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid user DN pattern "%s".
- ID: 730
Severity: ERROR
Message: The access log filtering criteria defined in "%s" could not be parsed because it contains an invalid target DN pattern "%s".
- ID: 732
Severity: ERROR
Message: Class %s specified in attribute ds-cfg-java-class of configuration entry %s cannot be instantiated as a Directory Server HTTP access logger: %s.
- ID: 735
Severity: ERROR
Message: An error occurred while attempting to update a Directory Server logger from the information in configuration entry %s: %s.
- ID: 737
Severity: ERROR
Message: Cannot configure java.util.logging root logger level: %s. java.util.logging support is now disabled.
- ID: 738
Severity: ERROR
Message: An error occurred while trying to initialize an instance of class %s as an HTTP endpoint as defined in configuration entry %s: %s.
- ID: 739
Severity: ERROR
Message: An error occurred while starting the HTTP endpoint as defined in configuration entry %s: %s.
- ID: 741
Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is invalid: %s.
- ID: 743
Severity: ERROR
Message: Cannot initialize the configuration framework: %s.
- ID: 744
Severity: ERROR
Message: Unable to retrieve children of configuration entry with dn: %s.
- ID: 745
Severity: ERROR
Message: Unable to load the configuration-enabled schema: %s.
- ID: 746
Severity: ERROR
Message: Backend config error when trying to delete an entry: %s.
- ID: 747
Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is referencing a non existing authorization DN %s.
- ID: 748
Severity: ERROR
Message: The HTTP endpoint configuration defined in %s is referencing mutually exclusive authorization DNs %s and %s.
- ID: 749
Severity: ERROR
Message: Unable to read the configuration from %s in the REST2LDAP endpoint configuration entry %s: %s.
- ID: 750
Severity: ERROR
Message: Invalid JSON element %s from %s in the REST2LDAP endpoint configuration entry %s: %s.
- ID: 751
Severity: ERROR
Message: Invalid configuration element from %s in the REST2LDAP endpoint configuration entry %s: %s.
- ID: 752
Severity: ERROR
Message: The OAuth2 authorization mechanism defined in %s contains an invalid JSON Pointer %s: %s.
- ID: 753
Severity: ERROR
Message: The authorization mechanism defined in %s is referencing a non-existing or non-readable directory: %s.
- ID: 754
Severity: ERROR
Message: The authorization mechanism defined in %s is referencing a non existing DN: %s.
- ID: 755
Severity: ERROR
Message: The authorization mechanism defined in %s is referencing an invalid URL %s: %s.
- ID: 756
Severity: ERROR
Message: Unable to configure the authorization mechanism defined in %s: %s.
- ID: 757
Severity: ERROR
Message: The requested admin API version '%s' is unsupported. This endpoint only supports the following admin API version(s): %s.
- ID: 758
Severity: ERROR
Message: The configuration of schema provider '%s' is not acceptable for the following reasons: %s.
- ID: 759
Severity: ERROR
Message: The schema provider class '%s' could not be instantiated or initialized with the configuration '%s' : %s.
- ID: 760
Severity: ERROR
Message: The core schema provider defined by '%s' has been disabled. The core schema must always be enabled.
- ID: 763
Severity: ERROR
Message: Unable to configure the backend '%s' because one of its base DNs is the empty DN.
- ID: 764
Severity: ERROR
Message: Cannot configure new SSL protocols for '%s' because the protocols '%s' are not supported. Look for supported protocols in 'cn=System,cn=monitor'.
- ID: 765
Severity: ERROR
Message: Cannot configure new SSL cipher suites for '%s' because the cipher suites '%s' are not supported. Look for supported cipher suites in 'cn=System,cn=monitor'.
- ID: 766
Severity: ERROR
Message: The metric name pattern to exclude '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.
- ID: 767
Severity: ERROR
Message: The metric name pattern to include '%s' cannot be parsed as a valid regular expression due to the following error: '%s'.
- ID: 772
Severity: ERROR
Message: The list of keys defined for the JSON matching rule contains an invalid JSON pointer : %s.
- ID: 774
Severity: ERROR
Message: Cannot create the property resolver due to the following error: '%s'.
- ID: 775
Severity: ERROR
Message: Error creating SSL socket factory: %s.
- ID: 776
Severity: ERROR
Message: The smtp-server value '%s' is invalid: %s.
- ID: 777
Severity: ERROR
Message: Unable to resolve the host for the listen address '%s' of the LDAP connection handler %s.