| | |
| | | ERR_CONFIG_ERROR_APPLYING_STARTUP_CHANGE_564=Unable to apply a change \ |
| | | at server startup: %s |
| | | ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE_565=One or more errors occurred \ |
| | | while applying changes on server startup |
| | | while applying changes on server startup: %s |
| | | ERR_CONFIG_BACKEND_MODE_INVALID_567=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.) |
| | |
| | | ERR_CONFIG_HTTPENDPOINT_INVALID_CONFIGURATION_741=The HTTP endpoint configuration \ |
| | | defined in %s is invalid: %s |
| | | ERR_CONFIG_REST2LDAP_MALFORMED_URL_742=Invalid configuration URL in the REST2LDAP endpoint \ |
| | | configuration entry %s: %s |
| | | configuration entry %s: %s |
| | | ERR_CANNOT_INITIALIZE_CONFIGURATION_FRAMEWORK_743=Cannot initialize the \ |
| | | configuration framework: %s |
| | | ERR_UNABLE_TO_RETRIEVE_CHILDREN_OF_CONFIGURATION_ENTRY_744=Unable to retrieve \ |
| | | children of configuration entry with dn: %s |
| | | ERR_UNABLE_TO_LOAD_CONFIGURATION_ENABLED_SCHEMA_745=Unable to load the \ |
| | | configuration-enabled schema: %s |
| | | ERR_CONFIG_BACKEND_CANNOT_DELETE_ENTRY_746=Backend config error when trying to \ |
| | | delete an entry: %s |