# 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-2008 Sun Microsystems, Inc.
|
|
|
|
#
|
# Global directives
|
#
|
global.category=BACKEND
|
|
#
|
# 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
|
#
|
FATAL_ERR_BACKEND_CANNOT_REMOVE_MULTIBASE_SUB_SUFFIX_1=An attempt was made to de-register sub-suffix "%s" from the backend with suffix "%s". However, the subordinate backend containing that sub-suffix also contains additional sub-suffixes and may not be de-registered. It may be possible to remove this sub-suffix by editing the configuration for the subordinate backend with which it is associated
|
FATAL_ERR_ROOTDSE_CONFIG_ENTRY_NULL_2=An attempt was made to configure the root DSE backend without providing a configuration entry. This is not allowed
|
INFO_ROOTDSE_SUBORDINATE_BASE_DESCRIPTION_3=Le jeu de DN de base sera utilis\u00e9 pour chaque recherche singleLevel, wholeSubtree et subordinateSubtree bas\u00e9e sur la racine DSE. En son absence, le jeu de tous les suffixes d\u00e9finis par l'utilisateur sera utilis\u00e9
|
SEVERE_WARN_ROOTDSE_NO_BACKEND_FOR_SUBORDINATE_BASE_4=Base DN "%s" is configured as one of the subordinate base DNs to use for searches below the root DSE. However, this base DN is not handled by any suffix registered with the Directory Server and will therefore not be used
|
SEVERE_WARN_ROOTDSE_SUBORDINATE_BASE_EXCEPTION_5=An unexpected problem occurred while trying to determine the set of subordinate base DNs to use for searches below the root DSE: %s
|
MILD_WARN_ROOTDSE_GET_ENTRY_NONROOT_6=Il a \u00e9t\u00e9 demand\u00e9 au backend de DSE racine de r\u00e9cup\u00e9rer une entr\u00e9e avec DN "%s". Seule une demande de r\u00e9cup\u00e9ration de la DSE racine elle-m\u00eame peut \u00eatre adress\u00e9e \u00e0 ce backend. Cependant, il v\u00e9rifiera avec les backends subordonn\u00e9s d\u00e9finis s'il peut trouver l'entr\u00e9e souhait\u00e9e.
|
MILD_ERR_ROOTDSE_ADD_NOT_SUPPORTED_7=Impossible d'ajouter l'entr\u00e9e "%s" car le backend de DSE racine ne prend pas en charge les op\u00e9ration d'ajout
|
MILD_ERR_ROOTDSE_DELETE_NOT_SUPPORTED_8=Impossible de supprimer l'entr\u00e9e "%s" car le backend de DSE racine ne prend pas en charge les op\u00e9rations de suppression
|
MILD_ERR_ROOTDSE_MODIFY_NOT_SUPPORTED_9=Impossible de mettre l'entr\u00e9e "%s" \u00e0 jour car le backend de DSE racine ne prend pas en charge les op\u00e9rations de modification. Si vous souhaitez changer le contenu du DSE racine, vous devriez pouvoir le faire en modifant l'entr\u00e9e "%s" dans la configuration
|
MILD_ERR_ROOTDSE_MODIFY_DN_NOT_SUPPORTED_10=Impossible de renommer l'entr\u00e9e "%s" car le backend de DSE racine ne prend pas en charge les op\u00e9rations de modification de DN
|
MILD_ERR_ROOTDSE_INVALID_SEARCH_BASE_11=Impossible d'effectuer une recherche (ID de connexion %d, ID d'op\u00e9ration %d) avec un DN de base de "%" dans le backend de DSE racine. Le DN de base pour les recherches dans ce backend doit \u00eatre le DN du DSE racine.
|
SEVERE_ERR_ROOTDSE_UNEXPECTED_SEARCH_FAILURE_12=An unexpected failure occurred while trying to process a search operation (connection ID %d, operation ID %d) in the root DSE backend: %s
|
SEVERE_ERR_ROOTDSE_INVALID_SEARCH_SCOPE_13=Unable to process the search with connection ID %d and operation ID %d because it had an invalid scope of %s
|
SEVERE_ERR_ROOTDSE_UNABLE_TO_CREATE_LDIF_WRITER_14=An unexpected error occurred while trying to open the LDIF writer for the root DSE backend: %s
|
SEVERE_ERR_ROOTDSE_UNABLE_TO_EXPORT_DSE_15=An unexpected error occurred while trying to export the root DSE entry to the specified LDIF target: %s
|
SEVERE_ERR_ROOTDSE_IMPORT_NOT_SUPPORTED_16=The root DSE backend does not support LDIF import operations
|
SEVERE_ERR_ROOTDSE_BACKUP_AND_RESTORE_NOT_SUPPORTED_17=The root DSE backend does not provide a facility for backup and restore operations. The contents of the root DSE should be backed up as part of the Directory Server configuration
|
INFO_ROOTDSE_USING_SUFFIXES_AS_BASE_DNS_18=La configuration du DSE racine ayant \u00e9t\u00e9 mise \u00e0 jour, celui-ci va d\u00e9sormais utiliser le jeu d\u00e9fini pour les suffixes Directory Server lors de recherches sous le DSE racine
|
INFO_ROOTDSE_USING_NEW_SUBORDINATE_BASE_DNS_19=La configuration du DSE racine ayant \u00e9t\u00e9 mise \u00e0 jour, celui-ci va d\u00e9sormais utiliser le jeu de DN de base %s lors de recherches sous le DSE racine
|
INFO_ROOTDSE_USING_NEW_USER_ATTRS_20=La configuration du DSE racine ayant \u00e9t\u00e9 mise \u00e0 jour, celui-ci va d\u00e9sormais utiliser un nouveau jeu d'attributs d\u00e9finis par l'utilisateur
|
SEVERE_ERR_MONITOR_CONFIG_ENTRY_NULL_21=An attempt was made to configure the monitor backend without providing a configuration entry. This is not allowed, and no monitor information will be available over protocol
|
SEVERE_ERR_MONITOR_CANNOT_DECODE_MONITOR_ROOT_DN_22=An unexpected error occurred while attempting to decode cn=monitor as the base DN for the Directory Server monitor information: %s. No monitor information will be available over protocol
|
MILD_ERR_MONITOR_ADD_NOT_SUPPORTED_23=Impossible d'ajouter l'entr\u00e9e "%s" car le backend de moniteur ne prend pas en charge les op\u00e9rations d'ajout
|
MILD_ERR_MONITOR_DELETE_NOT_SUPPORTED_24=Impossible de supprimer l'entr\u00e9e "%s" car le backend de moniteur ne prend pas en charge les op\u00e9rations de suppression
|
MILD_ERR_MONITOR_MODIFY_NOT_SUPPORTED_25=Impossible de mettre l'entr\u00e9e "%s" \u00e0 jour car le backend de moniteur ne prend pas en charge les op\u00e9rations de modification. Si vous souhaitez changer le contenu du moniteur de base, vous devriez pouvoir le faire en modifant l'entr\u00e9e "%s" dans la configuration
|
MILD_ERR_MONITOR_MODIFY_DN_NOT_SUPPORTED_26=Impossible de renommer l'entr\u00e9e "%s" car le backend de moniteur ne prend pas en charge les op\u00e9rations de modification de DN
|
SEVERE_ERR_MONITOR_UNABLE_TO_EXPORT_BASE_27=An error occurred while attempting to export the base monitor entry: %s
|
SEVERE_ERR_MONITOR_UNABLE_TO_EXPORT_PROVIDER_ENTRY_28=An error occurred while attempting to export the monitor entry for monitor provider %s: %s
|
SEVERE_ERR_MONITOR_IMPORT_NOT_SUPPORTED_29=The monitor backend does not support LDIF import operations
|
SEVERE_ERR_MONITOR_BACKUP_AND_RESTORE_NOT_SUPPORTED_30=The monitor backend does not provide a facility for backup and restore operations
|
INFO_MONITOR_USING_NEW_USER_ATTRS_31=La configuration du moniteur ayant \u00e9t\u00e9 mise \u00e0 jour, celui-ci va d\u00e9sormais utiliser un nouveau jeu d'attributs d\u00e9finis par l'utilisateur
|
MILD_ERR_MONITOR_GET_ENTRY_NULL_32=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e du backend de moniteur car le DN fourni \u00e9tait null
|
MILD_ERR_MONITOR_BASE_TOO_DEEP_33=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e %s du backend de moniteur car le DN est trop profond. Les entr\u00e9es de moniteur ne doivent pas se trouver plus d'un niveau sous %s
|
MILD_ERR_MONITOR_INVALID_BASE_34=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e %s du backend de moniteur car le DN ne se trouve pas sous la base de moniteur de %s
|
MILD_ERR_MONITOR_MULTIVALUED_RDN_35=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e %s du backend de moniteur car les entr\u00e9es de moniteur ne doivent pas contenir de RDN \u00e0 valeurs multiples
|
MILD_ERR_MONITOR_NO_SUCH_PROVIDER_36=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e %s du backend de moniteur en l'absence d'un fournisseur de moniteur "%s" enregistr\u00e9 avec Directory Server
|
INFO_MONITOR_UPTIME_37=%d jours %d heures %d minutes %d secondes
|
SEVERE_ERR_SCHEMA_CONFIG_ENTRY_NULL_38=An attempt was made to configure the schema backend without providing a configuration entry. This is not allowed, and no schema information will be available over protocol
|
INFO_SCHEMA_DESCRIPTION_ENTRY_DN_39=DN ou jeu de DN pour les entr\u00e9es pouvant \u00eatre r\u00e9cup\u00e9r\u00e9es afin de r\u00e9cup\u00e9rer les informations de sch\u00e9ma de Directory Server. Veuillez fournir plusieurs valeurs si le sch\u00e9ma doit \u00eatre disponible dans plusieurs emplacements pour des raisons de compatibilit\u00e9. En l'absence de valeur, une valeur par d\u00e9faut de "cn=schema" est utilis\u00e9e
|
SEVERE_ERR_SCHEMA_CANNOT_DETERMINE_BASE_DN_40=An error occurred while trying to determine the base DNs to use when publishing the Directory Server schema information, as specified in the ds-cfg-schema-entry-dn attribute of configuration entry %s: %s. The default schema base DN of cn=schema will be used
|
MILD_ERR_SCHEMA_ADD_NOT_SUPPORTED_41=Impossible d'ajouter l'entr\u00e9e "%s" car le backend de sch\u00e9ma ne prend pas en charge les op\u00e9rations d'ajout
|
MILD_ERR_SCHEMA_DELETE_NOT_SUPPORTED_42=Impossible de supprimer l'entr\u00e9e "%s" car le backend de sch\u00e9ma ne prend pas en charge les op\u00e9rations de suppression
|
MILD_ERR_SCHEMA_MODIFY_NOT_SUPPORTED_43=Impossible de mettre l'entr\u00e9e "%s" \u00e0 jour car le backend de sch\u00e9ma ne prend plus en charge les op\u00e9rations de modification. Si vous souhaitez changer le contenu du sch\u00e9ma de base, vous devriez pouvoir le faire en modifant l'entr\u00e9e "%s" dans la configuration
|
MILD_ERR_SCHEMA_MODIFY_DN_NOT_SUPPORTED_44=Impossible de renommer l'entr\u00e9e "%s" car le backend de sch\u00e9ma ne prend pas en charge les op\u00e9rations de modification de DN
|
SEVERE_ERR_SCHEMA_UNABLE_TO_EXPORT_BASE_45=An error occurred while attempting to export the base schema entry: %s
|
SEVERE_ERR_SCHEMA_IMPORT_NOT_SUPPORTED_46=The schema backend does not support LDIF import operations
|
SEVERE_ERR_SCHEMA_BACKUP_AND_RESTORE_NOT_SUPPORTED_47=The schema backend does not yet provide a facility for backup and restore operations
|
MILD_ERR_SCHEMA_INVALID_BASE_48=Impossible de r\u00e9cup\u00e9rer l'entr\u00e9e demand\u00e9e % du backend de sch\u00e9ma car le DN est \u00e9gal \u00e0 un des DN d'entr\u00e9e de sch\u00e9ma
|
SEVERE_ERR_SCHEMA_UNABLE_TO_CREATE_LDIF_WRITER_49=An unexpected error occurred while trying to open the LDIF writer for the schema backend: %s
|
INFO_SCHEMA_DEREGISTERED_BASE_DN_50=Le DN %s n'est plus inscrit et ne sera donc plus disponible en tant que DN d'entr\u00e9e de sch\u00e9ma
|
SEVERE_ERR_SCHEMA_CANNOT_DEREGISTER_BASE_DN_51=An error occurred while trying to deregister %s as a schema entry DN: %s
|
INFO_SCHEMA_REGISTERED_BASE_DN_52= Le DN %s est bien inscrit en tant que DN d'entr\u00e9e de sch\u00e9ma
|
SEVERE_ERR_SCHEMA_CANNOT_REGISTER_BASE_DN_53=An error occurred while trying to register %s as a schema entry DN: %s
|
INFO_SCHEMA_USING_NEW_USER_ATTRS_54=La configuration du sch\u00e9ma ayant \u00e9t\u00e9 mise \u00e0 jour, celui-ci va d\u00e9sormais utiliser un nouveau jeu d'attributs d\u00e9finis par l'utilisateur
|
FATAL_ERR_BACKEND_CANNOT_LOCK_ENTRY_55=The Directory Server was unable to obtain a lock on entry %s after multiple attempts. This could mean that the entry is already locked by a long-running operation or that the entry has previously been locked but was not properly unlocked
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_GET_MAC_56=An error occurred while attempting to obtain the %s MAC provider to create the signed hash for the backup: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_GET_DIGEST_57=An error occurred while attempting to obtain the %s message digest to create the hash for the backup: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_58=An error occurred while trying to create the schema archive file %s in directory %s: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_GET_CIPHER_59=An error occurred while attempting to obtain the cipher to use to encrypt the backup: %s
|
SEVERE_ERR_SCHEMA_BACKUP_ZIP_COMMENT_60=%s schema backup %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_LIST_SCHEMA_FILES_61=An error occurred while attempting to obtain a list of the files in directory %s to include in the schema backup: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_BACKUP_SCHEMA_FILE_62=An error occurred while attempting to back up schema file %s: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_CLOSE_ZIP_STREAM_63=An error occurred while trying to close the schema archive file %s in directory %s: %s
|
SEVERE_ERR_SCHEMA_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_64=An error occurred while attempting to update the backup descriptor file %s with information about the schema backup: %s
|
SEVERE_ERR_SCHEMA_RESTORE_NO_SUCH_BACKUP_65=Unable to restore or verify schema backup %s in directory %s because no such backup exists
|
SEVERE_ERR_SCHEMA_RESTORE_NO_BACKUP_FILE_66=Unable to restore or verify schema backup %s in directory %s because the archive filename could not be determined
|
SEVERE_ERR_SCHEMA_RESTORE_NO_SUCH_FILE_67=Unable to restore or verify schema backup %s because the specified archive file %s does not exist
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CHECK_FOR_ARCHIVE_68=Unable to restore or verify schema backup %s because an error occurred while trying to determine whether backup archive %s exists: %s
|
SEVERE_ERR_SCHEMA_RESTORE_UNKNOWN_DIGEST_69=Unable to restore or verify schema 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_SCHEMA_RESTORE_CANNOT_GET_DIGEST_70=Unable to restore or verify schema backup %s because it has an unsigned hash that uses an unknown or unsupported digest algorithm of %s
|
SEVERE_ERR_SCHEMA_RESTORE_UNKNOWN_MAC_71=Unable to restore or verify schema 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_SCHEMA_RESTORE_CANNOT_GET_MAC_72=Unable to restore or verify schema backup %s because it has a signed hash that uses an unknown or unsupported MAC algorithm of %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_OPEN_BACKUP_FILE_73=Unable to restore or verify schema backup %s because an error occurred while attempting to open the backup archive file %s: %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_GET_CIPHER_75=Unable to restore or verify schema backup %s because it is encrypted using an unknown or unsupported cipher: %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_RENAME_CURRENT_DIRECTORY_76=Unable to restore schema backup %s because an error occurred while attempting to rename the current schema directory from %s to %s: %s
|
NOTICE_SCHEMA_RESTORE_RESTORED_OLD_SCHEMA_77=Une erreur a emp\u00each\u00e9 la sauvegarde du sch\u00e9ma d'\u00eatre correctement restaur\u00e9e. Cependant, les fichiers du sch\u00e9ma d'origine en place avant le d\u00e9but de la proc\u00e9dure de restauration ont \u00e9t\u00e9 conserv\u00e9s et se trouvent maintenant dans leur emplacement d'origine de %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_RESTORE_OLD_SCHEMA_78=An error occurred that prevented the schema backup from being properly restored. The original schema files that were in place before the start of the restore process have been preserved and are contained in the %s directory
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CREATE_SCHEMA_DIRECTORY_79=Unable to restore schema 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_SCHEMA_RESTORE_OLD_SCHEMA_SAVED_80=An error occurred that prevented the schema backup from being properly restored. The original schema files that were in place before the start of the restore process have been preserved in the %s directory
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_GET_ZIP_ENTRY_81=Unable to restore or verify schema backup %s because an error occurred while trying to read the next entry from the archive file %s: %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_CREATE_FILE_82=Unable to restore schema backup %s because an error occurred while trying to recreate file %s: %s
|
SEVERE_ERR_SCHEMA_RESTORE_CANNOT_PROCESS_ARCHIVE_FILE_83=Unable to restore or verify schema backup %s because an error occurred while processing archived file %s: %s
|
SEVERE_ERR_SCHEMA_RESTORE_ERROR_ON_ZIP_STREAM_CLOSE_84=Unable to restore or verify schema backup %s because an unexpected error occurred while trying to close the archive file %s: %s
|
NOTICE_SCHEMA_RESTORE_UNSIGNED_HASH_VALID_85=La synth\u00e8se de message calcul\u00e9e \u00e0 partir du fichier de sauvegarde correspond \u00e0 la synth\u00e8se stock\u00e9e dans les informations de sauvegarde
|
SEVERE_ERR_SCHEMA_RESTORE_UNSIGNED_HASH_INVALID_86=Unable to restore or verify schema backup %s because the message digest calculated from the backup archive does not match the digest stored with the backup information
|
NOTICE_SCHEMA_RESTORE_SIGNED_HASH_VALID_87=La synth\u00e8se sign\u00e9e calcul\u00e9e \u00e0 partir de la sauvegarde correspond \u00e0 la signature stock\u00e9e dans les informations de sauvegarde
|
SEVERE_ERR_SCHEMA_RESTORE_SIGNED_HASH_INVALID_88=Unable to restore or verify schema backup %s because the signed digest calculated from the backup archive does not match the signature stored with the backup information
|
NOTICE_SCHEMA_RESTORE_VERIFY_SUCCESSFUL_89=Tous les tests effectu\u00e9s sur la sauvegarde de sch\u00e9ma %s du r\u00e9pertoire %s montrent que le fichier semble valide.
|
NOTICE_SCHEMA_RESTORE_SUCCESSFUL_90=La sauvegarde de sch\u00e9ma %s a \u00e9t\u00e9 restaur\u00e9e \u00e0 partir du fichier du r\u00e9pertoire %s
|
SEVERE_ERR_TASK_INVALID_STATE_91=The task defined in entry %s is invalid because it has an invalid state %s
|
SEVERE_ERR_TASK_CANNOT_PARSE_SCHEDULED_START_TIME_92=An error occurred while trying to parse the scheduled start time value %s from task entry %s
|
SEVERE_ERR_TASK_CANNOT_PARSE_ACTUAL_START_TIME_93=An error occurred while trying to parse the actual start time value %s from task entry %s
|
SEVERE_ERR_TASK_CANNOT_PARSE_COMPLETION_TIME_94=An error occurred while trying to parse the completion time value %s from task entry %s
|
SEVERE_ERR_TASK_MISSING_ATTR_95=Task entry %s is missing required attribute %s
|
SEVERE_ERR_TASK_MULTIPLE_ATTRS_FOR_TYPE_96=There are multiple instances of attribute %s in task entry %s
|
SEVERE_ERR_TASK_NO_VALUES_FOR_ATTR_97=There are no values for attribute %s in task entry %s
|
SEVERE_ERR_TASK_MULTIPLE_VALUES_FOR_ATTR_98=There are multiple values for attribute %s in task entry %s
|
SEVERE_ERR_TASK_EXECUTE_FAILED_99=An error occurred while executing the task defined in entry %s: %s
|
SEVERE_ERR_RECURRINGTASK_NO_ID_ATTRIBUTE_100=The provided recurring task entry does not contain attribute %s which is needed to hold the recurring task ID
|
SEVERE_ERR_RECURRINGTASK_MULTIPLE_ID_TYPES_101=The provided recurring task entry contains multiple attributes with type %s, which is used to hold the recurring task ID, but only a single instance is allowed
|
SEVERE_ERR_RECURRINGTASK_NO_ID_102=The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the recurring task ID
|
SEVERE_ERR_RECURRINGTASK_MULTIPLE_ID_VALUES_103=The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the recurring task ID, but only a single value is allowed
|
SEVERE_ERR_RECURRINGTASK_NO_CLASS_ATTRIBUTE_104=The provided recurring task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic
|
SEVERE_ERR_RECURRINGTASK_MULTIPLE_CLASS_TYPES_105=The provided recurring task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed
|
SEVERE_ERR_RECURRINGTASK_NO_CLASS_VALUES_106=The provided recurring task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic
|
SEVERE_ERR_RECURRINGTASK_MULTIPLE_CLASS_VALUES_107=The provided recurring task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed
|
SEVERE_ERR_RECURRINGTASK_CANNOT_LOAD_CLASS_108=An error occurred while attempting to load class %s specified in attribute %s of the provided recurring task entry: %s. Does this class exist in the Directory Server classpath?
|
SEVERE_ERR_RECURRINGTASK_CANNOT_INSTANTIATE_CLASS_AS_TASK_109=An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?
|
SEVERE_ERR_RECURRINGTASK_CANNOT_INITIALIZE_INTERNAL_110=An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s
|
SEVERE_ERR_TASKBE_CONFIG_ENTRY_NULL_111=The configuration entry provided when attempting to initialize the task backend was null
|
SEVERE_ERR_TASKBE_NO_BASE_DNS_112=The task backend configuration entry does not contain any base DNs. There must be exactly one base DN for task information in the Directory Server
|
SEVERE_ERR_TASKBE_MULTIPLE_BASE_DNS_113=The task backend configuration entry contains multiple base DNs. There must be exactly one base DN for task information in the Directory Server
|
SEVERE_ERR_TASKBE_CANNOT_DECODE_RECURRING_TASK_BASE_DN_114=An error occurred while attempting to decode recurring task base %s as a DN: %s
|
SEVERE_ERR_TASKBE_CANNOT_DECODE_SCHEDULED_TASK_BASE_DN_115=An error occurred while attempting to decode scheduled task base %s as a DN: %s
|
INFO_TASKBE_DESCRIPTION_RETENTION_TIME_116=La p\u00e9riode (en secondes) pendant laquelle les informations de la t\u00e2che doivent \u00eatre conserv\u00e9es apr\u00e8s le traitement de cette t\u00e2che est \u00e9coul\u00e9e. Une fois cette p\u00e9riode \u00e9coul\u00e9e, les informations de la t\u00e2che seront automatiquement supprim\u00e9es pour pr\u00e9server la m\u00e9moire et l'espace disque
|
SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_RETENTION_TIME_117=An unexpected error occurred while attempting to initialize the task retention time configuration: %s
|
INFO_TASKBE_DESCRIPTION_BACKING_FILE_118=Chemin vers le fichier de sauvegarde pour le backend de t\u00e2che. Ce fichier LDIF conservera toute la configuration pour les t\u00e2ches planifi\u00e9es et r\u00e9currentes d\u00e9finies
|
SEVERE_ERR_TASKBE_CANNOT_INITIALIZE_BACKING_FILE_119=An unexpected error occurred while attempting to initialize the task backing file configuration: %s
|
SEVERE_ERR_TASKBE_NO_BACKING_FILE_120=The updated configuration entry does not have a value for the required %s attribute, which specifies the path to the task data backing file
|
SEVERE_ERR_TASKBE_BACKING_FILE_EXISTS_121=The specified task data backing file %s already exists and the Directory Server will not attempt to overwrite it. Please delete or rename the existing file before attempting to use that path for the new backing file, or choose a new path
|
SEVERE_ERR_TASKBE_INVALID_BACKING_FILE_PATH_122=The specified path %s for the new task data backing file appears to be an invalid path. Please choose a new path for the task data backing file
|
SEVERE_ERR_TASKBE_BACKING_FILE_MISSING_PARENT_123=The parent directory %s for the new task data backing file %s does not exist. Please create this directory before attempting to use this path for the new backing file or choose a new path
|
SEVERE_ERR_TASKBE_BACKING_FILE_PARENT_NOT_DIRECTORY_124=The parent directory %s for the new task data backing file %s exists but is not a directory. Please choose a new path for the task data backing file
|
SEVERE_ERR_TASKBE_ERROR_GETTING_BACKING_FILE_125=An error occurred while attempting to determine the new path to the task data backing file: %s
|
SEVERE_ERR_TASKBE_NO_RETENTION_TIME_126=The updated configuration entry does not have a value for the required %s attribute, which specifies the length of time in seconds that information about completed tasks should be retained before they are cleaned up
|
SEVERE_ERR_TASKBE_ERROR_GETTING_RETENTION_TIME_127=An error occurred while attempting to determine the completed task retention time: %s
|
INFO_TASKBE_UPDATED_RETENTION_TIME_128=La p\u00e9riode de r\u00e9tention de la t\u00e2che termin\u00e9e a \u00e9t\u00e9 mise \u00e0 jour et dure maintenant %d secondes. Elle prend effet imm\u00e9diatement
|
INFO_TASKBE_UPDATED_BACKING_FILE_129=Le chemin vers le fichier de sauvegarde des donn\u00e9es de la t\u00e2che est maintenant %s. Un instantan\u00e9 de la configuration de la t\u00e2che actuelle a \u00e9t\u00e9 \u00e9crit dans ce fichier et continuera \u00e0 \u00eatre utilis\u00e9 pour de futures mises \u00e0 jour
|
SEVERE_ERR_TASKBE_ADD_DISALLOWED_DN_130=New entries in the task backend may only be added immediately below %s for scheduled tasks or immediately below %s for recurring tasks
|
SEVERE_ERR_TASKBE_MODIFY_DN_NOT_SUPPORTED_131=Modify DN operations are not supported in the task backend
|
INFO_TASKBE_BACKING_FILE_HEADER_132=Ce fichier contient les donn\u00e9es utilis\u00e9es par le backend du planificateur de t\u00e2ches de Directory Server. N'\u00e9ditez pas directement ce fichier car il existe un risque de perte de ces modifications. Les d\u00e9finitions de t\u00e2ches planifi\u00e9es et r\u00e9currentes doivent uniquement \u00eatre \u00e9dit\u00e9es au moyen des utilitaires d'administration fournis avec Directory Server
|
SEVERE_ERR_TASKSCHED_DUPLICATE_RECURRING_ID_133=Unable to add recurring task %s to the task scheduler because another recurring task already exists with the same ID
|
SEVERE_ERR_TASKSCHED_DUPLICATE_TASK_ID_134=Unable to schedule task %s because another task already exists with the same ID
|
SEVERE_ERR_TASKSCHED_CANNOT_FIND_RECURRING_TASK_135=Task %s has completed processing and indicates that it is associated with recurring task %s but no recurring task with that ID is currently defined so it is not possible to schedule the next iteration
|
SEVERE_ERR_TASKSCHED_ERROR_SCHEDULING_RECURRING_ITERATION_136=An error occurred while attempting to schedule the next iteration of recurring task %s: %s
|
SEVERE_ERR_TASKSCHED_CANNOT_PARSE_ENTRY_RECOVERABLE_137=An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is not a fatal error, so the task scheduler will attempt to continue parsing the file and schedule any additional tasks that it contains
|
FATAL_ERR_TASKSCHED_CANNOT_PARSE_ENTRY_FATAL_138=An error occurred while attempting to read an entry from the tasks backing file %s on or near line %d: %s. This is an unrecoverable error, and parsing cannot continue
|
SEVERE_ERR_TASKSCHED_ENTRY_HAS_NO_PARENT_139=Entry %s read from the tasks backing file is invalid because it has no parent and does not match the task root DN of %s
|
SEVERE_ERR_TASKSCHED_CANNOT_SCHEDULE_RECURRING_TASK_FROM_ENTRY_140=An error occurred while attempting to parse entry %s as a recurring task and add it to the scheduler: %s
|
SEVERE_ERR_TASKSCHED_CANNOT_SCHEDULE_TASK_FROM_ENTRY_141=An error occurred while attempting to parse entry %s as a task and add it to the scheduler: %s
|
SEVERE_ERR_TASKSCHED_INVALID_TASK_ENTRY_DN_142=Entry %s read from the tasks backing file %s has a DN which is not valid for a task or recurring task definition and will be ignored
|
SEVERE_ERR_TASKSCHED_ERROR_READING_TASK_BACKING_FILE_143=An error occurred while attempting to read from the tasks data backing file %s: %s
|
SEVERE_ERR_TASKSCHED_CANNOT_CREATE_BACKING_FILE_144=An error occurred while attempting to create a new tasks backing file %s for use with the task scheduler: %s
|
SEVERE_ERR_TASKSCHED_NO_CLASS_ATTRIBUTE_145=The provided task entry does not contain attribute %s which is needed to specify the fully-qualified name of the class providing the task logic
|
SEVERE_ERR_TASKSCHED_MULTIPLE_CLASS_TYPES_146=The provided task entry contains multiple attributes with type %s, which is used to hold the task class name, but only a single instance is allowed
|
SEVERE_ERR_TASKSCHED_NO_CLASS_VALUES_147=The provided task entry does not contain any values for the %s attribute, which is used to specify the fully-qualified name of the class providing the task logic
|
SEVERE_ERR_TASKSCHED_MULTIPLE_CLASS_VALUES_148=The provided task entry contains multiple values for the %s attribute, which is used to specify the task class name, but only a single value is allowed
|
SEVERE_ERR_TASKSCHED_CANNOT_LOAD_CLASS_149=An error occurred while attempting to load class %s specified in attribute %s of the provided task entry: %s. Does this class exist in the Directory Server classpath?
|
SEVERE_ERR_TASKSCHED_CANNOT_INSTANTIATE_CLASS_AS_TASK_150=An error occurred while trying to create an instance of class %s as a Directory Server task. Is this class a subclass of %s?
|
SEVERE_ERR_TASKSCHED_CANNOT_INITIALIZE_INTERNAL_151=An error occurred while attempting to perform internal initialization on an instance of class %s with the information contained in the provided entry: %s
|
SEVERE_WARN_TASKSCHED_CANNOT_RENAME_CURRENT_BACKING_FILE_152=An error occurred while attempting to rename the current tasks backing file from %s to %s: %s. The previous task configuration (which does not reflect the latest update) may be lost
|
SEVERE_ERR_TASKSCHED_CANNOT_RENAME_NEW_BACKING_FILE_153=An error occurred while attempting to rename the new tasks backing file from %s to %s: %s. If the Directory Server is restarted, then the task scheduler may not be able to
|
SEVERE_ERR_TASKSCHED_CANNOT_WRITE_BACKING_FILE_154=An error occurred while attempting to write the new tasks data backing file %s: %s. Configuration information reflecting the latest update may be lost
|
SEVERE_ERR_TASKBE_IMPORT_NOT_SUPPORTED_155=The task backend does not support LDIF import operations
|
INFO_TASKBE_INTERRUPTED_BY_SHUTDOWN_156=Le backend des t\u00e2ches est en cours de cl\u00f4ture
|
INFO_ROOTDSE_DESCRIPTION_SHOW_ALL_ATTRIBUTES_157=Indique si tous les attributs dans le DSE racine doivent \u00eatre trait\u00e9s comme des attributs d'utilisateurs (et par cons\u00e9quent retourn\u00e9s aux clients par d\u00e9faut), quelle que soit la configuration du sch\u00e9ma de Directory Server
|
SEVERE_ERR_ROOTDSE_CANNOT_DETERMINE_ALL_USER_ATTRIBUTES_158=An error occurred while trying to determine the value of the %s configuration attribute, which controls whether to treat all root DSE attributes like user attributes: %s. The attributes in the root DSE will be treated based on their definition in the server schema
|
INFO_ROOTDSE_UPDATED_SHOW_ALL_ATTRS_159=La configuration du DSE racine a \u00e9t\u00e9 mise \u00e0 jour afin que l'attribut de configuration %s utilise d\u00e9sormais une valeur de %s
|
SEVERE_ERR_TASKSCHED_REMOVE_RECURRING_EXISTING_ITERATION_160=Unable to remove recurring task %s because there is already a scheduled iteration of that task with ID %s that must be removed first
|
SEVERE_ERR_TASKSCHED_REMOVE_PENDING_NO_SUCH_TASK_161=Unable to remove pending task %s because no such task exists
|
SEVERE_ERR_TASKSCHED_REMOVE_PENDING_NOT_PENDING_162=Unable to remove pending task %s because the task is no longer pending
|
SEVERE_ERR_TASKSCHED_REMOVE_COMPLETED_NO_SUCH_TASK_163=Unable to remove completed task %s because no such task exists in the list of completed tasks
|
SEVERE_ERR_TASKBE_DELETE_INVALID_ENTRY_164=Unable to remove entry %s from the task backend because its DN is either not appropriate for that backend or it is not below the scheduled or recurring tasks base entry
|
SEVERE_ERR_TASKBE_DELETE_NO_SUCH_TASK_165=Unable to remove entry %s from the task backend because there is no scheduled task associated with that entry DN
|
SEVERE_ERR_TASKBE_DELETE_RUNNING_166=Unable to delete entry %s from the task backend because the associated task is currently running
|
SEVERE_ERR_TASKBE_DELETE_NO_SUCH_RECURRING_TASK_167=Unable to remove entry %s from the task backend because there is no recurring task associated with that entry DN
|
SEVERE_ERR_TASKBE_SEARCH_INVALID_BASE_168=Unable to process the search operation in the task backend because the provided base DN %s is not valid for entries in the task backend
|
SEVERE_ERR_TASKBE_SEARCH_NO_SUCH_TASK_169=Unable to process the search operation in the task backend because there is no scheduled task associated with the provided search base entry %s
|
SEVERE_ERR_TASKBE_SEARCH_NO_SUCH_RECURRING_TASK_170=Unable to process the search operation in the task backend because there is no recurring task associated with the provided search base entry %s
|
SEVERE_ERR_BACKUP_CONFIG_ENTRY_NULL_171=Unable to initialize the backup backend because the provided configuration entry is null
|
SEVERE_ERR_BACKUP_CANNOT_DECODE_BACKUP_ROOT_DN_172=Unable to initialize the backup backend because an error occurred while attempting to decode the base DN for the backend: %s
|
INFO_BACKUP_DESCRIPTION_BACKUP_DIR_LIST_173=Ensemble de r\u00e9pertoires auxquels les op\u00e9rations de recherche acc\u00e8deront par d\u00e9faut dans le backend de sauvegarde. L'acc\u00e8s aux r\u00e9pertoires de sauvegarde ne figurant pas dans cette liste sera encore possible en sp\u00e9cifiant directement le r\u00e9pertoire de sauvegarde dans le DN de base de recherche. Les modifications apport\u00e9es \u00e0 cet attribut de configuration prendront effet imm\u00e9diatement
|
SEVERE_ERR_BACKUP_CANNOT_DETERMINE_BACKUP_DIR_LIST_174=An error occurred while attempting to determine the backup directory list: %s. Initialization of the backup backend cannot continue
|
SEVERE_ERR_BACKUP_GET_ENTRY_NULL_175=Unable to retrieve an entry from the backup backend because the requested entry was null
|
SEVERE_ERR_BACKUP_INVALID_BASE_176=Requested entry %s does not exist in the backup backend
|
SEVERE_ERR_BACKUP_DN_DOES_NOT_SPECIFY_DIRECTORY_177=Unable to retrieve entry %s from the backup backend because the requested DN is one level below the base DN but does not specify a backup directory
|
SEVERE_ERR_BACKUP_INVALID_BACKUP_DIRECTORY_178=Unable to retrieve entry %s from the backup backend because the requested backup directory is invalid: %s
|
SEVERE_ERR_BACKUP_ERROR_GETTING_BACKUP_DIRECTORY_179=An error occurred while attempting to examine the requested backup directory: %s
|
SEVERE_ERR_BACKUP_NO_BACKUP_ID_IN_DN_180=Unable to retrieve entry %s from the backup backend because the requested DN is two levels below the base DN but does not specify a backup ID
|
SEVERE_ERR_BACKUP_NO_BACKUP_PARENT_DN_181=Unable to retrieve entry %s from the backup backend because it does not have a parent
|
SEVERE_ERR_BACKUP_NO_BACKUP_DIR_IN_DN_182=Unable to retrieve entry %s from the backup backend because the DN does not contain the backup directory in which the requested backup should reside
|
SEVERE_ERR_BACKUP_NO_SUCH_BACKUP_183=Backup %s does not exist in backup directory %s
|
SEVERE_ERR_BACKUP_ADD_NOT_SUPPORTED_184=Add operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_DELETE_NOT_SUPPORTED_185=Delete operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_MODIFY_NOT_SUPPORTED_186=Modify operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_MODIFY_DN_NOT_SUPPORTED_187=Modify DN operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_NO_SUCH_ENTRY_188=The requested entry %s does not exist in the backup backend
|
SEVERE_ERR_BACKUP_EXPORT_NOT_SUPPORTED_189=LDIF export operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_IMPORT_NOT_SUPPORTED_190=LDIF import operations are not supported in the backup backend
|
SEVERE_ERR_BACKUP_BACKUP_AND_RESTORE_NOT_SUPPORTED_191=Backup and restore operations are not supported in the backup backend
|
SEVERE_ERR_MEMORYBACKEND_REQUIRE_EXACTLY_ONE_BASE_192=Exactly one base DN must be provided for use with the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_ENTRY_ALREADY_EXISTS_193=Entry %s already exists in the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_ENTRY_DOESNT_BELONG_194=Entry %s does not belong in the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_PARENT_DOESNT_EXIST_195=Unable to add entry %s because its parent entry %s does not exist in the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_ENTRY_DOESNT_EXIST_196=Entry %s does not exist in the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_DELETE_ENTRY_WITH_CHILDREN_197=Cannot delete entry %s because it has one or more subordinate entries
|
SEVERE_ERR_MEMORYBACKEND_MODDN_NOT_SUPPORTED_198=Modify DN operations are not supported in the memory-based backend
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_WRITER_199=Unable to create an LDIF writer: %s
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_WRITE_ENTRY_TO_LDIF_200=Cannot write entry %s to LDIF: %s
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_CREATE_LDIF_READER_201=Unable to create an LDIF reader: %s
|
SEVERE_ERR_MEMORYBACKEND_ERROR_READING_LDIF_202=An unrecoverable error occurred while reading from LDIF: %s
|
SEVERE_ERR_MEMORYBACKEND_ERROR_DURING_IMPORT_203=An unexpected error occurred while processing the import: %s
|
SEVERE_ERR_MEMORYBACKEND_BACKUP_RESTORE_NOT_SUPPORTED_204=The memory-based backend does not support backup or restore operations
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_RENAME_ENRY_WITH_CHILDREN_205=Cannot rename entry %s because it has one or more subordinate entries
|
SEVERE_ERR_MEMORYBACKEND_CANNOT_RENAME_TO_ANOTHER_BACKEND_206=Cannot rename entry %s because the target entry is in a different backend
|
SEVERE_ERR_MEMORYBACKEND_RENAME_PARENT_DOESNT_EXIST_207=Cannot rename entry %s because the new parent entry %s doesn't exist
|
INFO_SCHEMA_DESCRIPTION_SHOW_ALL_ATTRIBUTES_208=Indique si les atttributs dans l'entr\u00e9e de sous-sch\u00e9ma doivent \u00eatre trait\u00e9s comme des attributs d'utilisateur m\u00eame s'ils sont marqu\u00e9s comme op\u00e9rationnels. Ceci peut fournir une compatibilit\u00e9 avec des applications qui requi\u00e8rent que des attributs de sch\u00e9ma comme attributeType et objectClasses soient inclus par d\u00e9faut m\u00eame s'ils ne sont pas n\u00e9cessaires. Remarquez que l'attribut ldapSyntaxes sera toujours consid\u00e9r\u00e9 comme op\u00e9rationnel, afin d'\u00e9viter des probl\u00e8mes lors des tentatives de modifications du sch\u00e9ma sur le protocole.
|
SEVERE_ERR_SCHEMA_CANNOT_DETERMINE_SHOW_ALL_209=An error occurred while trying to determine whether to treat all subschema entry attributes as user attributes regardless of the way they are defined in the schema, as specified in the ds-cfg-show-all-attributes attribute of configuration entry %s: %s. The default behavior, which is to treat the attribute types as defined in the server schema, will be used
|
FATAL_ERR_BACKEND_CANNOT_REGISTER_BASEDN_210=An error occurred while attempting to register base DN %s in the Directory Server: %s
|
MILD_ERR_SCHEMA_DELETE_MODTYPE_NOT_SUPPORTED_211=Le backend de sch\u00e9ma ne prend actuellement pas en charge la suppression des \u00e9l\u00e9ments de sch\u00e9ma existants
|
MILD_ERR_SCHEMA_INVALID_MODIFICATION_TYPE_212=Le backend de sch\u00e9ma ne prend actuellement pas en charge le type de modification %s
|
MILD_ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPE_213=Le backend de sch\u00e9ma ne prend actuellement pas en charge la modification de ce type d'attribut %s Seules les utilisations des types d'attributs, des classes d'objet, des formulaires de noms, des r\u00e8gles de contenu DIT, des r\u00e8gles de structure DIT et des r\u00e8gles de correspondance peuvent \u00eatre modifi\u00e9es
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_ATTRTYPE_214=Une erreur s'est produite lors de la tentative de d\u00e9codage du type d'attribut "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_ATTRTYPE_ALREADY_EXISTS_215=Impossible d'ajouter un type d'attribut %s au sch\u00e9ma de serveur car il existe un type d'attribut avec un nom ou un OID\u00a0incompatible : %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_OBJECTCLASS_216=Une erreur s'est produite lors lors de la tentative de d\u00e9codage de la classe d'objet "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_OBJECTCLASS_217=Impossible d'ajouter une classe d'objet %s car sa classe sup\u00e9rieure de %s n'est pas d\u00e9finie dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OC_UNDEFINED_REQUIRED_ATTR_218=Impossible d'ajouter une classe d'objet %s car elle n\u00e9cessite un attribut %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OC_UNDEFINED_OPTIONAL_ATTR_219=Impossible d'ajouter une classe d'objet %s car elle autorise un attribut %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OBJECTCLASS_ALREADY_EXISTS_220=Impossible d'ajouter une classe d'objet %s au sch\u00e9ma de serveur car il existe une classe d'objet avec avec un nom ou un OID\u00a0incompatible : %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_READ_EXISTING_USER_SCHEMA_221=Une erreur s'est produite lors de la tentative de lecture du contenu du fichier de sch\u00e9ma %s\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA_222=Une erreur s'est produite lors de la tentative d'\u00e9criture du sch\u00e9ma mis \u00e0 jour\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_NAME_FORM_223=Une erreur s'est produite lors de la tentative de d\u00e9codage du formulaire de nom "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_DCR_224=Une erreur s'est produite lors de la tentative de d\u00e9codage de la r\u00e8gle de contenu DIT "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_DSR_225=Une erreur s'est produite lors de la tentative de d\u00e9codage de la r\u00e8gle de structure DIT "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_MR_USE_226=Une erreur s'est produite lors de la tentative de d\u00e9codage de l'utilisation de la r\u00e8gle de correspondance "%s"\u00a0: %s
|
MILD_ERR_SCHEMA_MODIFY_DELETE_NO_VALUES_227=Le serveur n'autorisera pas la suppression de toutes les valeurs pour le type d'attribut %s dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_ATTRTYPE_228=Impossible d'ajouter un type d'attribut %s car il entre en conflit avec plusieurs types d'attributs existants (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_ATTRIBUTE_TYPE_229=Impossible d'ajouter un type d'attribut %s car il fait r\u00e9f\u00e9rence \u00e0 un type d'attribut sup\u00e9rieur %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_OBJECTCLASS_230=Impossible d'ajouter une classe d'objet %s car elle entre en conflit avec plusieurs classes d'objets existantes (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_NAME_FORM_231=Impossible d'ajouter un formulaire de nom %s car il entre en conflit avec plusieurs formulaires de noms existants (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_STRUCTURAL_OC_232=Impossible d'ajouter un formulaire de nom %s car il fait r\u00e9f\u00e9rence \u00e0 une classe d'objet structurelle %s qui n'est pas d\u00e9finie dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_REQUIRED_ATTR_233=Impossible d'ajouter un formulaire de nom %s car il fait r\u00e9f\u00e9rence \u00e0 un type d'attribut requis %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_OPTIONAL_ATTR_234=Impossible d'ajouter un formulaire de nom %s car il fait r\u00e9f\u00e9rence \u00e0 un type d'attribut facultatif %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DCR_235=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle entre en conflit avec des r\u00e8gles de contenus DIT existantes (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_DCR_236=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet structurelle %s, qui est d\u00e9j\u00e0 associ\u00e9e \u00e0 une autre r\u00e8gle de contenu DIT %s
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_STRUCTURAL_OC_237=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet structurelle %s qui n'est pas d\u00e9finie dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_AUXILIARY_OC_238=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet auxiliaire %s qui n'est pas d\u00e9finie dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_REQUIRED_ATTR_239=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 un type d'attribut requis %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_OPTIONAL_ATTR_240=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 un type d'attribut facultatif %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_PROHIBITED_ATTR_241=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 un type d'attribut interdit %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DSR_242=Impossible d'ajouter une r\u00e8gle de structure DIT %s car elle entre en conflit avec plusieurs r\u00e8gles de structures DIT existantes (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_NAME_FORM_CONFLICT_FOR_ADD_DSR_243=Impossible d'ajouter une r\u00e8gle de structure DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 un formulaire de nom %s, qui est d\u00e9j\u00e0 associ\u00e9 \u00e0 une autre r\u00e8gle de structure DIT %s
|
MILD_ERR_SCHEMA_MODIFY_DSR_UNDEFINED_NAME_FORM_244=Impossible d'ajouter une r\u00e8gle de structure DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 un formulaire de nom %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_MR_USE_245=Impossible d'ajouter une utilisation de r\u00e8gle de correspondance %s car elle entre en conflit avec plusieurs utilisations de r\u00e8gles de correspondance (%s et %s)
|
MILD_ERR_SCHEMA_MODIFY_MR_CONFLICT_FOR_ADD_MR_USE_246=Impossible d'ajouter une utilisation de r\u00e8gle de correspondance %s car elle fait r\u00e9f\u00e9rence \u00e0 une r\u00e8gle de correspondance %s d\u00e9j\u00e0 associ\u00e9e \u00e0 une autre utilisation de r\u00e8gles de correspondance %s
|
MILD_ERR_SCHEMA_MODIFY_MRU_UNDEFINED_ATTR_247=Impossible d'ajouter une utilisation de r\u00e8gle de correspondance %s car elle fait r\u00e9f\u00e9rence \u00e0 un type d'attribut %s qui n'est pas d\u00e9fini dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_AT_248=R\u00e9ference circulaire d\u00e9tect\u00e9e pour un type d'attribut %s dans lequel la cha\u00eene de type sup\u00e9rieur fait r\u00e9f\u00e9rence au type d'attribut lui-m\u00eame
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_OC_249=R\u00e9ference circulaire d\u00e9tect\u00e9e pour une classe d'objet %s dans laquelle la cha\u00eene de type sup\u00e9rieur fait r\u00e9f\u00e9rence \u00e0 la classe d'objet elle-m\u00eame
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_DSR_250=R\u00e9ference circulaire d\u00e9tect\u00e9e pour une r\u00e8gle de structure DIT %s dans lequel la cha\u00eene de type sup\u00e9rieur fait r\u00e9f\u00e9rence \u00e0 la r\u00e8gle de structure DIT elle-m\u00eame
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_CLEANED_251=Une erreur s'est produite lors de la tentative de cr\u00e9ation de copies des fichiers de sch\u00e9ma existants avant d'appliquer les mises \u00e0 jour\u00a0: %s. Le serveur a pu restaurer la configuration de sch\u00e9ma d'origine et aucun nettoyage suppl\u00e9mentaire ne sera donc n\u00e9cessaire
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_NOT_CLEANED_252=Une erreur s'est produite lors de la tentative de cr\u00e9ation de copies des fichiers de sch\u00e9ma existants avant d'appliquer les mises \u00e0 jour\u00a0: %s. Un probl\u00e8me s'est \u00e9galement produit lors de la tentative de restauration de la configuration de sch\u00e9ma d'origine et le serveur peut se trouver dans un \u00e9tat incoh\u00e9rent et n\u00e9cessiter un nettoyage manuel
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_RESTORED_253=Une erreur s'est produite lors de la tentative d'\u00e9criture de nouvelles versions des fichiers de sch\u00e9ma existants\u00a0: %s. Le serveur a pu restaurer la configuration de sch\u00e9ma d'origine et aucun nettoyage suppl\u00e9mentaire ne sera donc n\u00e9cessaire
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTORED_254=Une erreur s'est produite lors de la tentative d'\u00e9criture de nouvelles versions des fichiers de sch\u00e9ma existants\u00a0: %s. Un probl\u00e8me s'est \u00e9galement produit lors de la tentative de restauration de la configuration de sch\u00e9ma d'origine et le serveur peut se trouver dans un \u00e9tat incoh\u00e9rent et n\u00e9cessiter un nettoyage manuel
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPE_255=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car aucun type d'attribut de ce genre n'a \u00e9t\u00e9 d\u00e9fini
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_SUPERIOR_TYPE_256=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 en tant que type sup\u00e9rieur pour un type d'attribut %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_OC_257=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 en tant que type d'attribut requis ou facultatif dans une classe d'objet %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_NF_258=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 en tant que type d'attribut requis ou facultatif dans un formulaire de nom %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_DCR_259=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 en tant que type d'attribut requis, facultatif ou interdit dans une r\u00e8gle de contenu DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_MR_USE_260=Impossible de supprimer un type d'attribut %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 par une utilisation de r\u00e8gle de correspondance %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASS_261=Impossible de supprimer une classe d'objet %s du sch\u00e9ma de serveur car aucune classe d'objet de ce type n'a \u00e9t\u00e9 d\u00e9finie
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_SUPERIOR_CLASS_262=Impossible de supprimer une classe d'objet %s du sch\u00e9ma de serveur car elle est r\u00e9f\u00e9renc\u00e9e en tant que type sup\u00e9rieur pour une classe d'objet %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_IN_NF_263=Impossible de supprimer une classe d'objet %s du sch\u00e9ma de serveur car elle est r\u00e9f\u00e9renc\u00e9e en tant que classe structurelle pour un formulaire de nom %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_IN_DCR_264=Impossible de supprimer une classe d'objet %s du sch\u00e9ma de serveur car elle est r\u00e9f\u00e9renc\u00e9e en tant que classe structurelle ou structurelle pour une r\u00e8gle de contenu DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_NAME_FORM_265=Impossible de supprimer un formulaire de nom %s du sch\u00e9ma de serveur car aucun formulaire de nom de ce type n'a \u00e9t\u00e9 d\u00e9fini
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NF_IN_DSR_266=Impossible de supprimer un formulaire de nom %s du sch\u00e9ma de serveur car il est r\u00e9f\u00e9renc\u00e9 par une r\u00e8gle de structure DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DCR_267=Impossibler de supprimer une r\u00e8gle de contenu DIT %s du sch\u00e9ma de serveur car aucune r\u00e8gle de contenu de ce type n'a \u00e9t\u00e9 d\u00e9finie
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DSR_268=Impossibler de supprimer une r\u00e8gle de structure DIT %s du sch\u00e9ma de serveur car aucune r\u00e8gle de structure de ce type n'a \u00e9t\u00e9 d\u00e9finie
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_DSR_SUPERIOR_RULE_269=Impossibler de supprimer une r\u00e8gle de structure DIT %s du sch\u00e9ma de serveur car elle est r\u00e9f\u00e9renc\u00e9e en tant que r\u00e8gle sup\u00e9rieure pour une r\u00e8gle de structure %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_MR_USE_270=Impossibler de supprimer une utilisation de r\u00e8gle de correspondance %s du sch\u00e9ma de serveur car aucune une utilisation de r\u00e8gle de correspondance de ce type n'a \u00e9t\u00e9 d\u00e9finie
|
MILD_ERR_SCHEMA_MODIFY_NF_OC_NOT_STRUCTURAL_271=Impossible d'ajouter un formulaire de nom % car il fait r\u00e9f\u00e9rence \u00e0 une classe d'objet qui est d\u00e9finie sur le sch\u00e9ma de serveur mais n'est pas une classe d'objet structurelle
|
MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_STRUCTURAL_272=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet structurelle %s qui est d\u00e9finie dans le sch\u00e9ma de serveur mais n'est pas structurelle
|
MILD_ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_NF_273=Impossible d'ajouter un formulaire de nom %s car il fait r\u00e9f\u00e9rence \u00e0 une classe d'objet structurelle %s qui est d\u00e9j\u00e0 associ\u00e9e \u00e0 un autre formulaire de nom %s
|
MILD_ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_ATTRIBUTE_TYPE_274=Impossible d'ajouter un type d'attribut %s car le type sup\u00e9rieur %s est marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_ATTRTYPE_OBSOLETE_MR_275=Impossible d'ajouter un type d'attribut %s car la r\u00e8gle de correspondance associ\u00e9e %s est marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_OBJECTCLASS_276=Impossible d'ajouter une classe d'objet %s car la classe sup\u00e9rieure %s est marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OC_OBSOLETE_REQUIRED_ATTR_277=Impossible d'ajouter une classe d'objet %s car l'attribut requis %s est marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_OC_OBSOLETE_OPTIONAL_ATTR_278=Impossible d'ajouter une classe d'objet %s car l'attribut facultatif %s est marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_NF_OC_OBSOLETE_279=Impossible d'ajouter un formulaire de nom %s car sa classe d'objet structurelle %s est marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_NF_OBSOLETE_REQUIRED_ATTR_280=Impossible d'ajouter un formulaire de nom %s car il n\u00e9cessite un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_NF_OBSOLETE_OPTIONAL_ATTR_281=Impossible d'ajouter un formulaire de nom %s car il autorise un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_STRUCTURAL_OC_OBSOLETE_282=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car sa classe d'objet structurelle %s est marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_AUXILIARY_283=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet auxiliaire %s qui est d\u00e9finie dans le sch\u00e9ma de serveur mais n'est pas une classe auxiliaire
|
MILD_ERR_SCHEMA_MODIFY_DCR_AUXILIARY_OC_OBSOLETE_284=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle autorise une classe d'objet auxiliaire %s marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_REQUIRED_ATTR_285=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle n\u00e9cessite un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_OPTIONAL_ATTR_286=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle autorise un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_PROHIBITED_ATTR_287=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle interdit un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_NAME_FORM_288=Impossible d'ajouter une r\u00e8gle de structure DIT %s car son formulaire de nom %s est marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_SUPERIOR_RULE_289=Impossible d'ajouter une r\u00e8gle de structure DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une r\u00e8gle sup\u00e9rieure %s marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MRU_OBSOLETE_MR_290=Impossible d'ajouter une utilisation de r\u00e8gle de correspondance %s car sa r\u00e8gle de correspondance %s est marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_MRU_OBSOLETE_ATTR_291=Impossible d'ajouter une utilisation de r\u00e8gle de correspondance %s car elle fait r\u00e9f\u00e9rence \u00e0 un type d'attribut %s marqu\u00e9 comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_AUXILIARY_OC_292=Impossible d'ajouter une r\u00e8gle de contenu DIT %s car elle fait r\u00e9f\u00e9rence \u00e0 une classe d'objet auxiliaire %s marqu\u00e9e comme OBSOLETE dans le sch\u00e9ma de serveur
|
MILD_ERR_SCHEMA_MODIFY_INSUFFICIENT_PRIVILEGES_293=Vous ne disposez pas de privil\u00e8ges suffisants pour modifier le sch\u00e9ma de Directory Server
|
SEVERE_ERR_SCHEMA_CANNOT_FIND_CONCAT_FILE_294=Unable to find a file containing concatenated schema element definitions in order to determine if any schema changes were made with the server offline. The file was expected in the %s directory and should have been named either %s or %s
|
SEVERE_ERR_SCHEMA_ERROR_DETERMINING_SCHEMA_CHANGES_295=An error occurred while attempting to determine whether any schema changes had been made by directly editing the schema files with the server offline: %s
|
SEVERE_ERR_SCHEMA_CANNOT_WRITE_CONCAT_SCHEMA_FILE_296=An error occurred while attempting to write file %s containing a concatenated list of all server schema elements: %s. The server may not be able to accurately identify any schema changes made with the server offline
|
NOTICE_BACKEND_ENVIRONMENT_UNUSABLE_297=L'environnement de bases de donn\u00e9es JE correspondant \u00e0 l 'id de backend %s est corrompu Red\u00e9marrez Directory Server pour rouvrir l'environnement
|
SEVERE_ERR_TASKSCHED_NOT_ALLOWED_TASK_298=The Directory Server is not configured to allow task %s to be invoked
|
INFO_TASK_COMPLETION_BODY_299=ID de t\u00e2che\u00a0: %s\r\n\u00c9tat de la t\u00e2che: %s\r\nHeure de d\u00e9but planifi\u00e9e\u00a0: %s\r\nHeure de d\u00e9but r\u00e9elle\u00a0: %s\r\nHeure d'ach\u00e8vement\u00a0: %s\r\n\r\nMessages du fichier journal\u00a0:\r\n
|
SEVERE_ERR_TRUSTSTORE_GET_ENTRY_NULL_300=Unable to retrieve an entry from the trust store backend because the requested entry was null
|
SEVERE_ERR_TRUSTSTORE_INVALID_BASE_301=Requested entry %s does not exist in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_DN_DOES_NOT_SPECIFY_CERTIFICATE_302=Unable to process entry %s in the trust store backend because the requested DN is one level below the base DN but does not specify a certificate name
|
SEVERE_ERR_TRUSTSTORE_CANNOT_RETRIEVE_CERT_303=Error while trying to retrieve certificate %s from the trust store file %s: %s
|
SEVERE_ERR_TRUSTSTORE_MODIFY_NOT_SUPPORTED_304=Modify operations are not supported in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_MODIFY_DN_NOT_SUPPORTED_305=Modify DN operations are not supported in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_REQUIRES_ONE_BASE_DN_306=Unable to initialize the trust store backend from configuration entry %s because it does not contain exactly one base DN
|
SEVERE_ERR_TRUSTSTORE_IMPORT_AND_EXPORT_NOT_SUPPORTED_307=LDIF import and export operations are not supported in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_BACKUP_AND_RESTORE_NOT_SUPPORTED_308=Backup and restore operations are not supported in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_NO_SUCH_FILE_309=The trust store file %s specified in attribute ds-cfg-trust-store-file of configuration entry %s does not exist
|
SEVERE_ERR_TRUSTSTORE_INVALID_TYPE_310=The trust store type %s specified in attribute ds-cfg-trust-store-type of configuration entry %s is not valid: %s
|
SEVERE_ERR_TRUSTSTORE_PIN_FILE_CANNOT_CREATE_311=An error occurred while trying to create the PIN file %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s
|
SEVERE_ERR_TRUSTSTORE_PIN_FILE_CANNOT_READ_312=An error occurred while trying to read the trust store PIN from file %s specified in configuration attribute ds-cfg-trust-store-pin-file of configuration entry %s: %s
|
SEVERE_ERR_TRUSTSTORE_PIN_FILE_EMPTY_313=File %s specified in attribute ds-cfg-trust-store-pin-file of configuration entry %s should contain the PIN needed to access the trust store, but this file is empty
|
SEVERE_ERR_TRUSTSTORE_PIN_ENVAR_NOT_SET_314=Environment variable %s which is specified in attribute ds-cfg-trust-store-pin-environment-variable of configuration entry %s should contain the PIN needed to access the trust store, but this property is not set
|
SEVERE_ERR_TRUSTSTORE_PIN_PROPERTY_NOT_SET_315=Java property %s which is specified in attribute ds-cfg-trust-store-pin-property of configuration entry %s should contain the PIN needed to access the file-based trust manager, but this property is not set
|
SEVERE_ERR_TRUSTSTORE_CANNOT_DETERMINE_FILE_316=An unexpected error occurred while trying to determine the value of configuration attribute ds-cfg-trust-store-file in configuration entry %s: %s
|
SEVERE_ERR_TRUSTSTORE_CANNOT_LOAD_317=An error occurred while trying to load the trust store contents from file %s: %s
|
SEVERE_ERR_TRUSTSTORE_CANNOT_CREATE_FACTORY_318=An error occurred while trying to create a trust manager factory to access the contents of trust store file %s: %s
|
SEVERE_ERR_TRUSTSTORE_ALIAS_IN_USE_319=The certificate entry %s already exists
|
SEVERE_ERR_TRUSTSTORE_CANNOT_GENERATE_CERT_320=Error while attempting to generate a self-signed certificate %s in the trust store file %s: %s
|
SEVERE_ERR_TRUSTSTORE_CANNOT_ADD_CERT_321=Error while trying to add certificate %s to the trust store file %s: %s
|
SEVERE_ERR_TRUSTSTORE_DELETE_NOT_SUPPORTED_322=Delete operations are not supported in the trust store backend
|
SEVERE_ERR_TRUSTSTORE_ENTRY_MISSING_CERT_ATTR_323=The entry %s could not be added because it does not contain a certificate attribute %s
|
SEVERE_ERR_TRUSTSTORE_ENTRY_HAS_MULTIPLE_CERT_ATTRS_324=The entry %s could not be added because it contains multiple certificate attributes %s
|
SEVERE_ERR_TRUSTSTORE_ENTRY_MISSING_CERT_VALUE_325=The entry %s could not be added because it does not contain a value of certificate attribute %s
|
SEVERE_ERR_TRUSTSTORE_ENTRY_HAS_MULTIPLE_CERT_VALUES_326=The entry %s could not be added because it contains multiple values of certificate attribute %s
|
SEVERE_ERR_TRUSTSTORE_CANNOT_WRITE_CERT_327=Error while writing certificate %s to a file: %s
|
SEVERE_WARN_TRUSTSTORE_SET_PERMISSIONS_FAILED_328=Failed to set permissions on trust store file %s
|
SEVERE_ERR_ROOT_CONTAINER_NOT_INITIALIZED_329=The root container for backend %s has not been initialized preventing this backend from processing the requested operation
|
SEVERE_ERR_TASKBE_MODIFY_CANNOT_LOCK_ENTRY_330=Unable to obtain a write lock on entry %s
|
SEVERE_ERR_TASKBE_MODIFY_INVALID_ENTRY_331=Entry %s cannot be modified because it does not represent a task entry. Only task entries may be modified in the task backend
|
SEVERE_ERR_TASKBE_MODIFY_NO_SUCH_TASK_332=Entry %s cannot be modified because it does not represent a valid task in the server
|
SEVERE_ERR_TASKBE_MODIFY_COMPLETED_333=Entry %s cannot be modified because the assoicated task has completed running. Completed tasks cannot be modified
|
SEVERE_ERR_TASKBE_MODIFY_RECURRING_334=Entry %s cannot be modified because the server does not currently support modifying recurring task entries
|
SEVERE_ERR_TASKBE_MODIFY_RUNNING_335=The task associated with entry %s is currently running. The only modification allowed for running tasks is to replace the value of the ds-task-state attribute with "cancel"
|
INFO_TASKBE_RUNNING_TASK_CANCELLED_336=Le traitement de la t\u00e2che a \u00e9t\u00e9 interrompu par une requ\u00eate de modification destin\u00e9e \u00e0 annuler la t\u00e2che
|
SEVERE_ERR_TRUSTSTORE_CANNOT_DELETE_CERT_337=Error while trying to delete certificate %s from the trust store file %s: %s
|
SEVERE_ERR_TRUSTSTORE_CERTIFICATE_NOT_FOUND_338=Unable to retrieve entry %s from the trust store backend because the certificate %s does not exist
|
SEVERE_ERR_LDIF_BACKEND_MULTIPLE_BASE_DNS_339=The LDIF backend defined in configuration entry %s only supports a single base DN, but was configured for use with multiple base DNs
|
SEVERE_ERR_LDIF_BACKEND_ERROR_OPENING_FILE_340=An error occurred while attempting to open LDIF file %s for use by the LDIF backend defined in configuration entry %s: %s
|
SEVERE_ERR_LDIF_BACKEND_ERROR_READING_ENTRY_341=An error occurred while attempting to read data from LDIF file %s into the LDIF backend defined in configuration entry %s: %s
|
MILD_ERR_LDIF_BACKEND_DUPLICATE_ENTRY_342=Le fichier LDIF %s configur\u00e9 pour \u00eatre utilis\u00e9 avec le backend de LDIF d\u00e9fini dans l'entr\u00e9e de configuration %s a plusieurs entr\u00e9es avec un DN de %s
|
MILD_ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPE_343=Le fichier LDIF %s configur\u00e9 pour \u00eatre utilis\u00e9 avec le backend de LDIF d\u00e9fini dans l'entr\u00e9e de configuration %s inclut une entr\u00e9e %s qui n'est pas sous le DN de base d\u00e9fini pour ce backend
|
MILD_ERR_LDIF_BACKEND_MISSING_PARENT_344=Le fichier LDIF %s configur\u00e9 pour \u00eatre utilis\u00e9 avec le backend de LDIF d\u00e9fini dans l'entr\u00e9e de configuration %s inclut une entr\u00e9e %s mais son entr\u00e9e parent n'a pas encore \u00e9t\u00e9 lue
|
SEVERE_ERR_LDIF_BACKEND_ERROR_CREATING_FILE_345=An error occurred while trying to create file %s to write an updated version of the data for the LDIF backend defined in configuration entry %s: %s
|
SEVERE_ERR_LDIF_BACKEND_ERROR_WRITING_FILE_346=An error occurred while trying to write updated data to file %s for the LDIF backend defined in configuration entry %s: %s
|
SEVERE_ERR_LDIF_BACKEND_ERROR_RENAMING_FILE_347=An error occurred while attempting to rename file %s to %s while writing updated data for the LDIF backend defined in configuration entry %s: %s
|
MILD_ERR_LDIF_BACKEND_ADD_ALREADY_EXISTS_348=L'entr\u00e9e %s existe d\u00e9j\u00e0 dans la m\u00e9moire bas\u00e9e sur le backend de LDIF
|
MILD_ERR_LDIF_BACKEND_ADD_MISSING_PARENT_349=Le parent de l'entr\u00e9e %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_DELETE_NO_SUCH_ENTRY_350=L'entr\u00e9e %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_DELETE_NONLEAF_351=L'entr\u00e9e %s a une ou plusieurs entr\u00e9es subordonn\u00e9es et ne peut \u00eatre supprim\u00e9e tant que celles-ci n'ont pas \u00e9t\u00e9 supprim\u00e9es
|
MILD_ERR_LDIF_BACKEND_MODIFY_NO_SUCH_ENTRY_352=L'entr\u00e9e %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_MODDN_NO_SUCH_SOURCE_ENTRY_353=L'entr\u00e9e source %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTS_354=L'entr\u00e9e cible %s existe d\u00e9j\u00e0
|
MILD_ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXIST_355=Le nouveau DN parent %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_SEARCH_NO_SUCH_BASE_356=L'entr\u00e9e %s sp\u00e9cifi\u00e9e comme DN de base de recherche n'existe pas
|
SEVERE_ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_WRITER_357=An error occurred while trying to create the writer for the LDIF export operation: %s
|
SEVERE_ERR_LDIF_BACKEND_CANNOT_WRITE_ENTRY_TO_LDIF_358=An error occurred while trying to write entry %s during the LDIF export: %s
|
SEVERE_ERR_LDIF_BACKEND_CANNOT_CREATE_LDIF_READER_359=An error occurred while trying to create the reader for the LDIF import operation: %s
|
SEVERE_ERR_LDIF_BACKEND_ERROR_READING_LDIF_360=An unrecoverable error occurred while attempting to read data from the import file: %s. The LDIF import cannot continue
|
MILD_ERR_LDIF_BACKEND_BACKUP_RESTORE_NOT_SUPPORTED_361=Le backend de LDIF ne fournit pas actuellement de m\u00e9canisme de sauvegarde ou de restauration Utilisez plut\u00f4t les op\u00e9rations d'importation et exportation de LDIF
|
MILD_ERR_LDIF_BACKEND_LDIF_DOESNT_EXIST_362=Le fichier LDIF %s r\u00e9f\u00e9renc\u00e9 dans la configuration de l'entr\u00e9e de configuration du backend de LDIF %s n'existe pas
|
INFO_LDIF_BACKEND_LDIF_FILE_CHANGED_363=La modification du chemin du fichier de LDIF ne prend pas effet tant que le backend n'est pas d\u00e9sactiv\u00e9 et activ\u00e9 \u00e0 nouveau
|
INFO_LDIF_BACKEND_BASE_DN_CHANGED_364=La modification du DN de base du backend de LDIF ne prend pas effet tant que le backend n'est pas d\u00e9sactiv\u00e9 et activ\u00e9 \u00e0 nouveau
|
MILD_ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRY_365=L'entr\u00e9e cible %s n'existe pas
|
MILD_ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRY_366=L'entr\u00e9e cible %s n'existe pas
|
SEVERE_ERR_TRUSTSTORE_ERROR_READING_KEY_367=Error reading key %s from key store %s: %s
|
MILD_ERR_HAS_SUBORDINATES_NOT_SUPPORTED_368=Ce backend ne prend pas en charge l'attribut op\u00e9rationnel hasSubordinates
|
MILD_ERR_NUM_SUBORDINATES_NOT_SUPPORTED_369=Ce backend ne prend pas en charge l'attribut op\u00e9rationnel numSubordinates
|
NOTICE_BACKEND_OFFLINE_370=Le backend %s est maintenant hors ligne
|
