# CDDL HEADER START
|
#
|
# The contents of this file are subject to the terms of the
|
# Common Development and Distribution License, Version 1.0 only
|
# (the "License"). You may not use this file except in compliance
|
# with the License.
|
#
|
# You can obtain a copy of the license at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE
|
# or https://OpenDS.dev.java.net/OpenDS.LICENSE.
|
# See the License for the specific language governing permissions
|
# and limitations under the License.
|
#
|
# When distributing Covered Code, include this CDDL HEADER in each
|
# file and include the License file at
|
# trunk/opends/resource/legal-notices/OpenDS.LICENSE. If applicable,
|
# add the following below this CDDL HEADER, with the fields enclosed
|
# by brackets "[]" replaced with your own identifying information:
|
# Portions Copyright [yyyy] [name of copyright owner]
|
#
|
# CDDL HEADER END
|
#
|
# Copyright 2006-2009 Sun Microsystems, Inc.
|
#
|
# Global directives
|
#
|
global.category=CONFIG
|
#
|
# Format string definitions
|
#
|
# Keys must be formatted as follows:
|
#
|
# [SEVERITY]_[DESCRIPTION]_[ORDINAL]
|
#
|
# where:
|
#
|
# SEVERITY is one of:
|
# [INFO, MILD_WARN, SEVERE_WARN, MILD_ERR, SEVERE_ERR, FATAL_ERR, DEBUG, NOTICE]
|
#
|
# DESCRIPTION is an upper case string providing a hint as to the context of
|
# the message in upper case with the underscore ('_') character serving as
|
# word separator
|
#
|
# ORDINAL is an integer unique among other ordinals in this file
|
#
|
MILD_ERR_CONFIG_ATTR_IS_REQUIRED_1=Konfigurationsattribut %s erfordert mindestens einen Wert, aber der sich daraus ergebende Vorgang h\u00e4tte alle Werte entfernt
|
MILD_ERR_CONFIG_ATTR_REJECTED_VALUE_2=Der angegebene Wert %s f\u00fcr Konfigurationsattribut %s wurde zur\u00fcckgewiesen. Die angegebene Ursache ist: %s
|
MILD_ERR_CONFIG_ATTR_SET_VALUES_IS_SINGLE_VALUED_3=Konfigurationsattribut %s ist einwertig, es wurden aber mehrere Werte angegeben
|
MILD_ERR_CONFIG_ATTR_ADD_VALUES_IS_SINGLE_VALUED_4=Konfigurationsattribut %s ist einwertig, durch das Hinzuf\u00fcgen der angegebenen Werte w\u00e4re es aber mehrwertig geworden
|
MILD_ERR_CONFIG_ATTR_ADD_VALUES_ALREADY_EXISTS_5=Konfigurationsattribut %s enth\u00e4lt bereits einen Wert %s
|
MILD_ERR_CONFIG_ATTR_NO_SUCH_VALUE_6=Wert %s kann nicht aus dem Konfigurationsattribut %s entfernt werden, da der angegebene Wert nicht vorhanden ist
|
MILD_ERR_CONFIG_ATTR_INVALID_BOOLEAN_VALUE_7=Wert f\u00fcr boolesches Konfigurationsattribut %s kann nicht gesetzt werden, da der angegebenen Wert %s nicht 'true' oder 'false' ist
|
MILD_ERR_CONFIG_ATTR_NO_INT_VALUE_8=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Ganzzahl abgefragt werden, da das Attribut keine Werte enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_INT_VALUES_9=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Ganzzahl abgefragt werden, da das Attribut mehrere Werte enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_VALUE_OUT_OF_INT_RANGE_10=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Java-Ganzzahl abgefragt werden, da der Wert au\u00dferhalb des zul\u00e4ssigen Bereichs f\u00fcr Ganzzahlen liegt
|
MILD_ERR_CONFIG_ATTR_INVALID_INT_VALUE_11=Wert f\u00fcr das Ganzzahl-Konfigurationsattribut %s kann nicht gesetzt werden, da der angegebene Wert %s nicht als Ganzzahlwert interpretiert werden kann: %s
|
MILD_ERR_CONFIG_ATTR_INT_BELOW_LOWER_BOUND_12=Wert f\u00fcr Konfigurationsattribut %s kann nicht gesetzt werden, da der angegebene Wert %d kleiner als der niedrigste zul\u00e4ssige Wert %d ist
|
MILD_ERR_CONFIG_ATTR_INT_ABOVE_UPPER_BOUND_13=Wert f\u00fcr Konfigurationsattribut %s kann nicht gesetzt werden, da der angegebene Wert %d gr\u00f6\u00dfer als der h\u00f6chste zul\u00e4ssige Wert %d ist
|
MILD_ERR_CONFIG_ATTR_INT_COULD_NOT_PARSE_14=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als Ganzzahlwert geparst werden: %s
|
MILD_ERR_CONFIG_ATTR_NO_STRING_VALUE_15=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Zeichenkette abgefragt werden, da das Attribut keine Werte enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_STRING_VALUES_16=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Zeichenkette abgefragt werden, da das Attribut mehrere Werte enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_EMPTY_STRING_VALUE_17=F\u00fcr Konfigurationsattribut %s wurde eine leere Wertezeichenkette angegeben
|
MILD_ERR_CONFIG_ATTR_VALUE_NOT_ALLOWED_18=Wert %s ist nicht in der Liste der zul\u00e4ssigen Werte f\u00fcr Konfigurationsattribut %s enthalten
|
MILD_ERR_CONFIG_ATTR_INVALID_UNIT_19='%s' ist keine g\u00fcltige Einheit f\u00fcr Konfigurationsattribut %s
|
MILD_ERR_CONFIG_ATTR_NO_UNIT_DELIMITER_20=%s kann nicht als Ganzzahlwert und als Einheit f\u00fcr Konfigurationsattribut %s dekodiert werden, da kein Wert-/Einheitsbegrenzer gefunden werden kann
|
MILD_ERR_CONFIG_ATTR_COULD_NOT_PARSE_INT_COMPONENT_21=Ganzzahl-Anteil des Werts %s f\u00fcr Konfigurationsattribut %s kann nicht dekodiert werden: %s
|
MILD_ERR_CONFIG_ATTR_INVALID_VALUE_WITH_UNIT_22=Der angegebene Wert %s f\u00fcr die Ganzzahl mit dem Einheitsattribut %s ist unzul\u00e4ssig: %s
|
MILD_ERR_CONFIG_ENTRY_CONFLICTING_CHILD_23=Konfigurationseintrag %s kann nicht als untergeordneter Eintrag von Konfigurationseintrag %s hinzugef\u00fcgt werden, da bereits ein untergeordneter Eintrag mit dem DN vorhanden ist
|
MILD_ERR_CONFIG_ENTRY_NO_SUCH_CHILD_24=Eintrag %s kann nicht als untergeordneter Eintrag von Konfigurationseintrag %s entfernt werden, da der Eintrag keinen untergeordneten Eintrag mit dem angegebenen DN hat
|
MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_NONLEAF_25=Eintrag %s kann nicht als untergeordneter Eintrag von Konfigurationseintrag %s entfernt werden, da der Eintrag eigene untergeordnete Eintr\u00e4ge hat und Non-Leaf-Eintr\u00e4ge nicht entfernt werden k\u00f6nnen
|
###FATAL_ERR_CONFIG_FILE_DOES_NOT_EXIST_26=The specified configuration file %s \
|
### does not exist or is not readable
|
###FATAL_ERR_CONFIG_FILE_CANNOT_VERIFY_EXISTENCE_27=An unexpected error occurred \
|
### while attempting to determine whether configuration file %s exists: %s
|
###FATAL_ERR_CONFIG_FILE_CANNOT_OPEN_FOR_READ_28=An error occurred while \
|
### attempting to open the configuration file %s for reading: %s
|
###FATAL_ERR_CONFIG_FILE_READ_ERROR_29=An error occurred while attempting to \
|
### read the contents of configuration file %s: %s
|
MILD_ERR_CONFIG_ATTR_OPTIONS_NOT_ALLOWED_30=Ung\u00fcltiges Konfigurationsattribut %s entdeckt: die einzige in der Directory-Server-Konfiguration zul\u00e4ssige Attributoption zum Anzeigen des Satzes anstehender Werte ist "pending"
|
###FATAL_ERR_CONFIG_FILE_INVALID_LDIF_ENTRY_31=An error occurred at or near line \
|
### %d while trying to parse the configuration from LDIF file %s: %s
|
###FATAL_ERR_CONFIG_FILE_EMPTY_32=The specified configuration file %s does not \
|
### appear to contain any configuration entries
|
###FATAL_ERR_CONFIG_FILE_INVALID_BASE_DN_33=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
|
###FATAL_ERR_CONFIG_FILE_GENERIC_ERROR_34=An unexpected error occurred while \
|
### attempting to process the Directory Server configuration file %s: %s
|
###FATAL_ERR_CONFIG_FILE_DUPLICATE_ENTRY_35=Configuration entry %s starting at \
|
### or near line %s in the LDIF configuration file %s has the same DN as another \
|
### entry already read from that file
|
###FATAL_ERR_CONFIG_FILE_NO_PARENT_36=Configuration entry %s starting at or near \
|
### line %d in the configuration LDIF file %s does not appear to have a parent \
|
### entry (expected parent DN was %s)
|
###FATAL_ERR_CONFIG_FILE_UNKNOWN_PARENT_37=The Directory Server was unable to \
|
### determine the parent DN for configuration entry %s starting at or near line \
|
### %d in the configuration LDIF file %s
|
###FATAL_ERR_CONFIG_CANNOT_DETERMINE_SERVER_ROOT_38=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
|
###SEVERE_ERR_CONFIG_FILE_WRITE_ERROR_39=An unexpected error occurred while \
|
### trying to write configuration entry %s to LDIF: %s
|
###SEVERE_ERR_CONFIG_FILE_CLOSE_ERROR_40=An unexpected error occurred while \
|
### trying to close the LDIF writer: %s
|
###SEVERE_ERR_CONFIG_FILE_UNWILLING_TO_IMPORT_41=The Directory Server \
|
### configuration may not be altered by importing a new configuration from LDIF
|
###FATAL_ERR_CONFIG_LOGGER_CANNOT_GET_BASE_42=An error occurred while attempting \
|
### to retrieve the base logger entry cn=Loggers,cn=config from the Directory \
|
### Server configuration: %s
|
###SEVERE_WARN_CONFIG_LOGGER_BASE_DOES_NOT_EXIST_43=The logger configuration \
|
### base cn=Loggers,cn=config does not exist in the Directory Server \
|
### configuration. Logging facilities will not be available until this entry is \
|
### created and the Directory Server is restarted
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ACCESS_LOGGERS_44=There are no active \
|
### access loggers defined in the Directory Server configuration. No access \
|
### logging will be performed
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ACTIVE_ERROR_LOGGERS_45=There are no active \
|
### error loggers defined in the Directory Server configuration. No error \
|
### logging will be performed
|
MILD_WARN_CONFIG_LOGGER_NO_ACTIVE_DEBUG_LOGGERS_46=In der Directory-Server-Konfiguration sind keine aktiven Debug-Logger definiert. Es wird kein Debug-Logging ausgef\u00fchrt.
|
###SEVERE_ERR_CONFIG_LOGGER_ENTRY_UNACCEPTABLE_47=Configuration entry %s does \
|
### not contain a valid logger configuration: %s. It will be ignored
|
INFO_CONFIG_UNKNOWN_UNACCEPTABLE_REASON_48=Unbekannte unzul\u00e4ssige Ursache
|
###SEVERE_ERR_CONFIG_LOGGER_CANNOT_CREATE_LOGGER_49=An error occurred while \
|
### attempting to create a Directory Server logger from the information in \
|
### configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_OBJECTCLASS_50=Configuration entry %s does \
|
### not contain a valid objectclass for a Directory Server access, error, or \
|
### debug logger definition
|
INFO_CONFIG_LOGGER_DESCRIPTION_CLASS_NAME_51=Vollqualifizierter Name der Java-Klasse, die das Directory-Server-Protokoll definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend das zugeordnete Protokoll aktiv ist, muss das Protokoll deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_LOGGER_NO_CLASS_NAME_52=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-java-class which \
|
### specifies the fully-qualified class name for the associated logger
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_CLASS_NAME_53=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ACCESS_LOGGER_CLASS_54=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server access logger: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ERROR_LOGGER_CLASS_55=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server error logger: %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_DEBUG_LOGGER_CLASS_56=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server debug logger: %s
|
INFO_CONFIG_LOGGER_DESCRIPTION_ENABLED_57=Gibt an, ob das Directory-Server-Protokoll aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_LOGGER_NO_ENABLED_ATTR_58=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-enabled which \
|
### indicates whether the logger should be enabled for use in the Directory \
|
### Server
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ENABLED_VALUE_59=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_CORE_DESCRIPTION_ALLOW_ATTR_EXCEPTIONS_60=Gibt an, ob Ausnahmen bei den Zeichen zul\u00e4ssig sind, die in Attributnamen verwendet werden. Standardm\u00e4\u00dfig d\u00fcrfen Attributnamen nur ASCII-Buchstaben, numerische Ziffern und Striche enthalten; au\u00dferdem m\u00fcssen sie mit einem Buchstaben beginnen. Wenn Ausnahmen beim Attributnamen aktiviert sind, ist auch das Unterstrich-Zeichen zul\u00e4ssig, und die Attributnamen d\u00fcrfen auch mit einer Ziffer beginnen. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ALLOW_EXCEPTIONS_61=Configuration entry %s has \
|
### an invalid value for configuration attribute \
|
### ds-cfg-allow-attribute-name-exceptions (it should be a Boolean value of true \
|
### or false): %s
|
INFO_CONFIG_CORE_DESCRIPTION_INVALID_SYNTAX_BEHAVIOR_62=Verhalten von Directory-Server, wenn ein Attribut gefunden wird, dessen Wert nicht der Syntax f\u00fcr das Attribut entspricht. Zul\u00e4ssige Werte f\u00fcr dieses Attribut sind "reject", um den ung\u00fcltigen Wert zur\u00fcckzuweisen, "warn", um den ung\u00fcltigen Wert zu akzeptieren aber dabei eine Warnmeldung ins Protokoll zu schreiben, oder "accept", um den ung\u00fcltigen Wert ohne Warnung zu akzeptieren. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ENFORCE_STRICT_SYNTAX_63=Configuration entry \
|
### %s has an invalid value for configuration attribute \
|
### ds-cfg-invalid-attribute-syntax-behavior (it should be one of "accept", \
|
### "reject", or "warn" ): %s
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_PENDING_VALUE_SETS_64=Konfigurationseintrag %s enth\u00e4lt anscheinend mehrere anstehende Wertereihen
|
MILD_ERR_CONFIG_ATTR_MULTIPLE_ACTIVE_VALUE_SETS_65=Konfigurationseintrag %s enth\u00e4lt anscheinend mehrere aktive Wertereihen
|
MILD_ERR_CONFIG_ATTR_NO_ACTIVE_VALUE_SET_66=Konfigurationsattribut %s enth\u00e4lt keine aktive Wertereihe
|
MILD_ERR_CONFIG_ATTR_INT_INVALID_TYPE_67=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als Ganzzahl geparst werden, da das Element zu einem unzul\u00e4ssigen Typ (%s) geh\u00f6rt
|
MILD_ERR_CONFIG_ATTR_INT_INVALID_ARRAY_TYPE_68=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Reihe von Ganzzahlwerten geparst werden, da das Array Elemente unzul\u00e4ssigen Typs (%s) enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_INVALID_STRING_VALUE_69=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als Zeichenkettenwert geparst werden: %s
|
MILD_ERR_CONFIG_ATTR_STRING_INVALID_TYPE_70=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als Zeichenkettenwert geparst werden, da das Element zu einem unzul\u00e4ssigen Typ (%s) geh\u00f6rt
|
MILD_ERR_CONFIG_ATTR_STRING_INVALID_ARRAY_TYPE_71=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Reihe von Zeichenkettenwerten geparst werden, da das Array Elemente unzul\u00e4ssigen Typs (%s) enth\u00e4lt
|
MILD_ERR_CONFIG_ATTR_INT_WITH_UNIT_INVALID_TYPE_72=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als Ganzzahl mit Einheitswert geparst werden, da das Element zu einem unzul\u00e4ssigen Typ (%s) geh\u00f6rt
|
MILD_ERR_CONFIG_JMX_ATTR_NO_VALUE_73=Konfigurationseintrag %s enth\u00e4lt keinen Wert f\u00fcr Attribut %s
|
MILD_ERR_CONFIG_JMX_ATTR_NO_ATTR_74=Im Konfigurationseintrag %s ist das Attribut %s nicht enthalten (bzw. es ist enthalten, es kann aber nicht mit JMX darauf zugegriffen werden)
|
MILD_ERR_CONFIG_JMX_CANNOT_GET_CONFIG_ENTRY_75=Konfigurationseintrag %s kann nicht f\u00fcr Zugriff \u00fcber JMX abgerufen werden: %s
|
MILD_ERR_CONFIG_JMX_ATTR_INVALID_VALUE_76=Versuchte Aktualisierung des Attributs %s des Konfigurationseintrags %s \u00fcber JMX h\u00e4tte zu einem ung\u00fcltigen Wert gef\u00fchrt: %s
|
MILD_ERR_CONFIG_JMX_UNACCEPTABLE_CONFIG_77=Aktualisierung des Konfigurationseintrags %s \u00fcber JMX h\u00e4tte zu einer ung\u00fcltigen Konfiguration gef\u00fchrt: %s
|
MILD_ERR_CONFIG_JMX_NO_METHOD_78=Es wurde keine Methode %s f\u00fcr nicht aufrufbare Komponenten beim Konfigurationseintrag %s registriert
|
MILD_ERR_CONFIG_CANNOT_GET_CONFIG_ENTRY_79=Fehler beim Versuch, Konfigurationseintrag %s abzurufen: %s
|
INFO_CONFIG_SET_ATTRIBUTE_80=Der Wert des Konfigurationsattributs %s wurde auf %s im Konfigurationseintrag %s gesetzt
|
MILD_ERR_CONFIG_CHANGE_NOT_SUCCESSFUL_81=Der Versuch, den Konfigurationseintrag %s zu aktualisieren, ist fehlgeschlagen. Es sind ein oder mehrere Fehler aufgetreten: %s
|
###SEVERE_ERR_CONFIG_LOGGER_NO_FILE_NAME_82=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-log-file which \
|
### specifies the log file name for the associated logger
|
###SEVERE_ERR_CONFIG_JMX_CANNOT_REGISTER_MBEAN_83=The Directory Server could not \
|
### register a JMX MBean for the component associated with configuration entry \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_LDIF_WRITE_ERROR_84=An unexpected error occurred while \
|
### trying to export the Directory Server configuration to LDIF: %s
|
INFO_CONFIG_WORK_QUEUE_DESCRIPTION_NUM_THREADS_85=Anzahl der Worker-Threads, die zur Verarbeitung der Anfragen verwendet werden. Sie steuern die Zahl der Vorg\u00e4nge, die der Server gleichzeitig verarbeiten kann. Der optimale Wert h\u00e4ngt vom Systemtyp, auf dem der Server ausgef\u00fchrt wird, sowie von der zu verarbeitenden Arbeitslast ab. Er wird am besten durch Leistungstests ermittelt. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
INFO_CONFIG_WORK_QUEUE_DESCRIPTION_MAX_CAPACITY_86=Maximale Anzahl gleichzeitig anstehender Anfragen in der Arbeitswarteschlange, w\u00e4hrend alle Worker-Threads mit der Verarbeitung anderer Vorg\u00e4nge besch\u00e4ftigt sind. Wenn dieses Limit erreicht wird, werden neue Anfragen zur\u00fcckgewiesen. Der Wert 0 gibt an, dass kein Limit gesetzt ist. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_NUM_WORKER_THREADS_87=An error \
|
### occurred while attempting to retrieve the value of the \
|
### ds-cfg-num-worker-threads attribute from the %s entry, which is used to \
|
### specify the number of worker threads to service the work queue: %s. The \
|
### Directory Server will use the default value of 24
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_DETERMINE_QUEUE_CAPACITY_88=An error \
|
### occurred while attempting to retrieve the value of the \
|
### ds-cfg-max-work-queue-capacity attribute from the %s entry, which is used to \
|
### specify the maximum number of pending operations that may be held in the work \
|
### queue: %s. The Directory Server will use the default value of 0
|
###SEVERE_WARN_CONFIG_WORK_QUEUE_NUM_THREADS_INVALID_VALUE_89=The value of \
|
### configuration attribute ds-cfg-num-worker-threads in configuration entry %s \
|
### has an invalid value (%d). This attribute requires an integer value greater \
|
### than zero
|
###SEVERE_WARN_CONFIG_WORK_QUEUE_CAPACITY_INVALID_VALUE_90=The value of \
|
### configuration attribute ds-cfg-max-work-queue-capacity in configuration entry \
|
### %s has an invalid value (%d). This attribute requires an integer value \
|
### greater than or equal to zero
|
INFO_CONFIG_WORK_QUEUE_CREATED_THREADS_91=%d zus\u00e4tzliche Worker-Threads wurden erstellt, um die Gesamtzahl der verf\u00fcgbaren Threads auf %d zu erh\u00f6hen
|
INFO_CONFIG_WORK_QUEUE_DESTROYING_THREADS_92=%d Worker-Threads werden so bald wie m\u00f6glich beendet (es kann ein paar Sekunden dauern, bis die Threads tats\u00e4chlich beendet werden), um die Gesamtzahl der verf\u00fcgbaren Threads auf %d zu verringern
|
INFO_CONFIG_WORK_QUEUE_NEW_CAPACITY_93=Die Kapazit\u00e4t der Arbeitswarteschlange wurde aktualisiert. Der neue Wert betr\u00e4gt %d
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_TOO_MANY_FAILURES_94=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
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_CANNOT_CREATE_MONITOR_95=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
|
INFO_CONFIG_DESCRIPTION_BACKEND_DIRECTORY_96=Name des Verzeichnisses, in dem Backend-Datenbankdateien gespeichert werden
|
###SEVERE_ERR_CONFIG_BACKEND_NO_DIRECTORY_97=Configuration entry %s does not \
|
### contain a valid value for configuration attribute ds-cfg-db-directory
|
MILD_ERR_CONFIG_ATTR_DN_NULL_98=F\u00fcr DN-Konfigurationsattribut %s wurde ein Nullwert angegeben
|
MILD_ERR_CONFIG_ATTR_DN_CANNOT_PARSE_99=Fehler beim Versuch, Wert "%s" des Attributs %s als DN zu parsen: %s
|
MILD_ERR_CONFIG_ATTR_INVALID_DN_VALUE_100=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als DN geparst werden: %s
|
MILD_ERR_CONFIG_ATTR_DN_INVALID_TYPE_101=Wert %s f\u00fcr Konfigurationsattribut %s kann nicht als DN geparst werden, da das Element zu einem unzul\u00e4ssigen Typ (%s) geh\u00f6rt
|
MILD_ERR_CONFIG_ATTR_DN_INVALID_ARRAY_TYPE_102=Wert f\u00fcr Konfigurationsattribut %s kann nicht als Reihe von DN-Werten geparst werden, da das Array Elemente unzul\u00e4ssigen Typs (%s) enth\u00e4lt
|
###FATAL_ERR_CONFIG_CANNOT_REGISTER_AS_PRIVATE_SUFFIX_103=An unexpected error \
|
### occurred while trying to register the configuration handler base DN "%s" as a \
|
### private suffix with the Directory Server: %s
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_GET_CONFIG_BASE_104=An error occurred while \
|
### trying to retrieve configuration entry cn=Backends,cn=config in order to \
|
### initialize the Directory Server backends: %s
|
###SEVERE_ERR_CONFIG_BACKEND_BASE_DOES_NOT_EXIST_105=The entry \
|
### cn=Backends,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_BACKEND_ENTRY_DOES_NOT_HAVE_BACKEND_CONFIG_106=Configuration \
|
### entry %s exists below the backend configuration root of cn=Backends,cn=config \
|
### but does not have objectclass ds-cfg-backend that is required for a Directory \
|
### Server backend. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_BACKEND_ERROR_INTERACTING_WITH_BACKEND_ENTRY_107=An \
|
### unexpected error occurred while interacting with backend configuration entry \
|
### %s: %s
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_ENABLED_108=Gibt an, ob diese Backend zur Verwendung im Directory-Server aktiviert werden soll. Kann ge\u00e4ndert werden, w\u00e4hrend der Directory-Server online ist; wenn ein Backend aber deaktiviert ist, ist es nicht einsatzbereit
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_CLASS_109=Vollqualifizierter Name der Java-Klasse, die die Kernlogik f\u00fcr die Implementierung dieses Backends bereitstellt. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn das Backend deaktiviert und wieder reaktiviert oder der Server neu gestartet wird
|
###SEVERE_WARN_CONFIG_BACKEND_NO_ENABLED_ATTR_110=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-enabled, which is used to indicate \
|
### whether the backend should be enabled or disabled. Without this attribute, \
|
### it will default to being disabled
|
INFO_CONFIG_BACKEND_DISABLED_111=Das im Konfigurationseintrag %s definierte Backend ist als deaktiviert markiert und wird daher nicht verwendet
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_ENABLED_STATE_112=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
|
###SEVERE_ERR_CONFIG_BACKEND_NO_CLASS_ATTR_113=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-java-class, which is used to specify the \
|
### name of the class used to provide the backend implementation. The backend \
|
### associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_GET_CLASS_114=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for backend %s: %s. This backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_INSTANTIATE_115=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
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_INITIALIZE_116=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
|
###SEVERE_ERR_CONFIG_BACKEND_CLASS_NOT_BACKEND_117=The class %s specified in \
|
### configuration entry %s does not contain a valid Directory Server backend \
|
### implementation
|
NOTICE_CONFIG_BACKEND_ACTION_REQUIRED_TO_CHANGE_CLASS_118=Durch die angeforderte \u00c4nderung am Konfigurationseintrag %s wird die Klasse des zugeordneten Backends von %s nach %s ge\u00e4ndert. Diese \u00c4nderung tritt erst in Kraft, wenn das Backend deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
NOTICE_CONFIG_BACKEND_CANNOT_REMOVE_BACKEND_WITH_SUBORDINATES_119=Das in Konfigurationseintrag %s definierte Backend hat ein oder mehrere untergeordnete Backends. Ein Backend kann nicht entfernt werden, wenn es untergeordnete Backends hat
|
INFO_CONFIG_CORE_DESCRIPTION_MAX_ALLOWED_CONNECTIONS_120=Die maximale Anzahl an Client-Verbindungen, die gleichzeitig zum Directory-Server hergestellt werden k\u00f6nnen. Ein Wert kleiner gleich Null gibt an, dass es keine Begrenzung gibt. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
INFO_CONFIG_LOGGER_CLASS_ACTION_REQUIRED_122=Die angeforderte \u00c4nderung des Protokollklassennamens von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn das Protokoll deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_LOGGER_EXISTS_123=Neuer Protokolleintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderes Protokoll mit dem DN registriert ist
|
MILD_ERR_CONFIG_LOGGER_ACCESS_INITIALIZATION_FAILED_124=Fehler beim Versuch, eine Instanz der Klasse %s als Zugriffsprotokoll zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_LOGGER_ERROR_INITIALIZATION_FAILED_125=Fehler beim Versuch, eine Instanz der Klasse %s als Fehlerprotokoll zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_LOGGER_DEBUG_INITIALIZATION_FAILED_126=Fehler beim Versuch, eine Instanz der Klasse %s als Debug-Protokoll zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
###FATAL_ERR_CONFIG_MONITOR_CANNOT_GET_BASE_127=An error occurred while \
|
### attempting to retrieve the base monitor entry cn=Monitor Providers,cn=config \
|
### from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_MONITOR_BASE_DOES_NOT_EXIST_128=The monitor configuration \
|
### base cn=Monitor Providers,cn=config does not exist in the Directory Server \
|
### configuration. Only limited monitoring information will be available
|
###SEVERE_ERR_CONFIG_MONITOR_ENTRY_UNACCEPTABLE_129=Configuration entry %s does \
|
### not contain a valid monitor provider configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_MONITOR_CANNOT_CREATE_MONITOR_130=An error occurred while \
|
### attempting to create a Directory Server monitor provider from the information \
|
### in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_OBJECTCLASS_131=Configuration entry %s does \
|
### not contain the ds-cfg-monitor-provider objectclass, which is required for \
|
### monitor provider definitions
|
INFO_CONFIG_MONITOR_DESCRIPTION_CLASS_NAME_132=Vollqualifizierter Name der Java-Klasse, die den Directory-Server-\u00dcberwachungsanbieter definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend der zugeordnete Monitor aktiv ist, muss der Monitor deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_MONITOR_NO_CLASS_NAME_133=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class name \
|
### for the associated monitor provider
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_NAME_134=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_CLASS_135=Class %s specified in \
|
### configuration entry %s does not contain a valid monitor provider \
|
### implementation: %s
|
INFO_CONFIG_MONITOR_DESCRIPTION_ENABLED_136=Gibt an, ob dieser Directory-Server-\u00dcberwachungsanbieter aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_MONITOR_NO_ENABLED_ATTR_137=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the monitor provider \
|
### should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_MONITOR_INVALID_ENABLED_VALUE_138=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_MONITOR_CLASS_ACTION_REQUIRED_139=Die angeforderte \u00c4nderung des Monitor-Klassennamens von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der \u00dcberwachungsanbieter deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_MONITOR_INITIALIZATION_FAILED_140=Fehler beim Versuch, eine Instanz der Klasse %s als \u00dcberwachungsanbieter zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_MONITOR_EXISTS_141=Neuer \u00dcberwachungsanbieter-Eintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer \u00dcberwachungsanbieter mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CONFIG_BASE_142=An error occurred \
|
### while trying to retrieve configuration entry cn=Connection Handlers,cn=config \
|
### in order to initialize the Directory Server backends: %s
|
###SEVERE_ERR_CONFIG_CONNHANDLER_BASE_DOES_NOT_EXIST_143=The entry cn=Connection \
|
### Handlers,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_CONNHANDLER_ENTRY_DOES_NOT_HAVE_CONNHANDLER_CONFIG_144=Configuration \
|
### entry %s exists below the connection handler configuration root of \
|
### cn=Connection Handlers,cn=config but does not have objectclass \
|
### ds-cfg-connection-handler that is required for a Directory Server connection \
|
### handler. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_CONNHANDLER_ERROR_INTERACTING_WITH_CONNHANDLER_ENTRY_145=An \
|
### unexpected error occurred while interacting with connection handler \
|
### configuration entry %s: %s
|
INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_ENABLED_146=Gibt an, ob diese Verbindungsbehandlungsroutine zur Verwendung im Directory-Server aktiviert werden soll. Kann ge\u00e4ndert werden, w\u00e4hrend der Directory-Server online ist; wenn eine Verbindungsbehandlungsroutine aber deaktiviert ist, ist sie nicht einsatzbereit
|
INFO_CONFIG_CONNHANDLER_ATTR_DESCRIPTION_CLASS_147=Vollqualifizierter Name der Java-Klasse, die die Kernlogik f\u00fcr die Implementierung dieser Verbindungsbehandlungsroutine bereitstellt. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn die Verbindungsbehandlungsroutine deaktiviert und wieder reaktiviert oder der Server neu gestartet wird
|
###SEVERE_WARN_CONFIG_CONNHANDLER_NO_ENABLED_ATTR_148=Connection handler \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-enabled, which is used to indicate whether the \
|
### connection handler should be enabled or disabled. Without this attribute, it \
|
### will default to being disabled
|
INFO_CONFIG_CONNHANDLER_DISABLED_149=Die im Konfigurationseintrag %s definierte Verbindungsbehandlungsroutine ist als deaktiviert markiert und wird daher nicht verwendet
|
###SEVERE_ERR_CONFIG_CONNHANDLER_UNABLE_TO_DETERMINE_ENABLED_STATE_150=An \
|
### unexpected error occurred while attempting to determine whether the \
|
### connection handler associated with configuration entry %s should be enabled \
|
### or disabled: %s. It will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_NO_CLASS_ATTR_151=Connection handler \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-java-class, which is used to specify the name of the \
|
### class used to provide the connection handler implementation. The connection \
|
### handler associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_GET_CLASS_152=An unexpected error \
|
### occurred while trying to determine the name of the Java class that contains \
|
### the implementation for connection handler %s: %s. This connection handler \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INSTANTIATE_153=The Directory Server was \
|
### unable to load class %s and use it to create a connection handler instance as \
|
### defined in configuration entry %s. The error that occurred was: %s. This \
|
### connection handler will be disabled
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CANNOT_INITIALIZE_154=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
|
###SEVERE_ERR_CONFIG_CONNHANDLER_UNACCEPTABLE_CONFIG_155=The configuration for \
|
### the connection handler defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_BACKEND_UNACCEPTABLE_CONFIG_156=The configuration for the \
|
### backend defined in configuration entry %s was not acceptable according to its \
|
### internal validation. However, no specific information is available regarding \
|
### the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_MONITOR_UNACCEPTABLE_CONFIG_157=The configuration for the \
|
### monitor provider defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_LOGGER_UNACCEPTABLE_CONFIG_158=The configuration for the \
|
### logger defined in configuration entry %s was not acceptable according to its \
|
### internal validation. However, no specific information is available regarding \
|
### the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_CONNHANDLER_CLASS_NOT_CONNHANDLER_159=The class %s \
|
### specified in configuration entry %s does not contain a valid Directory Server \
|
### connection handler implementation
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_MR_BASE_160=An error occurred while \
|
### trying to retrieve configuration entry cn=Matching Rules,cn=config in order \
|
### to initialize the Directory Server matching rules: %s
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_BASE_DOES_NOT_EXIST_161=The entry cn=Matching \
|
### Rules,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_MATCHING_RULES_162=No child entries were found \
|
### below the entry cn=Matching Rules,cn=config to define the matching rules for \
|
### use in the Directory Server. This is an error, because the Directory Server \
|
### must have matching rules defined to function properly
|
###SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_MR_CONFIG_163=Configuration \
|
### entry %s exists below the matching rule configuration root of cn=Matching \
|
### Rules,cn=config but does not have objectclass ds-cfg-matching-rule that is \
|
### required for a Directory Server matching rule. This configuration entry will \
|
### be ignored
|
INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_ENABLED_164=Gibt an, ob diese \u00dcbereinstimmungsregel zur Verwendung im Directory-Server aktiviert werden soll. Kann ge\u00e4ndert werden, w\u00e4hrend der Directory-Server online ist. Wenn eine \u00dcbereinstimmungsregel deaktiviert wird, nachdem sie f\u00fcr ein oder mehrere Attribute verwendet wurde, gilt die \u00dcbereinstimmung f\u00fcr die Attribute ggf. nicht mehr wie erwartet
|
INFO_CONFIG_SCHEMA_MR_ATTR_DESCRIPTION_CLASS_165=Vollqualifizierter Name der Java-Klasse, die die Kernlogik f\u00fcr die Implementierung dieser \u00dcbereinstimmungsregel bereitstellt. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn die \u00dcbereinstimmungsregel deaktiviert und wieder reaktiviert oder der Server neu gestartet wird. Auch \u00c4nderungen an der \u00dcbereinstimmungsregelklasse von \u00dcbereinstimmungsregeln, die bereits f\u00fcr ein oder mehrere Attribute verwendet wurden, k\u00f6nnen zu unerwarteten Ergebnissen bei der \u00dcbereinstimmung dieser Attribute f\u00fchren
|
###SEVERE_WARN_CONFIG_SCHEMA_MR_NO_ENABLED_ATTR_166=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-enabled, which is \
|
### used to indicate whether the matching rule should be enabled or disabled. \
|
### Without this attribute, it will default to being disabled
|
INFO_CONFIG_SCHEMA_MR_DISABLED_167=Die im Konfigurationseintrag %s definierte \u00dcbereinstimmungsregel ist als deaktiviert markiert und wird daher nicht verwendet. Wenn sie bereits f\u00fcr ein oder mehrere Attribute verwendet wurde, kann es sein, dass die \u00dcbereinstimmung f\u00fcr die Werte dieser Attribute ggf. nicht funktioniert
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_UNABLE_TO_DETERMINE_ENABLED_STATE_168=An \
|
### unexpected error occurred while attempting to determine whether the matching \
|
### rule associated with configuration entry %s should be enabled or disabled: \
|
### %s. It will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_NO_CLASS_ATTR_169=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-java-class, which is used \
|
### to specify the name of the class used to provide the matching rule \
|
### implementation. The matching rule associated with this configuration entry \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_GET_CLASS_170=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for matching rule %s: %s. This matching rule will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INSTANTIATE_171=The Directory Server was \
|
### unable to load class %s and use it to create a matching rule instance as \
|
### defined in configuration entry %s. The error that occurred was: %s. This \
|
### matching rule will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_MR_CANNOT_INITIALIZE_172=An error occurred while \
|
### trying to initialize a matching rule loaded from class %s with the \
|
### information in configuration entry %s: %s. This matching rule will be \
|
### disabled
|
###SEVERE_WARN_CONFIG_SCHEMA_MR_CONFLICTING_MR_173=The matching rule defined in \
|
### configuration entry %s conflicts with another matching rule defined in the \
|
### server configuration: %s. This matching rule will not be used
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_GET_SYNTAX_BASE_174=An error occurred while \
|
### trying to retrieve configuration entry cn=Syntaxes,cn=config in order to \
|
### initialize the Directory Server attribute syntaxes: %s
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_BASE_DOES_NOT_EXIST_175=The entry \
|
### cn=Syntaxes,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_SYNTAXES_176=No child entries were found below \
|
### the entry cn=Syntaxes,cn=config to define the attribute syntaxes for use in \
|
### the Directory Server. This is an error, because the Directory Server must \
|
### have syntaxes defined to function properly
|
###SEVERE_WARN_CONFIG_SCHEMA_ENTRY_DOES_NOT_HAVE_SYNTAX_CONFIG_177=Configuration \
|
### entry %s exists below the attribute syntax configuration root of \
|
### cn=Syntaxes,cn=config but does not have objectclass ds-cfg-attribute-syntax \
|
### that is required for a Directory Server attribute syntax. This configuration \
|
### entry will be ignored
|
INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_ENABLED_178=Gibt an, ob diese Attributsyntax zur Verwendung im Directory-Server aktiviert werden soll. Kann ge\u00e4ndert werden, w\u00e4hrend der Directory-Server online ist. Wenn eine Syntax deaktiviert wird, nachdem sie f\u00fcr ein oder mehrere Attribute verwendet wurde, gilt die \u00dcbereinstimmung f\u00fcr die Attribute ggf. nicht mehr wie erwartet
|
INFO_CONFIG_SCHEMA_SYNTAX_ATTR_DESCRIPTION_CLASS_179=Vollqualifizierter Name der Java-Klasse, die die Kernlogik f\u00fcr die Implementierung dieser Attributsyntax bereitstellt. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn die Syntax deaktiviert und wieder reaktiviert oder der Server neu gestartet wird. Auch \u00c4nderungen an der Syntaxklasse von Attributsyntaxen, die bereits f\u00fcr ein oder mehrere Attribute verwendet wurden, k\u00f6nnen zu unerwarteten Ergebnissen bei der \u00dcbereinstimmung dieser Attribute f\u00fchren
|
###SEVERE_WARN_CONFIG_SCHEMA_SYNTAX_NO_ENABLED_ATTR_180=Attribute syntax \
|
### configuration entry %s does not contain attribute ds-cfg-enabled, \
|
### which is used to indicate whether the syntax should be enabled or disabled. \
|
### Without this attribute, it will default to being disabled
|
INFO_CONFIG_SCHEMA_SYNTAX_DISABLED_181=Die im Konfigurationseintrag %s definierte Attributsyntax ist als deaktiviert markiert und wird daher nicht verwendet. Wenn sie bereits f\u00fcr ein oder mehrere Attribute verwendet wurde, kann es sein, dass die \u00dcbereinstimmung f\u00fcr die Werte dieser Attribute ggf. nicht funktioniert
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_UNABLE_TO_DETERMINE_ENABLED_STATE_182=An \
|
### unexpected error occurred while attempting to determine whether the attribute \
|
### syntax associated with configuration entry %s should be enabled or disabled: \
|
### %s. It will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_NO_CLASS_ATTR_183=Matching rule configuration \
|
### entry %s does not contain attribute ds-cfg-java-class, which is used to \
|
### specify the name of the class that provides the attribute syntax \
|
### implementation. The syntax associated with this configuration entry will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_GET_CLASS_184=An unexpected error \
|
### occurred while trying to determine the name of the Java class that contains \
|
### the implementation for attribute syntax %s: %s. This syntax will be \
|
### disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INSTANTIATE_185=The Directory Server \
|
### was unable to load class %s and use it to create an attribute syntax instance \
|
### as defined in configuration entry %s. The error that occurred was: %s. \
|
### This syntax will be disabled
|
###SEVERE_ERR_CONFIG_SCHEMA_SYNTAX_CANNOT_INITIALIZE_186=An error occurred while \
|
### trying to initialize an attribute syntax loaded from class %s with the \
|
### information in configuration entry %s: %s. This syntax will be disabled
|
###SEVERE_WARN_CONFIG_SCHEMA_SYNTAX_CONFLICTING_SYNTAX_187=The attribute syntax \
|
### defined in configuration entry %s conflicts with another syntax defined in \
|
### the server configuration: %s. This attribute syntax will not be used
|
###SEVERE_ERR_CONFIG_SCHEMA_NO_SCHEMA_DIR_188=Unable to read the Directory \
|
### Server schema definitions because the schema directory %s does not exist
|
###SEVERE_ERR_CONFIG_SCHEMA_DIR_NOT_DIRECTORY_189=Unable to read the Directory \
|
### Server schema definitions because the schema directory %s exists but is not a \
|
### directory
|
###SEVERE_ERR_CONFIG_SCHEMA_CANNOT_LIST_FILES_190=Unable to read the Directory \
|
### Server schema definitions from directory %s or %s because an unexpected error \
|
### occurred while trying to list the files in that directory: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_OPEN_FILE_191=Schema configuration file %s \
|
### in directory %s cannot be parsed because an unexpected error occurred while \
|
### trying to open the file for reading: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_READ_LDIF_ENTRY_192=Schema configuration \
|
### file %s in directory %s cannot be parsed because an unexpected error occurred \
|
### while trying to read its contents as an LDIF entry: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_ATTR_TYPE_193=Unable to parse an \
|
### attribute type definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_ATTR_TYPE_194=An attribute type read \
|
### from schema configuration file %s conflicts with another attribute type \
|
### already read into the schema: %s. The later attribute type definition will \
|
### be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_OC_195=An objectclass read from schema \
|
### configuration file %s conflicts with another objectclass already read into \
|
### the schema: %s. The later objectclass definition will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_OC_196=An objectclass read from schema \
|
### configuration file %s could not be parsed: %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_STRUCTURAL_CLASS_BEHAVIOR_197=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-single-structural-objectclass-behavior (it should be one of "accept", \
|
### "reject", or "warn" ): %s
|
INFO_CONFIG_CORE_DESCRIPTION_CHECK_SCHEMA_198=Gibt an, ob der Directory-Server Schemapr\u00fcfungen f\u00fcr Aktualisierungsvorg\u00e4nge durchf\u00fchren soll, um sicherzustellen, dass die Eintr\u00e4ge f\u00fcr die Schemakonfiguration des Servers zul\u00e4ssig sind (z.\u00a0B. dass alle erforderlichen Attribute und keine verbotenen Attribute vorhanden sind). Es ist nicht empfohlen, die Schemapr\u00fcfung zu deaktivieren, da dadurch ung\u00fcltige Eintr\u00e4ge in den Server gelangen k\u00f6nnen. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_CHECK_SCHEMA_199=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-check-schema (it should be a \
|
### Boolean value of true or false): %s
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CANNOT_INSTALL_DEFAULT_CACHE_200=An unexpected \
|
### error occurred that prevented the server from installing its default entry \
|
### cache framework: %s
|
###SEVERE_WARN_CONFIG_ENTRYCACHE_NO_CONFIG_ENTRY_201=The entry cache \
|
### configuration entry "cn=Entry Caches,cn=config" does not exist in the \
|
### Directory Server configuration. No entry cache will be available until this \
|
### entry is created with a valid entry cache configuration
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CANNOT_INITIALIZE_CACHE_202=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
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CONFIG_NOT_ACCEPTABLE_203=The configuration for \
|
### the entry cache defined in configuration entry %s was not acceptable: %s
|
###SEVERE_ERR_CONFIG_ENTRYCACHE_CONFIG_LEVEL_NOT_ACCEPTABLE_204=The configuration \
|
### for the entry cache defined in configuration entry %s was not acceptable: \
|
### the entry cache level %d is already in use
|
INFO_WARN_CONFIG_ENTRYCACHE_NO_MONITOR_CONFIG_ENTRY_205=Die Konfiguration des Eintragsspeichers %s \u00dcberwachungsanbieter ist nicht verf\u00fcgbar. Der \u00dcberwachungsanbieter %s wird daher nicht aktiviert
|
INFO_WARN_CONFIG_ENTRYCACHE_MONITOR_CONFIG_DISABLED_206=Die Konfiguration des Eintragsspeichers %s \u00dcberwachungsanbieter wurde deaktiviert. Der \u00dcberwachungsanbieter %s wird daher nicht aktiviert
|
MILD_ERR_CONFIG_ENTRY_CANNOT_REMOVE_CHILD_215=Unerwarteter Fehler beim Versuch, Eintrag %s als untergeordneten Eintrag von Konfigurationseintrag %s zu entfernen: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_NAME_FORM_216=Unable to parse a name \
|
### form definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_NAME_FORM_217=A name form read from \
|
### schema configuration file %s conflicts with another name form already read \
|
### into the schema: %s. The later name form definition will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_DCR_218=Unable to parse a DIT content \
|
### rule definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_DCR_219=A DIT content rule read from \
|
### schema configuration file %s conflicts with another DIT content rule already \
|
### read into the schema: %s. The later DIT content rule definition will be \
|
### used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_DSR_220=Unable to parse a DIT \
|
### structure rule definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_DSR_221=A DIT structure rule read from \
|
### schema configuration file %s conflicts with another DIT structure rule \
|
### already read into the schema: %s. The later DIT structure rule definition \
|
### will be used
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_MRU_222=Unable to parse a matching \
|
### rule use definition from schema configuration file %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_MRU_223=A matching rule use read from \
|
### schema configuration file %s conflicts with another matching rule use already \
|
### read into the schema: %s. The later matching rule use definition will be \
|
### used
|
###SEVERE_WARN_CONFIG_LOGGER_NO_ROTATION_POLICY_224=No file rotation policy has \
|
### been defined in configuration entry %s. No log rotation will take place
|
###SEVERE_ERR_CONFIG_LOGGER_NO_SIZE_LIMIT_225=No size limit has been defined for \
|
### the size based file rotation policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_NO_TIME_LIMIT_226=No time limit has been defined for \
|
### the time based file rotation policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_ROTATION_POLICY_227=An invalid file rotation \
|
### policy %s has been defined in configuration entry %s
|
MILD_ERR_CONFIG_ATTR_READ_ONLY_228=Konfigurationsattribut %s ist schreibgesch\u00fctzt. Seine Werte k\u00f6nnen nicht ge\u00e4ndert werden
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CONFIG_BASE_229=An error occurred while \
|
### trying to retrieve configuration entry cn=Plugins,cn=config in order to \
|
### initialize the Directory Server plugins: %s
|
###SEVERE_ERR_CONFIG_PLUGIN_BASE_DOES_NOT_EXIST_230=The entry \
|
### cn=Plugins,cn=config does not appear to exist in the Directory Server \
|
### configuration. This is a required entry
|
###SEVERE_WARN_CONFIG_PLUGIN_ENTRY_DOES_NOT_HAVE_PLUGIN_CONFIG_231=Configuration \
|
### entry %s exists below the plugin configuration root of cn=Plugins,cn=config \
|
### but does not have objectclass ds-cfg-backend that is required for a Directory \
|
### Server plugin. This configuration entry will be ignored
|
###SEVERE_ERR_CONFIG_PLUGIN_ERROR_INTERACTING_WITH_PLUGIN_ENTRY_232=An \
|
### unexpected error occurred while interacting with backend configuration entry \
|
### %s: %s
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_ENABLED_233=Gibt an, ob diese Plugin zur Verwendung im Directory-Server aktiviert werden soll. Kann ge\u00e4ndert werden, w\u00e4hrend der Directory-Server online ist. Die \u00c4nderungen treten sofort in Kraft
|
###SEVERE_WARN_CONFIG_PLUGIN_NO_ENABLED_ATTR_234=Plugin configuration entry %s \
|
### does not contain attribute ds-cfg-enabled, which is used to indicate \
|
### whether the plugin should be enabled or disabled. Without this attribute, it \
|
### will default to being disabled
|
INFO_CONFIG_PLUGIN_DISABLED_235=Das im Konfigurationseintrag %s definierte Plugin ist als deaktiviert markiert und wird daher nicht verwendet
|
###SEVERE_ERR_CONFIG_PLUGIN_UNABLE_TO_DETERMINE_ENABLED_STATE_236=An unexpected \
|
### error occurred while attempting to determine whether the plugin associated \
|
### with configuration entry %s should be enabled or disabled: %s. It will be \
|
### disabled
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_PLUGIN_TYPE_237=Plugin-Typen f\u00fcr diese Plugin, die steuern, wann das Plugin w\u00e4hrend der Verarbeitung aufgerufen wird. Dieser Wert ist w\u00e4hrend des Ladens und Initialisierens des Plugins schreibgesch\u00fctzt. \u00c4nderungen an diesem Attribut treten erst in Kraft, wenn das Plugin deaktiviert und wieder reaktiviert oder der Server neu gestartet wird
|
INFO_CONFIG_PLUGIN_ATTR_DESCRIPTION_CLASS_238=Vollqualifizierter Name der Java-Klasse, die die Kernlogik f\u00fcr Implementierung dieses Plugins bereitstellt. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn das Plugin deaktiviert und wieder reaktiviert oder der Server neu gestartet wird
|
###SEVERE_ERR_CONFIG_PLUGIN_NO_PLUGIN_TYPES_239=Plugin configuration entry %s \
|
### does not contain attribute ds-cfg-plugin-type, which is used to specify the \
|
### name(s) of the plugin type(s) for the plugin. This is a required attribute, \
|
### so this plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_INVALID_PLUGIN_TYPE_240=Plugin configuration entry \
|
### %s has an invalid value %s for attribute ds-cfg-plugin-type that does not \
|
### name a valid plugin type. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_PLUGIN_TYPES_241=An unexpected error \
|
### occurred while trying to determine the set of plugin types for the plugin \
|
### defined in configuration entry %s: %s. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_NO_CLASS_ATTR_242=Plugin configuration entry %s does \
|
### not contain attribute ds-cfg-java-class, which is used to specify the name \
|
### of the class used to provide the plugin implementation. The plugin \
|
### associated with this configuration entry will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_GET_CLASS_243=An unexpected error occurred \
|
### while trying to determine the name of the Java class that contains the \
|
### implementation for plugin %s: %s. This plugin will be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INSTANTIATE_244=The Directory Server was \
|
### unable to load class %s and use it to create a plugin instance as defined in \
|
### configuration entry %s. The error that occurred was: %s. This plugin will \
|
### be disabled
|
###SEVERE_ERR_CONFIG_PLUGIN_CANNOT_INITIALIZE_245=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
|
INFO_CONFIG_CORE_DESCRIPTION_NOTIFY_ABANDONED_OPERATIONS_246=Gibt an, ob der Directory-Server einem Client auf abgebrochene Vorg\u00e4nge eine Reaktion senden soll, damit dieser wei\u00df, dass der Server sie nicht mehr bearbeitet. Die LDAP-Spezifikation verbietet das Senden von Reaktionen in solchen F\u00e4llen, aber einige Clients funktionieren nicht ordnungsgem\u00e4\u00df, wenn sie vergeblich auf eine Reaktion auf abgebrochene Vorg\u00e4nge warten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_NOTIFY_ABANDONED_OPERATIONS_247=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-notify-abandoned-operations (it should be a Boolean value of true or \
|
### false): %s
|
###SEVERE_ERR_CONFIG_EXTOP_INVALID_CLASS_256=Class %s specified in configuration \
|
### entry %s does not contain a valid extended operation handler implementation: \
|
### %s
|
MILD_ERR_CONFIG_EXTOP_INITIALIZATION_FAILED_261=Fehler beim Versuch, eine Instanz der Klasse %s als erweiterte Vorgangsbehandlungsroutine zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
###FATAL_ERR_CONFIG_SASL_CANNOT_GET_BASE_264=An error occurred while attempting \
|
### to retrieve the SASL mechanism handler base entry cn=SASL \
|
### Mechanisms,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_SASL_BASE_DOES_NOT_EXIST_265=The SASL mechanism \
|
### configuration base cn=SASL Mechanisms,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_SASL_ENTRY_UNACCEPTABLE_266=Configuration entry %s does not \
|
### contain a valid SASL mechanism handler configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_SASL_CANNOT_CREATE_HANDLER_267=An error occurred while \
|
### attempting to create a Directory Server SASL mechanism handler from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_SASL_INVALID_OBJECTCLASS_268=Configuration entry %s does \
|
### not contain the ds-cfg-sasl-mechanism-handler objectclass, which is required \
|
### for SASL mechanism handler definitions
|
INFO_CONFIG_SASL_DESCRIPTION_CLASS_NAME_269=Vollqualifizierter Name der Java-Klasse, die die SASL-Mechanismus-Behandlungsroutine f\u00fcr den Directory-Server definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend die zugeordnete Behandlungsroutine aktiv ist, muss die Behandlungsroutine deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_SASL_NO_CLASS_NAME_270=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated SASL mechanism handler
|
###SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_NAME_271=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_SASL_INVALID_CLASS_272=Class %s specified in configuration \
|
### entry %s does not contain a valid SASL mechanism handler implementation: %s
|
INFO_CONFIG_SASL_DESCRIPTION_ENABLED_273=Gibt an, ob diese SASL-Mechanismus-Behandlungsroutine f\u00fcr den Directory-Server aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_SASL_NO_ENABLED_ATTR_274=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the SASL \
|
### mechanism handler should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_SASL_INVALID_ENABLED_VALUE_275=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_SASL_CLASS_ACTION_REQUIRED_276=Die angeforderte \u00c4nderung des Klassennamens der SASL-Mechanismus-Behandlungsroutine von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn die Behandlungsroutine deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_SASL_INITIALIZATION_FAILED_277=Fehler beim Versuch, eine Instanz der Klasse %s als SASL-Mechanismus-Behandlungsroutine zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_SASL_EXISTS_278=Neuer Eintrag f\u00fcr SASL-Mechanismus-Behandlungsroutine mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits eine andere Behandlungsroutine mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_SASL_UNACCEPTABLE_CONFIG_279=The configuration for the SASL \
|
### mechanism handler defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
MILD_ERR_CONFIG_FILE_ADD_ALREADY_EXISTS_280=Eintrag %s kann nicht zur Directory-Server-Konfiguration hinzugef\u00fcgt werden, da bereits ein anderer Konfigurationseintrag mit dem DN vorhanden ist
|
MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_DN_281=Eintrag %s kann nicht zur Directory-Server-Konfiguration hinzugef\u00fcgt werden, da der DN keinen \u00fcbergeordneten Eintrag hat
|
MILD_ERR_CONFIG_FILE_ADD_NO_PARENT_282=Eintrag %s kann nicht zur Directory-Server-Konfiguration hinzugef\u00fcgt werden, da der \u00fcbergeordnete Eintrag %s nicht vorhanden ist
|
MILD_ERR_CONFIG_FILE_ADD_REJECTED_BY_LISTENER_283=Konfigurationseintrag %s kann nicht zum Directory-Server hinzugef\u00fcgt werden, da einer der beim \u00fcbergeordneten Eintrag %s registrierten Hinzuf\u00fcge-Listener diese \u00c4nderung mit folgender Nachricht zur\u00fcckgewiesen hat: %s
|
MILD_ERR_CONFIG_FILE_ADD_FAILED_284=Unerwarteter Fehler beim Versuch, Konfigurationseintrag %s als untergeordneten Eintrag von %s hinzuzuf\u00fcgen: %s
|
MILD_ERR_CONFIG_FILE_DELETE_NO_SUCH_ENTRY_285=Eintrag %s kann nicht aus der Directory-Server-Konfiguration entfernt werden, da der angegebene Eintrag nicht vorhanden ist
|
MILD_ERR_CONFIG_FILE_DELETE_HAS_CHILDREN_286=Eintrag %s kann nicht aus der Directory-Server-Konfiguration entfernt werden, da der angegebene Eintrag ein oder mehrere untergeordnete Eintr\u00e4ge hat
|
MILD_ERR_CONFIG_FILE_DELETE_NO_PARENT_287=Eintrag %s kann nicht aus der Directory-Server-Konfiguration entfernt werden, da der Eintrag keinen \u00fcbergeordneten Eintrag hat und das Entfernen des Konfigurations-Root-Eintrags nicht zul\u00e4ssig ist
|
MILD_ERR_CONFIG_FILE_DELETE_REJECTED_288=Eintrag %s kann nicht aus der Directory-Server-Konfiguration entfernt werden, da einer der beim \u00fcbergeordneten Eintrag %s registrierten L\u00f6sch-Listener diese \u00c4nderung mit folgender Nachricht zur\u00fcckgewiesen hat: %s
|
MILD_ERR_CONFIG_FILE_DELETE_FAILED_289=Unerwarteter Fehler beim Versuch, Konfigurationseintrag %s als untergeordneten Eintrag von %s zu entfernen: %s
|
MILD_ERR_CONFIG_FILE_MODIFY_NO_SUCH_ENTRY_290=Eintrag %s kann nicht ge\u00e4ndert werden, da der angegebene Eintrag nicht vorhanden ist
|
MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_CHANGE_LISTENER_291=Eintrag %s kann nicht ge\u00e4ndert werden, da einer der bei diesem Eintrag registrierten Konfigurations\u00e4nderungs-Listener die \u00c4nderung zur\u00fcckgewiesen hat: %s
|
MILD_ERR_CONFIG_FILE_MODIFY_REJECTED_BY_COMPONENT_292=Eintrag %s kann nicht ge\u00e4ndert werden, da eine der bei diesem Eintrag registrierten konfigurierbaren Komponenten die \u00c4nderung zur\u00fcckgewiesen hat: %s
|
MILD_ERR_CONFIG_FILE_SEARCH_NO_SUCH_BASE_293=Der Suchvorgang kann nicht ausgef\u00fchrt werden, da der Basiseintrag %s nicht vorhanden ist
|
MILD_ERR_CONFIG_FILE_SEARCH_INVALID_SCOPE_294=Der Suchvorgang kann nicht ausgef\u00fchrt werden, da der angegebenen Suchbereich %s ung\u00fcltig ist
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_CREATE_TEMP_ARCHIVE_295=Aufgrund einer Konfigurations\u00e4nderung ist ein Fehler beim Versuch aufgetreten, die tempor\u00e4re Datei %s zu erstellen, in der die archivierten Versionen der vorherigen Directory-Server-Konfigurationen gespeichert werden: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_EXISTING_ARCHIVE_296=Fehler beim Versuch, die archivierte Konfiguration von %s in die tempor\u00e4re Datei %s zu kopieren: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_COPY_CURRENT_CONFIG_297=Fehler beim Versuch, die archivierten Konfigurationen in Datei %s zu aktualisieren, um die aktuelle Konfiguration aus Datei %s hinzuzuf\u00fcgen: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_TEMP_ARCHIVE_298=Fehler beim Versuch, die archivierten Konfigurationsdaten von %s nach %s umzubenennen. Die Ursache f\u00fcr den Fehler konnte nicht ermittelt werden
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_REPLACE_ARCHIVE_299=Das aktualisierte Archiv mit den fr\u00fcheren Directory-Server-Konfigurationen kann nicht von %s nach %s umbenannt werden: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_EXPORT_NEW_CONFIG_300=Fehler beim Versuch, die neue Directory-Server-Konfiguration nach Datei %s zu exportieren: %s
|
MILD_ERR_CONFIG_FILE_WRITE_CANNOT_RENAME_NEW_CONFIG_301=Fehler beim Versuch, die neue Directory-Server-Konfigurationsdatei von %s nach %s umzubenennen: %s
|
MILD_ERR_CONFIG_FILE_MODDN_NOT_ALLOWED_302=DN-\u00c4nderungsvorg\u00e4nge sind in der Directory-Server-Konfiguration nicht erlaubt
|
INFO_CONFIG_LOGGER_SUPPRESS_INTERNAL_OPERATIONS_303=Gibt an, ob Nachrichten f\u00fcr interne Vorg\u00e4nge vom Zugriffsprotokoll ausgenommen bleiben
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_SUPPRESS_INT_OPERATION_VALUE_304=Invalid \
|
### value specified for attribute %s. Allowed values are true or false
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BASE_DNS_305=Satz von Basis-DNs, die f\u00fcr dieses Backend verwendet werden. Es h\u00e4ngt von der Backendimplementierung ab, ob \u00c4nderungen an diesem Attribut sofort in Kraft treten
|
###SEVERE_ERR_CONFIG_BACKEND_NO_BASE_DNS_306=Backend configuration entry %s does \
|
### not contain attribute ds-cfg-base-dn, which is used to specify the \
|
### set of base DNs for the backend. This is a required attribute, and therefore \
|
### the backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BASE_DNS_307=An unexpected \
|
### error occurred while attempting to determine the set of base DNs associated \
|
### with the backend defined in configuration entry %s: %s. This backend will \
|
### be disabled
|
INFO_CONFIG_KEYMANAGER_DESCRIPTION_ENABLED_313=Gibt an, ob der Schl\u00fcssel-Manager-Anbieter f\u00fcr den Directory-Server aktiviert werden soll. Ein Schl\u00fcssel-Manager-Anbieter ist f\u00fcr Vorg\u00e4nge erforderlich, die Zugriff auf einen Schl\u00fcssel-Manager erfordern (z.\u00a0B. bei Kommunikation \u00fcber SSL). \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft, wirken sich aber nur auf zuk\u00fcnftige Versuche aus, auf den Schl\u00fcssel-Manager zuzugreifen
|
###SEVERE_ERR_CONFIG_KEYMANAGER_NO_ENABLED_ATTR_314=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the key manager provider is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_KEYMANAGER_DESCRIPTION_CLASS_317=Fully-qualified name of the \
|
### Java class that includes the key manager provider \
|
### implementation. Changes to this configuration attribute will not take effect \
|
### until the key manager provider has been disabled and then re-enabled, or \
|
### until the server is restarted
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_ENABLED_328=Indicates whether the \
|
### Directory Server trust manager provider should be enabled. A trust manager \
|
### provider is required for operations that require access to a trust manager \
|
### (e.g., communication over SSL). Changes to this configuration attribute will \
|
### take effect immediately, but will only impact future attempts to access the \
|
### trust manager
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_ENABLED_ATTR_329=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the trust manager provider is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_DESCRIPTION_CLASS_332=Fully-qualified name of the \
|
### Java class that includes the trust manager \
|
### provider implementation. Changes to this configuration attribute will not \
|
### take effect until the trust manager provider has been disabled and then \
|
### re-enabled, or until the server is restarted
|
###SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_ENABLED_347=Indicates whether the \
|
### Directory Server certificate mapper should be enabled. A certificate mapper \
|
### is used to establish a mapping between a client certificate chain and a user \
|
### entry in the Directory Server for SASL EXTERNAL authentication and similar \
|
### purposes. Changes to this configuration attribute will take effect \
|
### immediately
|
###SEVERE_ERR_CONFIG_CERTMAPPER_NO_ENABLED_ATTR_348=Configuration entry "%s" \
|
### does not contain a value for attribute ds-cfg-enabled, \
|
### which indicates whether the certificate mapper is enabled for use in the \
|
### server
|
###SEVERE_ERR_CONFIG_CERTMAPPER_DESCRIPTION_CLASS_351=Fully-qualified name of the \
|
### Java class that includes the certificate mapper \
|
### implementation. Changes to this configuration attribute will not take effect \
|
### until the certificate mapper has been disabled and then re-enabled, or until \
|
### the server is restarted
|
MILD_WARN_CONFIG_LOGGER_NO_RETENTION_POLICY_357=Im Eintrag %s wurde keine Dateiaufbewahrungsrichtlinie definiert. Es werden keine Protokolldateien gel\u00f6scht
|
###SEVERE_WARN_CONFIG_LOGGER_INVALID_RETENTION_POLICY_358=An invalid file \
|
### retention policy %s has been defined in configuration entry %s
|
###SEVERE_WARN_CONFIG_LOGGER_NO_NUMBER_OF_FILES_359=No file number limit has \
|
### been defined for the retention policy in the configuration entry %s
|
###SEVERE_WARN_CONFIG_LOGGER_NO_DISK_SPACE_USED_360=No disk space limit has been \
|
### defined for the retention policy in the configuration entry %s
|
###FATAL_ERR_CONFIG_PWSCHEME_CANNOT_GET_BASE_363=An error occurred while \
|
### attempting to retrieve the password storage scheme base entry cn=Password \
|
### Storage Schemes,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWSCHEME_BASE_DOES_NOT_EXIST_364=The password storage \
|
### scheme configuration base cn=Password Storage Schemes,cn=config does not \
|
### exist in the Directory Server configuration. This entry must be present for \
|
### the server to function properly
|
###SEVERE_ERR_CONFIG_PWSCHEME_ENTRY_UNACCEPTABLE_365=Configuration entry %s does \
|
### not contain a valid password storage scheme configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWSCHEME_CANNOT_CREATE_SCHEME_366=An error occurred while \
|
### attempting to create a Directory Server password storage scheme from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_OBJECTCLASS_367=Configuration entry %s \
|
### does not contain the ds-cfg-password-storage-scheme objectclass, which is \
|
### required for password storage scheme definitions
|
INFO_CONFIG_PWSCHEME_DESCRIPTION_CLASS_NAME_368=Vollqualifizierter Name der Java-Klasse, die das Directory-Server-Passwortspeicherschema definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend das zugeordnete Schema aktiv ist, muss das Speicherschema deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_PWSCHEME_NO_CLASS_NAME_369=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified \
|
### class name for the associated password storage scheme
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_NAME_370=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_CLASS_371=Class %s specified in \
|
### configuration entry %s does not contain a valid password storage scheme \
|
### implementation: %s
|
INFO_CONFIG_PWSCHEME_DESCRIPTION_ENABLED_372=Gibt an, ob dieses Directory-Server-Passwortspeicherschema aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_PWSCHEME_NO_ENABLED_ATTR_373=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### storage scheme should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWSCHEME_INVALID_ENABLED_VALUE_374=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: \
|
### %s
|
INFO_CONFIG_PWSCHEME_CLASS_ACTION_REQUIRED_375=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr das Passwortspeicherschema von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn das Speicherschema deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_PWSCHEME_INITIALIZATION_FAILED_376=Fehler beim Versuch, eine Instanz der Klasse %s als Passwortspeicherschema zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_PWSCHEME_EXISTS_377=Neuer Eintrag f\u00fcr Passwortspeicherschema mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderes Speicherschema mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_PWSCHEME_UNACCEPTABLE_CONFIG_378=The configuration for the \
|
### password storage scheme defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_PLUGIN_CLASS_ACTION_REQUIRED_379=Die angeforderte \u00c4nderung des Plugin-Klassennamens von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn das Plugin deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
###SEVERE_ERR_CONFIG_LOGGER_NO_FREE_DISK_SPACE_380=No disk space limit has been \
|
### defined for the retention policy in the configuration entry %s
|
###SEVERE_ERR_CONFIG_LOGGER_INVALID_JAVA5_POLICY_381=The free disk space based \
|
### retention policy in the configuration entry %s. is not allowed for the \
|
### Directory Server when running on pre Java 6 VMs
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_BACKEND_ID_382=Eindeutige Kennung f\u00fcr dieses Backend. \u00c4nderungen an diesem Konfigurationsattribut treten erst in Kraft, wenn das Backend deaktiviert und wieder reaktiviert oder der Server neu gestartet wird
|
###SEVERE_WARN_CONFIG_BACKEND_NO_BACKEND_ID_383=Backend configuration entry %s \
|
### does not contain attribute ds-cfg-backend-id, which is used to provide a \
|
### unique identifier for the backend. The backend will be disabled
|
###SEVERE_WARN_CONFIG_BACKEND_DUPLICATE_BACKEND_ID_384=The backend defined in \
|
### configuration entry %s has a backend ID of %s that conflicts with the backend \
|
### ID for another backend in the server. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_BACKEND_ID_385=An unexpected \
|
### error occurred while attempting to determine the backend ID for the backend \
|
### defined in configuration entry %s: %s. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_MAC_386=An error occurred while \
|
### attempting to obtain the %s MAC provider to create the signed hash for the \
|
### backup: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_DIGEST_387=An error occurred while \
|
### attempting to obtain the %s message digest to create the hash for the backup: \
|
### %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_388=An error occurred \
|
### while trying to create the config archive file %s in directory %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_GET_CIPHER_389=An error occurred while \
|
### attempting to obtain the cipher to use to encrypt the backup: %s
|
###SEVERE_ERR_CONFIG_BACKUP_ZIP_COMMENT_390=%s config backup %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_DETERMINE_CONFIG_FILE_LOCATION_391=An error \
|
### occurred while attempting to determine the path to the Directory Server \
|
### configuration file so that it could be archived: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_BACKUP_CONFIG_FILE_392=An error occurred \
|
### while attempting to back up configuration file %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_BACKUP_ARCHIVED_CONFIGS_393=An error occurred \
|
### while attempting to back up the archived previous configurations from file \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_CLOSE_ZIP_STREAM_394=An error occurred while \
|
### trying to close the config archive file %s in directory %s: %s
|
###SEVERE_ERR_CONFIG_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_395=An error \
|
### occurred while attempting to update the backup descriptor file %s with \
|
### information about the configuration backup: %s
|
###SEVERE_ERR_CONFIG_RESTORE_NO_SUCH_BACKUP_396=Unable to restore or verify \
|
### configuration backup %s in directory %s because no such backup exists
|
###SEVERE_ERR_CONFIG_RESTORE_NO_BACKUP_FILE_397=Unable to restore or verify \
|
### configuration backup %s in directory %s because the archive filename could \
|
### not be determined
|
###SEVERE_ERR_CONFIG_RESTORE_NO_SUCH_FILE_398=Unable to restore or verify \
|
### configuration backup %s because the specified archive file %s does not exist
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CHECK_FOR_ARCHIVE_399=Unable to restore or \
|
### verify configuration backup %s because an error occurred while trying to \
|
### determine whether backup archive %s exists: %s
|
###SEVERE_ERR_CONFIG_RESTORE_UNKNOWN_DIGEST_400=Unable to restore or verify \
|
### configuration backup %s because an unsigned hash of this backup is available \
|
### but the server cannot determine the digest algorithm used to generate this \
|
### hash
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_DIGEST_401=Unable to restore or verify \
|
### configuration backup %s because it has an unsigned hash that uses an unknown \
|
### or unsupported digest algorithm of %s
|
###SEVERE_ERR_CONFIG_RESTORE_UNKNOWN_MAC_402=Unable to restore or verify \
|
### configuration backup %s because a signed hash of this backup is available but \
|
### the server cannot determine the MAC algorithm used to generate this hash
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_MAC_403=Unable to restore or verify \
|
### configuration backup %s because it has a signed hash that uses an unknown or \
|
### unsupported MAC algorithm of %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_OPEN_BACKUP_FILE_404=Unable to restore or \
|
### verify configuration backup %s because an error occurred while attempting to \
|
### open the backup archive file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_CIPHER_406=Unable to restore or verify \
|
### configuration backup %s because it is encrypted using an unknown or \
|
### unsupported cipher: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_BACKUP_EXISTING_CONFIG_407=Unable to restore \
|
### configuration backup %s because an error occurred while attempting to \
|
### temporarily back up the current configuration files from %s to %s: %s
|
NOTICE_CONFIG_RESTORE_RESTORED_OLD_CONFIG_408=Ein Fehler verhindert, dass die Konfigurationssicherung ordnungsgem\u00e4\u00df wiederhergestellt wird. Die originalen, vor dem Start des Wiederherstellungsprozesses g\u00fcltigen Konfigurationsdateien sind jedoch noch erhalten und befinden sich an ihrem Originalspeicherort unter %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_RESTORE_OLD_CONFIG_409=An error occurred \
|
### that prevented the configuration backup from being properly restored. The \
|
### original configuration files that were in place before the start of the \
|
### restore process have been preserved and are contained in the %s directory
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CREATE_CONFIG_DIRECTORY_410=Unable to \
|
### restore configuration backup %s because an error occurred while attempting to \
|
### create a new empty directory %s into which the files should be restored: %s
|
###SEVERE_ERR_CONFIG_RESTORE_OLD_CONFIG_SAVED_411=An error occurred that \
|
### prevented the configuration backup from being properly restored. The \
|
### original configuration files that were in place before the start of the \
|
### restore process have been preserved in the %s directory
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_GET_ZIP_ENTRY_412=Unable to restore or \
|
### verify configuration backup %s because an error occurred while trying to read \
|
### the next entry from the archive file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_CREATE_FILE_413=Unable to restore \
|
### configuration backup %s because an error occurred while trying to recreate \
|
### file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_CANNOT_PROCESS_ARCHIVE_FILE_414=Unable to restore \
|
### or verify configuration backup %s because an error occurred while processing \
|
### archived file %s: %s
|
###SEVERE_ERR_CONFIG_RESTORE_ERROR_ON_ZIP_STREAM_CLOSE_415=Unable to restore or \
|
### verify configuration backup %s because an unexpected error occurred while \
|
### trying to close the archive file %s: %s
|
NOTICE_CONFIG_RESTORE_UNSIGNED_HASH_VALID_416=Der vom Sicherungsarchiv berechnete Message Digest stimmt mit dem in den Sicherungsinformationen gespeichertem Digest \u00fcberein.
|
###SEVERE_ERR_CONFIG_RESTORE_UNSIGNED_HASH_INVALID_417=Unable to restore or \
|
### verify configuration backup %s because the message digest calculated from the \
|
### backup archive does not match the digest stored with the backup information
|
NOTICE_CONFIG_RESTORE_SIGNED_HASH_VALID_418=Der vom Sicherungsarchiv berechnete signierte Digest stimmt mit der in den Sicherungsinformationen gespeicherten Signatur \u00fcberein
|
###SEVERE_ERR_CONFIG_RESTORE_SIGNED_HASH_INVALID_419=Unable to restore or verify \
|
### configuration backup %s because the signed digest calculated from the backup \
|
### archive does not match the signature stored with the backup information
|
NOTICE_CONFIG_RESTORE_VERIFY_SUCCESSFUL_420=Alle mit der Konfigurationssicherung %s aus dem Verzeichnis %s durchgef\u00fchrten Pr\u00fcfungen ergeben, dass es sich anscheinend um ein g\u00fcltiges Archiv handelt
|
NOTICE_CONFIG_RESTORE_SUCCESSFUL_421=Konfigurationssicherung %s wurde erfolgreich vom Archiv im Verzeichnis %s wiederhergestellt
|
###SEVERE_ERR_CONFIG_BACKEND_CANNOT_ACQUIRE_SHARED_LOCK_422=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
|
###SEVERE_WARN_CONFIG_BACKEND_CANNOT_RELEASE_SHARED_LOCK_423=An error occurred \
|
### while attempting to release a shared lock for backend %s: %s. This may \
|
### interfere with operations that require exclusive access, including LDIF \
|
### import and restoring a backup
|
INFO_CONFIG_FILE_HEADER_424=Diese Datei enth\u00e4lt die prim\u00e4re Directory-Server-Konfiguration. Sie darf nicht direkt bearbeitet werden, w\u00e4hrend der Server online ist. Verwalten Sie die Serverkonfiguration nur mit den Administrationstools, die mit dem Directory-Server geliefert wurden
|
INFO_CONFIG_CORE_DESCRIPTION_ADD_MISSING_RDN_ATTRS_425=Gibt an, ob der Directory-Server automatisch fehlende RDN-Attribute zu einem Eintrag hinzuf\u00fcgen soll, wenn der Eintrag hinzugef\u00fcgt wird. Standardm\u00e4\u00dfig werden Eintr\u00e4ge, die keine RDN-Attributwerte in ihrer Attributsliste haben, zur\u00fcckgewiesen, da sie nicht der LDAP-Spezifikation entsprechen. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_ADD_MISSING_RDN_ATTRS_426=Configuration entry \
|
### %s has an invalid value for configuration attribute \
|
### ds-cfg-add-missing-rdn-attributes (it should be a Boolean value of true or \
|
### false): %s
|
INFO_CONFIG_CORE_DESCRIPTION_SERVER_ERROR_RESULT_CODE_427=Ergebniscode, der f\u00fcr Reaktionen verwendet wird, bei denen Vorg\u00e4nge aufgrund eines internen Serverfehlers fehlschlagen. Geben Sie als Wert die entsprechende Ganzzahl zum dazugeh\u00f6rigen LDAP-Ergebniscode an. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SERVER_ERROR_RESULT_CODE_428=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-server-error-result-code (it should be an integer value greater than \
|
### or equal to 1): %s
|
###FATAL_ERR_CONFIG_IDMAPPER_CANNOT_GET_BASE_429=An error occurred while \
|
### attempting to retrieve the identity mapper base entry cn=Identity \
|
### Mappers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_IDMAPPER_BASE_DOES_NOT_EXIST_430=The identity mapper \
|
### configuration base cn=Identity Mappers,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_IDMAPPER_ENTRY_UNACCEPTABLE_431=Configuration entry %s does \
|
### not contain a valid identity mapper configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_IDMAPPER_CANNOT_CREATE_MAPPER_432=An error occurred while \
|
### attempting to create a Directory Server identity mapper from the information \
|
### in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_OBJECTCLASS_433=Configuration entry %s \
|
### does not contain the ds-cfg-identity-mapper objectclass, which is required \
|
### for identity mapper definitions
|
INFO_CONFIG_IDMAPPER_DESCRIPTION_CLASS_NAME_434=Vollqualifizierter Name der Java-Klasse, die einen Identit\u00e4ts-Mapper f\u00fcr den Directory-Server definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend der zugeordnete Identit\u00e4ts-Mapper aktiv ist, muss der Mapper deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_CLASS_NAME_435=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class name \
|
### for the associated identity mapper
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_NAME_436=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_CLASS_437=Class %s specified in \
|
### configuration entry %s does not contain a valid identity mapper \
|
### implementation: %s
|
INFO_CONFIG_IDMAPPER_DESCRIPTION_ENABLED_438=Gibt an, ob der Identit\u00e4ts-Mapper f\u00fcr den Directory-Server aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_ENABLED_ATTR_439=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the identity mapper \
|
### should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_ENABLED_VALUE_440=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_IDMAPPER_CLASS_ACTION_REQUIRED_441=Die angeforderte \u00c4nderung des Klassennamen f\u00fcr den Identit\u00e4ts-Mapper von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der Identit\u00e4ts-Mapper deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_IDMAPPER_INITIALIZATION_FAILED_442=Fehler beim Versuch, eine Instanz der Klasse %s als Identit\u00e4ts-Mapper zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_IDMAPPER_EXISTS_443=Neuer Identit\u00e4ts-Mapper-Eintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer Identit\u00e4ts-Mapper mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_IDMAPPER_UNACCEPTABLE_CONFIG_444=The configuration for the \
|
### identity mapper defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_PROXY_MAPPER_DN_445=DN des Konfigurationseintrags f\u00fcr den Identit\u00e4ts-Mapper, den der Directory-Server zusammen mit der von einem Proxy verarbeiteten Authorisierungs-V2-Steuerung verwenden soll. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_PROXY_MAPPER_DN_446=Configuration entry %s has \
|
### an invalid value for configuration attribute \
|
### ds-cfg-proxied-authorization-identity-mapper (it should be the DN of a \
|
### valid identity mapper configuration entry): %s
|
###SEVERE_ERR_CONFIG_CORE_NO_PROXY_MAPPER_FOR_DN_447=The proxied authorization \
|
### identity mapper DN %s specified in configuration entry %s does not refer to a \
|
### valid identity mapper configuration entry
|
###SEVERE_ERR_CONFIG_IDMAPPER_NO_PROXY_MAPPER_DN_448=The Directory Server does \
|
### not have any identity mapper configured for use in conjunction with proxied \
|
### authorization V2 operations. The Directory Server will not be able to \
|
### process requests containing the proxied authorization control with a \
|
### username-based authorization ID
|
###SEVERE_ERR_CONFIG_IDMAPPER_INVALID_PROXY_MAPPER_DN_449=The configured proxied \
|
### authorization identity mapper DN %s does not refer to an active identity \
|
### mapper. The Directory Server will not be able to process requests containing \
|
### the proxied authorization control with a username-based authorization ID
|
INFO_CONFIG_CORE_DESCRIPTION_SIZE_LIMIT_450=Standardm\u00e4\u00dfige Maximalzahl an Eintr\u00e4gen, die einem Client bei Suchvorg\u00e4ngen ausgegeben werden. Sie kann f\u00fcr einzelnen Benutzer \u00fcbergangen werden, indem das Betriebsattribut ds-rlim-size-limit in den Benutzereintrag eingef\u00fcgt wird. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SIZE_LIMIT_451=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-size-limit (It should be a \
|
### positive integer value specifying the size limit to use, or a value of 0 or \
|
### -1 to indicate that no limit should be enforced): %s
|
###FATAL_ERR_CONFIG_SYNCH_CANNOT_GET_CONFIG_BASE_452=An error occurred while \
|
### attempting to retrieve the Directory Server synchronization provider \
|
### configuration base entry cn=Synchronization Providers,cn=config: %s
|
###FATAL_ERR_CONFIG_SYNCH_BASE_DOES_NOT_EXIST_453=The Directory Server \
|
### synchronization provider base entry cn=Synchronization Providers,cn=config \
|
### does not exist. This entry must be present in the Directory Server \
|
### configuration
|
###FATAL_ERR_CONFIG_SYNCH_ENTRY_DOES_NOT_HAVE_PROVIDER_CONFIG_454=Configuration \
|
### entry %s exists below the Directory Server synchronization provider root but \
|
### does not contain attribute ds-cfg-synchronization-provider which must be \
|
### present in all synchronization provider configuration entries
|
###FATAL_ERR_CONFIG_SYNCH_CANNOT_CHECK_FOR_PROVIDER_CONFIG_OC_455=An error \
|
### occurred while attempting to determine whether configuration entry %s was a \
|
### valid Directory Server synchronization provider: %s
|
INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_ENABLED_456=Gibt an, ob der zugeordnete Directory-Server-Synchronisationsanbieter aktiviert ist und vom Server verwendet werden soll. Diese Attribut muss in allen Synchronisationsanbietereintr\u00e4gen vorhanden sein und darf nicht ge\u00e4ndert werden, w\u00e4hrend der Directory-Server ausgef\u00fchrt wird
|
###FATAL_ERR_CONFIG_SYNCH_PROVIDER_NO_ENABLED_ATTR_457=Synchronization provider \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-enabled which indicates whether the \
|
### synchronization provider is enabled for use
|
###SEVERE_WARN_CONFIG_SYNCH_PROVIDER_DISABLED_458=The Directory Server \
|
### synchronization provider defined in configuration entry %s is disabled. This \
|
### provider will not be used
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_ENABLED_STATE_459=An error \
|
### occurred while attempting to determine whether the Directory Server \
|
### synchronization provider defined in configuration entry %s should be enabled: \
|
### %s
|
INFO_CONFIG_SYNCH_DESCRIPTION_PROVIDER_CLASS_460=Vollqualifizierter Name der Java-Klasse, die die Logik f\u00fcr den Directory-Server-Synchronisationsanbieter bereitstellt. Diese Attribut muss in allen Synchronisationsanbietereintr\u00e4gen vorhanden sein und darf nicht ge\u00e4ndert werden, w\u00e4hrend der Directory-Server ausgef\u00fchrt wird
|
###FATAL_ERR_CONFIG_SYNCH_NO_CLASS_ATTR_461=Synchronization provider \
|
### configuration entry %s does not contain attribute \
|
### ds-cfg-java-class which specifies the name of the class \
|
### that implements the synchronization provider logic
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_DETERMINE_CLASS_462=An error occurred while \
|
### attempting to determine the name of the class used to provide the Directory \
|
### Server synchronization provider logic from configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_LOAD_PROVIDER_CLASS_463=An error occurred \
|
### while attempting to load class %s referenced in synchronization provider \
|
### configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_UNABLE_TO_INSTANTIATE_PROVIDER_464=An error occurred \
|
### while attempting to instantiate class %s referenced in synchronization \
|
### provider configuration entry %s: %s
|
###FATAL_ERR_CONFIG_SYNCH_ERROR_INITIALIZING_PROVIDER_465=An error occurred \
|
### while attempting to initialize the Directory Server synchronization provider \
|
### referenced in configuration entry %s: %s
|
INFO_CONFIG_SYNCH_PROVIDER_HAS_BEEN_DISABLED_466=Der in Konfigurationseintrag %s definierte Synchronisationsanbieter ist momentan aktiviert, jedoch wurde die Konfiguration ge\u00e4ndert, sodass er deaktiviert werden sollte. Die Deaktivierung tritt erst in Kraft, wenn der Directory-Server neu gestartet wird
|
###FATAL_ERR_CONFIG_SYNCH_PROVIDER_CLASS_CHANGED_467=The Java class providing \
|
### the logic for the synchronization provider defined in configuration entry %s \
|
### has changed from %s to %s. This will not take effect until the Directory \
|
### Server is restarted
|
INFO_CONFIG_BACKEND_ATTR_DESCRIPTION_WRITABILITY_468=Schreib-Modus f\u00fcr dieses Backend. Der Wert ist "enabled", wenn alle Schreibvorg\u00e4nge erlaubt sind, "disabled", wenn alle Schreibvorg\u00e4nge zur\u00fcckgewiesen werden, oder "internal-only", wenn nur interne Schreibvorg\u00e4nge und Synchronisationsaktualisierungen zul\u00e4ssig sind. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_BACKEND_NO_WRITABILITY_MODE_469=The backend defined in \
|
### configuration entry %s does not have a value for configuration attribute \
|
### ds-cfg-writability-mode which indicates the writability mode for that \
|
### backend. The backend will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_INVALID_WRITABILITY_MODE_470=The backend defined in \
|
### configuration entry %s has an invalid writability mode of %s. The backend \
|
### will be disabled
|
###SEVERE_ERR_CONFIG_BACKEND_UNABLE_TO_DETERMINE_WRITABILITY_471=An unexpected \
|
### error occurred while attempting to determine the writability mode for the \
|
### backend defined in configuration entry %s: %s. The backend will be disabled
|
INFO_CONFIG_CORE_DESCRIPTION_WRITABILITY_MODE_472=Schreib-Modus f\u00fcr den Directory-Server. Zul\u00e4ssige Werte sind "enabled", "disabled" und "internal-only". \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_WRITABILITY_MODE_473=Configuration entry %s \
|
### has an invalid value for configuration attribute ds-cfg-writability-mode (the \
|
### value should be one of "enabled", "disabled", or "internal-only"): %s
|
INFO_CONFIG_CORE_DESCRIPTION_BIND_WITH_DN_REQUIRES_PW_474=Gibt an, ob einfache Verbindungen, die ein DN enthalten, auch ein Passwort enthalten m\u00fcssen. Wenn diese Option deaktiviert ist, werden Verbindungen ohne Passwort als anonyme Verbindungen behandelt, selbst wenn sie einen Verbindungs-DN enthalten. Dies kann bei einigen Anwendungstypen zu Sicherheitsl\u00fccken f\u00fchren. Wenn diese Option aktiviert ist, werden einfache Verbindungsanfragen, die ein DN aber kein Passwort enthalten, zur\u00fcckgewiesen, anstatt standardm\u00e4\u00dfig als anonyme Authentifizierungen behandelt zu werden. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_BIND_WITH_DN_REQUIRES_PW_475=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-bind-with-dn-requires-password (the value should be either "TRUE" or \
|
### "FALSE"): %s
|
###FATAL_ERR_CONFIG_PWVALIDATOR_CANNOT_GET_BASE_476=An error occurred while \
|
### attempting to retrieve the password validator base entry cn=Password \
|
### Validators,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWVALIDATOR_BASE_DOES_NOT_EXIST_477=The password validator \
|
### configuration base cn=Password Validators,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_ENTRY_UNACCEPTABLE_478=Configuration entry %s \
|
### does not contain a valid password validator configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_CANNOT_CREATE_VALIDATOR_479=An error occurred \
|
### while attempting to create a Directory Server password validator from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_OBJECTCLASS_480=Configuration entry %s \
|
### does not contain the ds-cfg-password-validator objectclass, which is required \
|
### for password validator definitions
|
INFO_CONFIG_PWVALIDATOR_DESCRIPTION_CLASS_NAME_481=Vollqualifizierter Name der Java-Klasse, die die Passwort\u00fcberpr\u00fcfung f\u00fcr den Directory-Server definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend die zugeordnete \u00dcberpr\u00fcfung aktiv ist, muss die \u00dcberpr\u00fcfung deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_NO_CLASS_NAME_482=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated password validator
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_NAME_483=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_CLASS_484=Class %s specified in \
|
### configuration entry %s does not contain a valid password validator \
|
### implementation: %s
|
INFO_CONFIG_PWVALIDATOR_DESCRIPTION_ENABLED_485=Gibt an, ob die Passwort\u00fcberpr\u00fcfung f\u00fcr den Directory-Server aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_NO_ENABLED_ATTR_486=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### validator should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_INVALID_ENABLED_VALUE_487=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_PWVALIDATOR_CLASS_ACTION_REQUIRED_488=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr die Passwort\u00fcberpr\u00fcfung von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn die Passwort\u00fcberpr\u00fcfung deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_PWVALIDATOR_INITIALIZATION_FAILED_489=Fehler beim Versuch, eine Instanz der Klasse %s als Passwort\u00fcberpr\u00fcfung zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_PWVALIDATOR_EXISTS_490=Neuer Eintrag f\u00fcr Passwort\u00fcberpr\u00fcfung mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits eine andere \u00dcberpr\u00fcfung mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_PWVALIDATOR_UNACCEPTABLE_CONFIG_491=The configuration for \
|
### the password validator defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_PWGENERATOR_CANNOT_GET_BASE_492=An error occurred while \
|
### attempting to retrieve the password generator base entry cn=Password \
|
### Generators,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_PWGENERATOR_BASE_DOES_NOT_EXIST_493=The password generator \
|
### configuration base cn=Password Generators,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWGENERATOR_ENTRY_UNACCEPTABLE_494=Configuration entry %s \
|
### does not contain a valid password generator configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_PWGENERATOR_CANNOT_CREATE_GENERATOR_495=An error occurred \
|
### while attempting to create a Directory Server password generator from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_OBJECTCLASS_496=Configuration entry %s \
|
### does not contain the ds-cfg-password-generator objectclass, which is required \
|
### for password generator definitions
|
INFO_CONFIG_PWGENERATOR_DESCRIPTION_CLASS_NAME_497=Vollqualifizierter Name der Java-Klasse, die den Directory-Server-Passwortgenerator definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend der zugeordnete Generator aktiv ist, muss der Generator deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_PWGENERATOR_NO_CLASS_NAME_498=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated password generator
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_NAME_499=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_CLASS_500=Class %s specified in \
|
### configuration entry %s does not contain a valid password generator \
|
### implementation: %s
|
INFO_CONFIG_PWGENERATOR_DESCRIPTION_ENABLED_501=Gibt an, ob der Directory-Server-Passwortgenerator aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_PWGENERATOR_NO_ENABLED_ATTR_502=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the password \
|
### generator should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_PWGENERATOR_INVALID_ENABLED_VALUE_503=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_PWGENERATOR_CLASS_ACTION_REQUIRED_504=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr den Passwortgenerator von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der Generator deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_PWGENERATOR_INITIALIZATION_FAILED_505=Fehler beim Versuch, eine Instanz der Klasse %s als Passwortgenerator zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_PWGENERATOR_EXISTS_506=Neuer Passwortgeneratoreintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer Generator mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_PWGENERATOR_UNACCEPTABLE_CONFIG_507=The configuration for \
|
### the password generator defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_DEFAULT_PWPOLICY_DN_508=DN des Konfigurationseintrags, der die Standard-Passwortrichtline f\u00fcr den Directory-Server definiert. Diese gilt f\u00fcr alle Benutzer, f\u00fcr die keine benutzerdefinierte Passwortrichtlinie definiert ist. Dieser Eintrag ist obligatorisch und muss eine Konfiguration f\u00fcr eine g\u00fcltige Passwortrichtlinie enthalten. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_NO_DEFAULT_PWPOLICY_509=No default password policy was \
|
### configured for the Directory Server. This must be specified by the \
|
### ds-cfg-default-password-policy attribute in configuration entry %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_DEFAULT_PWPOLICY_DN_510=Configuration entry %s \
|
### has an invalid value for configuration attribute \
|
### ds-cfg-default-password-policy (the value should a DN specifying the default \
|
### password policy configuration entry): %s
|
###SEVERE_ERR_CONFIG_CORE_NO_SUCH_PWPOLICY_511=The value %s for configuration \
|
### attribute ds-cfg-default-password-policy does not refer to a valid password \
|
### policy configuration entry
|
###FATAL_ERR_CONFIG_PWPOLICY_CANNOT_GET_BASE_512=An error occurred while \
|
### attempting to retrieve the password policy base entry cn=Password \
|
### Policies,cn=config from the Directory Server configuration: %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_BASE_DOES_NOT_EXIST_513=The password policy \
|
### configuration base cn=Password Policies,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_PWPOLICY_NO_POLICIES_514=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
|
###SEVERE_ERR_CONFIG_PWPOLICY_INVALID_POLICY_CONFIG_515=The password policy \
|
### defined in configuration entry %s is invalid: %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_MISSING_DEFAULT_POLICY_516=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
|
###SEVERE_WARN_CONFIG_PWPOLICY_CANNOT_DELETE_DEFAULT_POLICY_517=The specified \
|
### entry %s is currently defined as the configuration entry for the default \
|
### password policy. The default password policy configuration entry may not be \
|
### removed
|
INFO_CONFIG_PWPOLICY_REMOVED_POLICY_518=Passwortrichtlinieneintrag %s wurde aus der Directory-Server-Konfiguration entfernt. Alle Benutzereintr\u00e4ge, die explizit auf diese Passwortrichtlinie verweisen, k\u00f6nnen nicht mehr authentifiziert werden
|
###FATAL_ERR_CONFIG_AUTHZ_CANNOT_GET_ENTRY_519=An error occurred while \
|
### attempting to retrieve the Directory Server access control configuration \
|
### entry cn=Access Control Handler,cn=config: %s
|
###FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_EXIST_520=The Directory Server access \
|
### control configuration entry cn=Access Control Handler,cn=config does not \
|
### exist. This entry must be present in the Directory Server configuration
|
###FATAL_ERR_CONFIG_AUTHZ_ENTRY_DOES_NOT_HAVE_OBJECT_CLASS_521=The Directory \
|
### Server access control configuration entry cn=Access Control Handler,cn=config \
|
### does not have the correct object class. This entry must have the object \
|
### class ds-cfg-access-control-handler in order to be valid
|
INFO_CONFIG_AUTHZ_DESCRIPTION_ENABLED_523=Gibt an, ob die Zugriffssteuerung aktiviert ist und vom Server verwendet werden soll. Diese Attribut ist obligatorisch
|
###FATAL_ERR_CONFIG_AUTHZ_NO_ENABLED_ATTR_524=The access control configuration \
|
### entry %s does not contain attribute ds-cfg-enabled which \
|
### indicates whether the access control is enabled for use
|
###SEVERE_WARN_CONFIG_AUTHZ_DISABLED_525=Access control has been disabled
|
NOTICE_CONFIG_AUTHZ_ENABLED_526=Die Zugriffssteuerung wurde aktiviert und verwendet die Implementierung %s
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_ENABLED_STATE_527=An error \
|
### occurred while attempting to determine whether the Directory Server access \
|
### control as defined in configuration entry %s should be enabled: %s
|
INFO_CONFIG_AUTHZ_DESCRIPTION_CLASS_528=Vollqualifizierter Name der Java-Klasse, die die Zugriffssteuerungsimplementierung f\u00fcr den Directory-Server bereitstellt. Diese Attribut ist obligatorisch
|
###FATAL_ERR_CONFIG_AUTHZ_NO_CLASS_ATTR_529=The access control configuration \
|
### entry %s does not contain attribute ds-cfg-java-class which specifies \
|
### the name of the Java class providing the access control implementation for \
|
### the Directory Server
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_DETERMINE_CLASS_530=An error occurred while \
|
### attempting to determine the name of the class used to provide the Directory \
|
### Server access control implementation from configuration entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_LOAD_CLASS_531=An error occurred while \
|
### attempting to load class %s referenced in the access control configuration \
|
### entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_BAD_CLASS_532=The access control implementation class \
|
### %s referenced in the access control configuration entry %s does not implement \
|
### the %s interface: %s
|
###FATAL_ERR_CONFIG_AUTHZ_UNABLE_TO_INSTANTIATE_HANDLER_533=An error occurred \
|
### while attempting to instantiate class %s referenced in the access control \
|
### configuration entry %s: %s
|
###FATAL_ERR_CONFIG_AUTHZ_ERROR_INITIALIZING_HANDLER_534=An error occurred while \
|
### attempting to initialize the Directory Server access control implementation \
|
### referenced in configuration entry %s: %s
|
###FATAL_ERR_CONFIG_ROOTDN_CANNOT_GET_BASE_535=An error occurred while \
|
### attempting to retrieve the root DN base entry cn=Root DNs,cn=config from the \
|
### Directory Server configuration: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_BASE_DOES_NOT_EXIST_536=The password policy \
|
### configuration base cn=Root DNs,cn=config does not exist in the Directory \
|
### Server configuration. This entry must be present for the server to function \
|
### properly
|
###SEVERE_ERR_CONFIG_ROOTDN_ENTRY_UNACCEPTABLE_537=Configuration entry %s does \
|
### not contain a valid root DN configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_CREATE_538=An error occurred while attempting \
|
### to create a Directory Server root DN from the information in configuration \
|
### entry %s: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_INVALID_OBJECTCLASS_539=Configuration entry %s does \
|
### not contain the ds-cfg-root-dn-user objectclass, which is required for Directory \
|
### Server root DN definitions
|
INFO_CONFIG_ROOTDN_DESCRIPTION_ALTERNATE_BIND_DN_540=Legt einen oder mehrere alternative Verbindungs-DNs fest, die zus\u00e4tzlich zum tats\u00e4chlichen DN des Root-DN-Konfigurationseintrags als zugeordneter Root-DN zur Authentifizierung verwendet werden k\u00f6nnen. Alternative Verbindungs-DNs d\u00fcrfen sich nicht im Konflikt mit anderen Eintr\u00e4gen in dem Verzeichnis befinden, und sie d\u00fcrfen sich auch nicht im Konflikt mit anderen alternativen Verbindungs-DNs befinden, die f\u00fcr andere Root-DNs konfiguriert sind. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_ROOTDN_CONFLICTING_MAPPING_541=Unable to register "%s" as \
|
### an alternate bind DN for user "%s" because it is already registered as an \
|
### alternate bind DN for root user "%s"
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_PARSE_ALTERNATE_BIND_DNS_542=An error \
|
### occurred while trying to parse the set of alternate bind DNs for root user \
|
### %s: %s
|
###SEVERE_ERR_CONFIG_ROOTDN_CANNOT_REGISTER_ALTERNATE_BIND_DN_543=An error \
|
### occurred while trying to register"%s" as an alternate bind DN for root user \
|
### "%s": %s
|
###SEVERE_ERR_CONFIG_ROOTDN_EXISTS_544=Unable to add root DN entry %s because \
|
### another root user is already registered with that DN
|
###FATAL_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_GET_BASE_545=An error occurred while \
|
### attempting to retrieve the account status notification handler base entry \
|
### cn=Account Status Notification Handlers,cn=config from the Directory Server \
|
### configuration: %s
|
###SEVERE_WARN_CONFIG_ACCTNOTHANDLER_BASE_DOES_NOT_EXIST_546=The account status \
|
### notification handler configuration base cn=Account Status Notification \
|
### Handlers,cn=config does not exist in the Directory Server configuration. \
|
### This entry must be present for the server to function properly
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_ENTRY_UNACCEPTABLE_547=Configuration entry \
|
### %s does not contain a valid account status notification handler \
|
### configuration: %s. It will be ignored
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_CANNOT_CREATE_HANDLER_548=An error occurred \
|
### while attempting to create a Directory Server account status notification \
|
### handler from the information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_OBJECTCLASS_549=Configuration entry \
|
### %s does not contain the ds-cfg-account-status-notification-handler \
|
### objectclass, which is required for account status notification handler \
|
### definitions
|
INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_CLASS_NAME_550=Vollqualifizierter Name der Java-Klasse, die die Kontostatusbenachrichtigungsroutine f\u00fcr den Directory-Server definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend die zugeordnete Benachrichtigungsroutine aktiv ist, muss die Routine deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_CLASS_NAME_551=Configuration entry %s \
|
### does not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the \
|
### fully-qualified class name for the associated account status notification \
|
### handler
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_NAME_552=Configuration entry \
|
### %s has an invalid value for attribute \
|
### ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_CLASS_553=Class %s specified in \
|
### configuration entry %s does not contain a valid account status notification \
|
### handler implementation: %s
|
INFO_CONFIG_ACCTNOTHANDLER_DESCRIPTION_ENABLED_554=Gibt an, ob diese Kontostatusbenachrichtigungsroutine f\u00fcr den Directory-Server aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_NO_ENABLED_ATTR_555=Configuration entry %s \
|
### does not contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether \
|
### the account status notification handler should be enabled for use in the \
|
### Directory Server
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_INVALID_ENABLED_VALUE_556=Configuration \
|
### entry %s has an invalid value for attribute \
|
### ds-cfg-enabled: %s
|
INFO_CONFIG_ACCTNOTHANDLER_CLASS_ACTION_REQUIRED_557=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr die Kontostatusbenachrichtigungsroutine von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn die Benachrichtigungsroutine deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_INITIALIZATION_FAILED_558=Fehler beim Versuch, eine Instanz der Klasse %s als Kontostatusbenachrichtigungsroutine zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_EXISTS_559=Neuer Eintrag f\u00fcr Kontostatusbenachrichtigungsroutine mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits eine andere Benachrichtigungsroutine mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_ACCTNOTHANDLER_UNACCEPTABLE_CONFIG_560=The configuration \
|
### for the account status notification handler defined in configuration entry %s \
|
### was not acceptable according to its internal validation. However, no \
|
### specific information is available regarding the problem(s) with the entry
|
INFO_CONFIG_CORE_DESCRIPTION_LOOKTHROUGH_LIMIT_561=Standardm\u00e4\u00dfige Maximalzahl an Kandidateneintr\u00e4gen, die bei der Ausf\u00fchrung von Suchvorg\u00e4ngen nach Treffern durchsucht werden. Sie kann f\u00fcr einzelne Benutzer \u00fcbergangen werden, indem das Betriebsattribut ds-rlim-lookthrough-limit in den Benutzereintrag eingef\u00fcgt wird. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_LOOKTHROUGH_LIMIT_562=Configuration entry %s \
|
### has an invalid value for configuration attribute ds-cfg-lookthrough-limit (It \
|
### should be a positive integer value specifying the lookthrough limit to use, \
|
### or a value of 0 or -1 to indicate that no limit should be enforced): %s
|
###FATAL_ERR_CONFIG_UNABLE_TO_APPLY_STARTUP_CHANGES_563=An error occurred while \
|
### attempting to apply the changes contained in file %s to the server \
|
### configuration at startup: %s
|
###FATAL_ERR_CONFIG_ERROR_APPLYING_STARTUP_CHANGE_564=Unable to apply a change \
|
### at server startup: %s
|
###FATAL_ERR_CONFIG_UNABLE_TO_APPLY_CHANGES_FILE_565=One or more errors occurred \
|
### while applying changes on server startup
|
INFO_CONFIG_DESCRIPTION_BACKEND_MODE_566=Die Berechtigungen f\u00fcr das Verzeichnis mit den Backend-Datenbankdateien
|
###SEVERE_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.)
|
###SEVERE_ERR_CONFIG_BACKEND_INSANE_MODE_568=Invalid UNIX file permissions %s \
|
### does not allow read and write access to the backend database directory by \
|
### the backend
|
INFO_CONFIG_CORE_DESCRIPTION_TIME_LIMIT_569=Standardm\u00e4\u00dfige Maximaldauer f\u00fcr die Ausf\u00fchrung von Suchvorg\u00e4ngen. Sie kann f\u00fcr einzelne Benutzer \u00fcbergangen werden, indem das Betriebsattribut ds-rlim-time-limit in den Benutzereintrag eingef\u00fcgt wird. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_INVALID_TIME_LIMIT_570=Configuration entry %s has an \
|
### invalid value for configuration attribute ds-cfg-time-limit (it should be an \
|
### integer value followed by a space and a time unit of seconds, minutes, hours, \
|
### days, or weeks): %s
|
###SEVERE_ERR_CONFIG_PWPOLICY_NO_DEFAULT_POLICY_571=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
|
###SEVERE_WARN_CONFIG_BACKEND_CANNOT_REGISTER_BACKEND_572=An error occurred \
|
### while attempting to register backend %s with the Directory Server: %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_NO_REASON_573=An error \
|
### occurred while trying to create the configuration archive directory %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_CREATE_ARCHIVE_DIR_574=An error occurred while \
|
### trying to create the configuration archive directory %s: %s
|
###SEVERE_ERR_CONFIG_FILE_CANNOT_WRITE_CONFIG_ARCHIVE_575=An error occurred \
|
### while trying to write the current configuration to the configuration archive: \
|
### %s
|
INFO_CONFIG_CORE_DESCRIPTION_REJECT_UNAUTHENTICATED_REQUESTS_576=Gibt an, ob der Directory-Server Anfragen von nicht authentifizierten Clients zur\u00fcckweisen soll. Wenn der Wert "true" ist, d\u00fcrfen nicht authentifizierte Clients nur Verbindungs- und StartTLS-Anfragen senden. \u00c4nderungen an diesem Konfigurationsattribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_CORE_REJECT_UNAUTHENTICATED_REQUESTS_INVALID_577=Configuration \
|
### entry %s has an invalid value for configuration attribute \
|
### ds-cfg-reject-unauthenticated-requests(the value should be either true or \
|
### false)
|
###FATAL_ERR_CONFIG_GROUP_CANNOT_GET_BASE_578=An error occurred while attempting \
|
### to retrieve the group implementation base entry cn=Group \
|
### Implementations,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_GROUP_BASE_DOES_NOT_EXIST_579=The group implementation \
|
### configuration base cn=Group Implementations,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_GROUP_ENTRY_UNACCEPTABLE_580=Configuration entry %s does \
|
### not contain a valid group implementation configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_GROUP_CANNOT_CREATE_IMPLEMENTATION_581=An error occurred \
|
### while attempting to create a Directory Server group implementation from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_OBJECTCLASS_582=Configuration entry %s does \
|
### not contain the ds-cfg-group-implementation objectclass, which is required \
|
### for group implementation definitions
|
INFO_CONFIG_GROUP_DESCRIPTION_CLASS_NAME_583=Vollqualifizierter Name der Java-Klasse, die die Directory-Server-Gruppenimplementierung definiert. Wenn der Name ge\u00e4ndert wird, w\u00e4hrend die zugeordnete Implementierung aktiv ist, muss die Gruppenimplementierung deaktiviert und wieder reaktiviert werden, damit die \u00c4nderungen in Kraft treten
|
###SEVERE_ERR_CONFIG_GROUP_NO_CLASS_NAME_584=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated group implementation
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_NAME_585=Configuration entry %s has an \
|
### invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_CLASS_586=Class %s specified in configuration \
|
### entry %s does not contain a valid group implementation: %s
|
INFO_CONFIG_GROUP_DESCRIPTION_ENABLED_587=Gibt an, ob die Directory-Server-Gruppenimplementierung aktiviert werden soll. \u00c4nderungen an diesem Attribut treten sofort in Kraft
|
###SEVERE_ERR_CONFIG_GROUP_NO_ENABLED_ATTR_588=Configuration entry %s does not \
|
### contain a valid value for configuration attribute \
|
### ds-cfg-enabled which indicates whether the group \
|
### implementation should be enabled for use in the Directory Server
|
###SEVERE_ERR_CONFIG_GROUP_INVALID_ENABLED_VALUE_589=Configuration entry %s has \
|
### an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_GROUP_CLASS_ACTION_REQUIRED_590=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr die Gruppenimplementierung von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn die Gruppenimplementierung deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_GROUP_INITIALIZATION_FAILED_591=Fehler beim Versuch, eine Instanz der Klasse %s als Gruppenimplementierung zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_GROUP_EXISTS_592=Neuer Gruppenimplementierungseintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits eine andere Gruppenimplementierung mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_GROUP_UNACCEPTABLE_CONFIG_593=The configuration for the \
|
### group implementation defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_ROOTDN_DESCRIPTION_ROOT_PRIVILEGE_594=Set of \
|
### privileges that should automatically be assigned to root users when they \
|
### authenticate to the server
|
###SEVERE_WARN_CONFIG_ROOTDN_UNRECOGNIZED_PRIVILEGE_595=The set of default root \
|
### privileges contained in configuration attribute %s of entry %s contains an \
|
### unrecognized privilege %s
|
###SEVERE_ERR_CONFIG_ROOTDN_ERROR_DETERMINING_ROOT_PRIVILEGES_596=An error \
|
### occurred while attempting to determine the set of privileges that root users \
|
### should be granted by default: %s
|
INFO_CONFIG_ROOTDN_UPDATED_PRIVILEGES_597=Der Satz an Berechtigungen, die Root-Benutzern automatisch zugewiesen werden, wurde aktualisiert. Dieser neue Berechtigungssatz gilt nicht f\u00fcr bestehende authentifizierte Verbindungen von Root-Benutzern, sondern erst f\u00fcr darauffolgende Root-Benutzer-Authentifizierungen
|
MILD_ERR_CONFIG_FILE_ADD_INSUFFICIENT_PRIVILEGES_598=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um Hinzuf\u00fcgevorg\u00e4nge in der Directory-Server-Konfiguration durchzuf\u00fchren
|
MILD_ERR_CONFIG_FILE_DELETE_INSUFFICIENT_PRIVILEGES_599=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um L\u00f6schvorg\u00e4nge in der Directory-Server-Konfiguration durchzuf\u00fchren
|
MILD_ERR_CONFIG_FILE_MODIFY_INSUFFICIENT_PRIVILEGES_600=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um \u00c4nderungsvorg\u00e4nge in der Directory-Server-Konfiguration durchzuf\u00fchren
|
MILD_ERR_CONFIG_FILE_MODDN_INSUFFICIENT_PRIVILEGES_601=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um DN-\u00c4nderungsvorg\u00e4nge in der Directory-Server-Konfiguration durchzuf\u00fchren
|
MILD_ERR_CONFIG_FILE_SEARCH_INSUFFICIENT_PRIVILEGES_602=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um Suchvorg\u00e4nge in der Directory-Server-Konfiguration durchzuf\u00fchren
|
MILD_ERR_CONFIG_FILE_MODIFY_PRIVS_INSUFFICIENT_PRIVILEGES_603=Sie verf\u00fcgen nicht \u00fcber ausreichende Berechtigungen, um den Satz der Standard-Root-Berechtigungen zu \u00e4ndern
|
###FATAL_ERR_CONFIG_CERTMAPPER_CANNOT_GET_BASE_604=An error occurred while \
|
### attempting to retrieve the certificate mapper base entry cn=Certificate \
|
### Mappers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_CERTMAPPER_BASE_DOES_NOT_EXIST_605=The certificate mapper \
|
### configuration base cn=Certificate Mappers,cn=config does not exist in the \
|
### Directory Server configuration. This entry must be present for the server to \
|
### function properly
|
###SEVERE_ERR_CONFIG_CERTMAPPER_ENTRY_UNACCEPTABLE_606=Configuration entry %s \
|
### does not contain a valid certificate mapper configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_CERTMAPPER_CANNOT_CREATE_MAPPER_607=An error occurred while \
|
### attempting to create a Directory Server certificate mapper from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_OBJECTCLASS_608=Configuration entry %s \
|
### does not contain the ds-cfg-certificate-mapper objectclass, which is required \
|
### for certificate mapper definitions
|
###SEVERE_ERR_CONFIG_CERTMAPPER_NO_CLASS_NAME_609=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated certificate mapper
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_NAME_610=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_CLASS_611=Class %s specified in \
|
### configuration entry %s does not contain a valid certificate mapper \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_CERTMAPPER_INVALID_ENABLED_VALUE_612=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_CERTMAPPER_CLASS_ACTION_REQUIRED_613=Die angeforderte \u00c4nderung des Klassennamen f\u00fcr den Zertifikat-Mapper von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der Zertifikat-Mapper deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_CERTMAPPER_INITIALIZATION_FAILED_614=Fehler beim Versuch, eine Instanz der Klasse %s als Zertifikat-Mapper zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_CERTMAPPER_EXISTS_615=Neuer Zertifikat-Mapper-Eintrag mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer Mapper mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_CERTMAPPER_UNACCEPTABLE_CONFIG_616=The configuration for \
|
### the certificate mapper defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_KEYMANAGER_CANNOT_GET_BASE_617=An error occurred while \
|
### attempting to retrieve the key manager provider base entry cn=Key Manager \
|
### Providers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_KEYMANAGER_BASE_DOES_NOT_EXIST_618=The key manager \
|
### provider configuration base cn=Key Manager Providers,cn=config does not exist \
|
### in the Directory Server configuration. This entry must be present for the \
|
### server to function properly
|
###SEVERE_ERR_CONFIG_KEYMANAGER_ENTRY_UNACCEPTABLE_619=Configuration entry %s \
|
### does not contain a valid key manager provider configuration: %s. It will be \
|
### ignored
|
###SEVERE_ERR_CONFIG_KEYMANAGER_CANNOT_CREATE_PROVIDER_620=An error occurred \
|
### while attempting to create a Directory Server key manager provider from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_OBJECTCLASS_621=Configuration entry %s \
|
### does not contain the ds-cfg-key-manager-provider objectclass, which is \
|
### required for key manager provider definitions
|
###SEVERE_ERR_CONFIG_KEYMANAGER_NO_CLASS_NAME_622=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated key manager provider
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_NAME_623=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_CLASS_624=Class %s specified in \
|
### configuration entry %s does not contain a valid key manager provider \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_KEYMANAGER_INVALID_ENABLED_VALUE_625=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-enabled: %s
|
INFO_CONFIG_KEYMANAGER_CLASS_ACTION_REQUIRED_626=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr den Schl\u00fcssel-Manager-Anbieter von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der Anbieter deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_KEYMANAGER_INITIALIZATION_FAILED_627=Fehler beim Versuch, eine Instanz der Klasse %s als Schl\u00fcssel-Manager-Anbieter zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_KEYMANAGER_EXISTS_628=Neuer Eintrag f\u00fcr Schl\u00fcssel-Manager-Anbieter mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer Anbieter mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_KEYMANAGER_UNACCEPTABLE_CONFIG_629=The configuration for \
|
### the key manager provider defined in configuration entry %s was not acceptable \
|
### according to its internal validation. However, no specific information is \
|
### available regarding the problem(s) with the entry
|
###FATAL_ERR_CONFIG_TRUSTMANAGER_CANNOT_GET_BASE_630=An error occurred while \
|
### attempting to retrieve the trust manager provider base entry cn=Trust Manager \
|
### Providers,cn=config from the Directory Server configuration: %s
|
###SEVERE_WARN_CONFIG_TRUSTMANAGER_BASE_DOES_NOT_EXIST_631=The trust manager \
|
### provider configuration base cn=Trust Manager Providers,cn=config does not \
|
### exist in the Directory Server configuration. This entry must be present for \
|
### the server to function properly
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_ENTRY_UNACCEPTABLE_632=Configuration entry %s \
|
### does not contain a valid trust manager provider configuration: %s. It will \
|
### be ignored
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_CANNOT_CREATE_PROVIDER_633=An error occurred \
|
### while attempting to create a Directory Server trust manager provider from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_OBJECTCLASS_634=Configuration entry %s \
|
### does not contain the ds-cfg-trust-manager-provider objectclass, which is \
|
### required for trust manager provider definitions
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_NO_CLASS_NAME_635=Configuration entry %s does \
|
### not contain a valid value for configuration attribute \
|
### ds-cfg-java-class which specifies the fully-qualified class \
|
### name for the associated trust manager provider
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_NAME_636=Configuration entry %s \
|
### has an invalid value for attribute ds-cfg-java-class: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_CLASS_637=Class %s specified in \
|
### configuration entry %s does not contain a valid trust manager provider \
|
### implementation: %s
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_INVALID_ENABLED_VALUE_638=Configuration entry \
|
### %s has an invalid value for attribute ds-cfg-enabled: \
|
### %s
|
INFO_CONFIG_TRUSTMANAGER_CLASS_ACTION_REQUIRED_639=Die angeforderte \u00c4nderung des Klassennamens f\u00fcr den Trust-Manager-Anbieter von %s nach %s im Konfigurationseintrag %s kann nicht dynamisch ausgef\u00fchrt werden. Diese \u00c4nderung tritt erst in Kraft, wenn der Anbieter deaktiviert und wieder reaktiviert oder der Directory-Server neu gestartet wird
|
MILD_ERR_CONFIG_TRUSTMANAGER_INITIALIZATION_FAILED_640=Fehler beim Versuch, eine Instanz der Klasse %s als Trust-Manager-Anbieter zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
MILD_ERR_CONFIG_TRUSTMANAGER_EXISTS_641=Neuer Eintrag f\u00fcr Trust-Manager-Anbieter mit DN %s kann nicht hinzugef\u00fcgt werden, da bereits ein anderer Anbieter mit dem DN registriert ist
|
###SEVERE_ERR_CONFIG_TRUSTMANAGER_UNACCEPTABLE_CONFIG_642=The configuration for \
|
### the trust manager provider defined in configuration entry %s was not \
|
### acceptable according to its internal validation. However, no specific \
|
### information is available regarding the problem(s) with the entry
|
###SEVERE_ERR_CONFIG_JMX_CANNOT_GET_ATTRIBUTE_643=Unable to retrieve JMX \
|
### attribute %s associated with configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_JMX_SET_ATTR_NO_CONNECTION_644=Unable to set the value of \
|
### JMX attribute %s associated with configuration entry %s because no JMX \
|
### connection is available
|
###SEVERE_ERR_CONFIG_CHANGE_NO_RESULT_645=%s.%s returned a result of null for \
|
### entry %s
|
###SEVERE_ERR_CONFIG_CHANGE_RESULT_ERROR_646=%s.%s failed for entry %s: result \
|
### code=%s, admin action required=%b, messages="%s"
|
###SEVERE_WARN_CONFIG_CHANGE_RESULT_ACTION_REQUIRED_647=%s.%s indicated that \
|
### administrative action is required for entry %s: messages="%s"
|
INFO_CONFIG_CHANGE_RESULT_MESSAGES_648=%s.%s war erfolgreich, hat aber folgende Nachricht f\u00fcr Eintrag %s erstellt: %s
|
###SEVERE_ERR_CONFIG_VATTR_INVALID_SEARCH_FILTER_649=Unable to parse value "%s" \
|
### from config entry "%s" as a valid search filter: %s
|
###SEVERE_ERR_CONFIG_VATTR_INITIALIZATION_FAILED_650=An error occurred while \
|
### trying to load an instance of class %s referenced in configuration entry %s \
|
### as a virtual attribute provider: %s
|
###SEVERE_ERR_CONFIG_VATTR_SV_TYPE_WITH_MV_PROVIDER_651=The virtual attribute \
|
### configuration in entry "%s" is not valid because attribute type %s is \
|
### single-valued but provider %s may generate multiple values
|
###SEVERE_ERR_CONFIG_VATTR_SV_TYPE_WITH_MERGE_VALUES_652=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
|
MILD_ERR_CONFIG_FILE_MODIFY_STRUCTURAL_CHANGE_NOT_ALLOWED_653=Konfigurationseintrag %s kann nicht ge\u00e4ndert werden, da die \u00c4nderung seine strukturelle Objektklasse \u00e4ndern w\u00fcrde
|
###FATAL_ERR_CONFIG_CANNOT_CALCULATE_DIGEST_654=An error occurred while \
|
### attempting to calculate a SHA-1 digest of file %s: %s
|
###SEVERE_WARN_CONFIG_MANUAL_CHANGES_DETECTED_655=The Directory Server has \
|
### detected that one or more external changes have been made to the \
|
### configuration file %s while the server was online, but another change has \
|
### caused the server configuration to be overwritten. The manual changes have \
|
### not been applied, but they have been preserved in file %s
|
###SEVERE_ERR_CONFIG_MANUAL_CHANGES_LOST_656=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
|
###SEVERE_ERR_CONFIG_ROTATION_POLICY_INVALID_CLASS_657=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server log rotation policy: %s
|
###SEVERE_ERR_CONFIG_RETENTION_POLICY_INVALID_CLASS_658=Class %s specified in \
|
### attribute ds-cfg-java-class of configuration entry %s cannot be \
|
### instantiated as a Directory Server log retention policy: %s
|
###SEVERE_ERR_CONFIG_ROTATION_POLICY_CANNOT_CREATE_POLICY_659=An error occurred \
|
### while attempting to create a Directory Server log rotation policy from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_RETENTION_POLICY_CANNOT_CREATE_POLICY_660=An error occurred \
|
### while attempting to create a Directory Server log retention policy from the \
|
### information in configuration entry %s: %s
|
###SEVERE_ERR_CONFIG_LOGGING_CANNOT_CREATE_WRITER_661=An error occurred while \
|
### attempting to create a text writer for a Directory Server logger from the \
|
### information in configuration entry %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_MULTIPLE_ENTRIES_IN_FILE_662=Schema configuration \
|
### file %s in directory %s contains more than one entry. Only the first entry \
|
### will be examined, and the additional entries will be ignored
|
###SEVERE_WARN_CONFIG_SCHEMA_UNPARSEABLE_EXTRA_DATA_IN_FILE_663=Schema \
|
### configuration file %s in directory %s contains additional data after the \
|
### schema entry that cannot be parsed by the LDIF reader: %s. The first entry \
|
### will be processed, but the remaining data will be ignored
|
###SEVERE_WARN_CONFIG_PLUGIN_EMPTY_ELEMENT_IN_ORDER_664=The plugin order \
|
### definition for plugins of type %s contains an empty element. This may cause \
|
### the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_MULTIPLE_WILDCARDS_IN_ORDER_665=The plugin order \
|
### definition for plugins of type %s contains multiple wildcard characters. All \
|
### plugin definitions should contain exactly one wildcard element to indicate \
|
### where unmatched plugins should be included in the order, and including \
|
### multiple wildcards may cause the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_LISTED_MULTIPLE_TIMES_666=The plugin order \
|
### definition for plugins of type %s includes multiple references to the '%s' \
|
### plugin. This may cause the plugin order to be evaluated incorrectly
|
###SEVERE_WARN_CONFIG_PLUGIN_ORDER_NO_WILDCARD_667=The plugin order definition \
|
### for plugins of type %s does not include a wildcard element to indicate where \
|
### unmatched plugins should be included in the order. The server will default \
|
### to invoking all unnamed plugins after set of named plugins
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_SYNTAX_IN_USE_668=Attribute syntax %s \
|
### cannot be deleted from the server because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_SYNTAX_IN_USE_669=Attribute syntax \
|
### %s cannot be disabled because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_MR_IN_USE_BY_AT_670=Matching rule %s \
|
### cannot be deleted from the server because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DELETE_MR_IN_USE_BY_MRU_671=Matching rule %s \
|
### cannot be deleted from the server because it is in use by matching rule use \
|
### %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_MR_IN_USE_BY_AT_672=Matching rule %s \
|
### cannot be disabled because it is in use by attribute type %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_DISABLE_MR_IN_USE_BY_MRU_673=Matching rule \
|
### %s cannot be disabled because it is in use by matching rule use %s
|
###SEVERE_ERR_CONFIG_WORK_QUEUE_INITIALIZATION_FAILED_674=Unable to initialize \
|
### an instance of class %s as a work queue as specified in configuration entry \
|
### %s: %s
|
INFO_CONFIG_WORK_QUEUE_CLASS_CHANGE_REQUIRES_RESTART_675=Die Klasse, die zur Bereitstellung der Implementierung der Arbeitswarteschlange f\u00fcr den Directory-Server verwendet wird, wurde von %s nach %s ge\u00e4ndert. Diese \u00c4nderung tritt erst in Kraft, wenn der Server neu gestartet wird
|
###SEVERE_ERR_CONFIG_FILE_ADD_APPLY_FAILED_676=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
|
###SEVERE_ERR_CONFIG_FILE_DELETE_APPLY_FAILED_677=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
|
###SEVERE_ERR_CONFIG_FILE_MODIFY_APPLY_FAILED_678=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
|
MILD_ERR_CONFIG_KEYMANAGER_CONFIG_NOT_ACCEPTABLE_679=Die Konfiguration des in Konfigurationseintrag %s definierten Schl\u00fcssel-Manager-Anbieters ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_TRUSTMANAGER_CONFIG_NOT_ACCEPTABLE_680=Die Konfiguration des in Konfigurationseintrag %s definierten Trust-Manager-Anbieters ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_AUTHZ_CONFIG_NOT_ACCEPTABLE_681=Die Konfiguration des in Konfigurationseintrag %s definierten Trust-Manager-Anbieters ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_ACCTNOTHANDLER_CONFIG_NOT_ACCEPTABLE_682=Die Konfiguration der in Konfigurationseintrag %s definierten Kontostatusbenachrichtigungsroutine ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_SCHEMA_SYNTAX_CONFIG_NOT_ACCEPTABLE_683=Die Konfiguration der in Konfigurationseintrag %s definierten Attributsyntax ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_CERTMAPPER_CONFIG_NOT_ACCEPTABLE_684=Die Konfiguration des in Konfigurationseintrag %s definierten Zertifikat-Mappers ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_GROUP_CONFIG_NOT_ACCEPTABLE_686=Die Konfiguration der in Konfigurationseintrag %s definierten Gruppenimplementierung ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_IDMAPPER_CONFIG_NOT_ACCEPTABLE_687=Die Konfiguration des in Konfigurationseintrag %s definierten Identit\u00e4t-Mappers ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_SCHEMA_MR_CONFIG_NOT_ACCEPTABLE_688=Die Konfiguration der in Konfigurationseintrag %s definierten \u00dcbereinstimmungsregel ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_PWGENERATOR_CONFIG_NOT_ACCEPTABLE_689=Die Konfiguration des in Konfigurationseintrag %s definierten Passwortgenerators ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_PWSCHEME_CONFIG_NOT_ACCEPTABLE_690=Die Konfiguration des in Konfigurationseintrag %s definierten Passwortspeicherschemas ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_PWVALIDATOR_CONFIG_NOT_ACCEPTABLE_691=Die Konfiguration der in Konfigurationseintrag %s definierten Passwort\u00fcberpr\u00fcfung ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_PLUGIN_CONFIG_NOT_ACCEPTABLE_692=Die Konfiguration des in Konfigurationseintrag %s definierten Plugins ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_SASL_CONFIG_NOT_ACCEPTABLE_693=Die Konfiguration der in Konfigurationseintrag %s definierten SASL-Mechanismus-Behandlungsroutine ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_VATTR_CONFIG_NOT_ACCEPTABLE_694=Die Konfiguration des in Konfigurationseintrag %s definierten virtuellen Attributanbieters ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_ALERTHANDLER_CONFIG_NOT_ACCEPTABLE_695=Die Konfiguration der in Konfigurationseintrag %s definierten Warnungsbehandlungsroutine ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_ALERTHANDLER_INITIALIZATION_FAILED_696=Fehler beim Versuch, eine Instanz der Klasse %s als Warnungsbehandlungsroutine zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
###SEVERE_ERR_CONFIG_CORE_INVALID_SMTP_SERVER_697=The provided SMTP server value \
|
### '%s' is invalid. An SMTP server value must have an IP address or a \
|
### resolvable name, and it may optionally be followed by a colon and an integer \
|
### value between 1 and 65535 to specify the server port number
|
###SEVERE_ERR_STARTOK_CANNOT_OPEN_FOR_READING_698=An error occurred while \
|
### attempting to open the current configuration file %s for reading in order to \
|
### copy it to the ".startok" file: %s
|
###SEVERE_ERR_STARTOK_CANNOT_OPEN_FOR_WRITING_699=An error occurred while \
|
### attempting to open file %s in order to write the ".startok" configuration \
|
### file: %s
|
###SEVERE_ERR_STARTOK_CANNOT_WRITE_700=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
|
###SEVERE_ERR_STARTOK_CANNOT_RENAME_701=An error occurred while attempting to \
|
### rename file %s to %s for use as the ".startok" configuration file: %s
|
NOTICE_CONFIG_FILE_USING_STARTOK_FILE_702=Der Directory-Server wird mit der letzten als funktionierend bekannten Konfigurationsdatei %s anstelle mit der aktuellen Konfigurationsdatei %s gestartet
|
###SEVERE_WARN_CONFIG_FILE_NO_STARTOK_FILE_703=No last known good configuration \
|
### file %s exists. The server will attempt to start using the active \
|
### configuration file %s
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_INVALID_704=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: %s
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_INVALID_FORM_705=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### does not follow a singular property=value form
|
###SEVERE_ERR_CONFIG_JE_PROPERTY_SHADOWS_CONFIG_706=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### shadows configuration attribute %s
|
###SEVERE_ERR_CONFIG_JE_DUPLICATE_PROPERTY_707=An error occurred while \
|
### trying to parse and validate Berkeley DB JE property %s: the property \
|
### is already defined for this component
|
INFO_CONFIG_JE_PROPERTY_REQUIRES_RESTART_708=Das Setzen der Berkeley DB JE-Eigenschaft %s tritt erst in Kraft wenn die Komponente, f\u00fcr die sie gesetzt wurde, neu gestartet wird
|
###SEVERE_ERR_CONFIG_LOGGING_CANNOT_OPEN_FILE_709=An error occurred while \
|
### attempting to open the configured log file %s for logger %s: %s
|
###SEVERE_ERR_CONFIG_WORKFLOW_ELEMENT_CONFIG_NOT_ACCEPTABLE_710=The configuration \
|
### for the workflow element defined in configuration entry %s was not \
|
### acceptable: %s
|
###SEVERE_ERR_CONFIG_WORKFLOW_ELEMENT_CANNOT_INITIALIZE_711=An error occurred \
|
### while trying to initialize a workflow element from class %s with the \
|
### information in configuration entry %s: %s. This workflow element will be \
|
### disabled
|
MILD_ERR_CONFIG_WORKFLOW_ELEMENT_ALREADY_REGISTERED_712=Das Arbeitsablaufelement %s ist bereits beim Directory-Server registriert. Diese Arbeitsablaufelement wird ignoriert
|
###SEVERE_ERR_CONFIG_WORKFLOW_CANNOT_CONFIGURE_MANUAL_713=An error occurred \
|
### while trying to configure in manual mode the workflows in the \
|
### Directory Server, and rollback to automatic configuration mode has failed \
|
### too. If the server is in an unstab\
|
### le state restart it with the last \
|
### valid configuration
|
###SEVERE_ERR_CONFIG_WORKFLOW_CANNOT_CONFIGURE_AUTO_714=An error occurred \
|
### while trying to configure in automatic mode the workflows in the \
|
### Directory Server, and rollback to manual configuration mode has failed \
|
### too. If the server is in an unstable state restart it with the last \
|
### valid configuration
|
###SEVERE_ERR_CONFIG_LOGGING_INSANE_MODE_715=Invalid UNIX file permissions %s \
|
### does not allow write access to the log file by the log publisher
|
###SEVERE_ERR_CONFIG_LOGGING_MODE_INVALID_716=Invalid UNIX file permissions %s: %s
|
MILD_ERR_CONFIG_EXTENSION_CONFIG_NOT_ACCEPTABLE_717=Die Konfiguration der in Konfigurationseintrag %s definierten Erweiterung ist ung\u00fcltig: %s
|
MILD_ERR_CONFIG_EXTENSION_INITIALIZATION_FAILED_718=Fehler beim Versuch, eine Instanz der Klasse %s als eine Erweiterung zu initialisieren, wie im Konfigurationseintrag %s definiert ist: %s
|
###SEVERE_ERR_CONFIG_NETWORKGROUPREQUESTFILTERINGPOLICY_INVALID_ATTRIBUTE_719=The \
|
### allowed attribute %s specified in configuration entry %s is also defined as \
|
### a prohibited attribute
|
###SEVERE_ERR_CONFIG_NETWORKGROUPREQUESTFILTERINGPOLICY_INVALID_SUBTREE_720=The \
|
### allowed subtree %s specified in configuration entry %s is also defined as \
|
### a prohibited subtree
|
###SEVERE_ERR_CONFIG_NETWORK_GROUP_CONFIG_NOT_ACCEPTABLE_721=The configuration \
|
### for the network group defined in configuration entry %s was not acceptable: %s
|
###SEVERE_ERR_CONFIG_NETWORK_GROUP_POLICY_CANNOT_INITIALIZE_722=An error occurred \
|
### while trying to initialize a network group policy loaded from class %s with \
|
### the information in configuration entry %s: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CANNOT_PARSE_LDAP_SYNTAX_723=An ldapSyntaxes \
|
### attribute read from schema configuration file %s could not be parsed: %s
|
###SEVERE_WARN_CONFIG_SCHEMA_CONFLICTING_LDAP_SYNTAX_724=An ldap syntax read \
|
### from schema configuration file %s conflicts with another ldap syntax already \
|
### read into the schema: %s. The later ldap syntax description will be used
|
