# 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=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=El conjunto de ND de base que se utilizar\u00e1 para las b\u00fasquedas "singleLevel" (un solo nivel), "wholeSubtree" (todo el \u00e1rbol) y "subordinateSubtree" (\u00e1rbol subordinado) en funci\u00f3n del DSE ra\u00edz. Si no se especifica esta opci\u00f3n, se utilizar\u00e1 el conjunto de todos los sufijos definidos por el usuario
|
###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=Se ha solicitado al servidor de fondo DSE ra\u00edz que recupere la entrada con el ND "%s". A este servidor de fondo s\u00f3lo se le puede solicitar que recupere el propio DSE ra\u00edz. Sin embargo, se realizar\u00e1 una comprobaci\u00f3n del mismo con los servidores de fondo subordinados definidos y se verificar\u00e1 si puede buscar la entrada solicitada
|
MILD_ERR_ROOTDSE_ADD_NOT_SUPPORTED_7=No se puede agregar la entrada "%s" porque no se admiten las operaciones de adici\u00f3n en el servidor de fondo DSE ra\u00edz
|
MILD_ERR_ROOTDSE_DELETE_NOT_SUPPORTED_8=No se puede suprimir la entrada "%s" porque no se admiten las operaciones de eliminaci\u00f3n en el servidor de fondo DSE ra\u00edz
|
MILD_ERR_ROOTDSE_MODIFY_NOT_SUPPORTED_9=No se puede actualizar la entrada "%s" porque no se admiten las operaciones de modificaci\u00f3n en el servidor de fondo DSE ra\u00edz. Si desea modificar el contenido del propio DSE ra\u00edz, es posible realizar esta operaci\u00f3n mediante la modificaci\u00f3n de la entrada "%s" de la configuraci\u00f3n
|
MILD_ERR_ROOTDSE_MODIFY_DN_NOT_SUPPORTED_10=No se puede cambiar el nombre de la entrada "%s" porque no se admiten las operaciones de modificaci\u00f3n de ND en el servidor de fondo DSE ra\u00edz
|
MILD_ERR_ROOTDSE_INVALID_SEARCH_BASE_11=No se puede realizar una b\u00fasqueda (Id. de conexi\u00f3n %d, Id. de operaci\u00f3n %d) con el ND de base de "%s" en el servidor de fondo DSE ra\u00edz. El ND de base de las b\u00fasquedas de este servidor de fondo debe ser el ND del propio DSE ra\u00edz
|
###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=Se ha actualizado la configuraci\u00f3n del DSE ra\u00edz para que utilice el conjunto definido de sufijos del servidor de directorios al realizar b\u00fasquedas por debajo del DSE ra\u00edz
|
INFO_ROOTDSE_USING_NEW_SUBORDINATE_BASE_DNS_19=Se ha actualizado la configuraci\u00f3n del DSE ra\u00edz para que utilice el conjunto de ND de base %s al realizar b\u00fasquedas por debajo del DSE ra\u00edz
|
INFO_ROOTDSE_USING_NEW_USER_ATTRS_20=Se ha actualizado la configuraci\u00f3n del DSE ra\u00edz para que utilice un nuevo conjunto de atributos definidos por el usuario
|
###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=No se puede agregar la entrada "%s" porque no se admiten las operaciones de adici\u00f3n en el servidor de fondo de supervisi\u00f3n
|
MILD_ERR_MONITOR_DELETE_NOT_SUPPORTED_24=No se puede suprimir la entrada "%s" porque no se admiten las operaciones de eliminaci\u00f3n en el servidor de fondo de supervisi\u00f3n
|
MILD_ERR_MONITOR_MODIFY_NOT_SUPPORTED_25=No se puede actualizar la entrada "%s" porque no se admiten las operaciones de modificaci\u00f3n en el servidor de fondo de supervisi\u00f3n. Si desea modificar el contenido de la propia entrada de supervisi\u00f3n de base, es posible realizar esta operaci\u00f3n mediante la modificaci\u00f3n de la entrada "%s" en la configuraci\u00f3n
|
MILD_ERR_MONITOR_MODIFY_DN_NOT_SUPPORTED_26=No se puede cambiar el nombre de la entrada "%s" porque no se admiten las operaciones de modificaci\u00f3n de ND en el servidor de fondo de supervisi\u00f3n
|
###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=Se ha actualizado la configuraci\u00f3n de supervisi\u00f3n para que utilice un nuevo conjunto de atributos definidos por el usuario
|
MILD_ERR_MONITOR_GET_ENTRY_NULL_32=No se puede recuperar la entrada solicitada del servidor de fondo de supervisi\u00f3n porque el ND especificado es nulo
|
MILD_ERR_MONITOR_BASE_TOO_DEEP_33=No se puede recuperar la entrada solicitada %s del servidor de fondo de supervisi\u00f3n porque el ND se encuentra en un nivel demasiado profundo. Las entradas de supervisi\u00f3n s\u00f3lo pueden encontrarse en un nivel por debajo de %s
|
MILD_ERR_MONITOR_INVALID_BASE_34=No se puede recuperar la entrada solicitada %s del servidor de fondo de supervisi\u00f3n porque el ND no se encuentra por debajo de la base de supervisi\u00f3n de %s
|
MILD_ERR_MONITOR_MULTIVALUED_RDN_35=No se puede recuperar la entrada solicitada %s del servidor de fondo de supervisi\u00f3n porque es posible que las entradas de supervisi\u00f3n no contengan RDN con varios valores
|
MILD_ERR_MONITOR_NO_SUCH_PROVIDER_36=No se puede recuperar la entrada solicitada del servidor de fondo de supervisi\u00f3n porque no hay ning\u00fan proveedor de supervisi\u00f3n "%s" registrado en el servidor de directorios
|
INFO_MONITOR_UPTIME_37=%d d\u00edas %d horas %d minutos %d segundos
|
###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=ND o conjunto de ND de las entradas que pueden recuperarse con el fin de obtener la informaci\u00f3n del esquema de Directory Server. Pueden especificarse varios valores si el esquema va a estar disponible en varias ubicaciones por motivos de compatibilidad. Si se no se especifica ning\u00fan valor, se utilizar\u00e1 el valor predeterminado "cn=schema"
|
###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=No se puede agregar la entrada "%s" porque no se admiten las operaciones de adici\u00f3n en el servidor de fondo del esquema
|
MILD_ERR_SCHEMA_DELETE_NOT_SUPPORTED_42=No se puede suprimir la entrada "%s" porque no se admiten las operaciones de eliminaci\u00f3n en el servidor de fondo del esquema
|
MILD_ERR_SCHEMA_MODIFY_NOT_SUPPORTED_43=No se puede actualizar la entrada "%s" porque a\u00fan no se admiten las operaciones de modificaci\u00f3n en el servidor de fondo del esquema. Si desea modificar el contenido de la propia entrada de esquema de base, es posible realizar esta operaci\u00f3n mediante la modificaci\u00f3n de la entrada "%s" de la configuraci\u00f3n
|
MILD_ERR_SCHEMA_MODIFY_DN_NOT_SUPPORTED_44=No se puede cambiar el nombre de la entrada "%s" porque no se admiten las operaciones de modificaci\u00f3n de ND en el servidor de fondo del esquema
|
###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=No se puede recuperar la entrada solicitada %s desde el servidor de fondo del esquema debido a que el ND es igual a uno de los ND de entrada de esquema
|
###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=Se ha anulado satisfactoriamente el registro del ND %s, por lo que ya no estar\u00e1 disponible como ND de entrada de esquema
|
###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=Se ha registrado satisfactoriamente el ND %s como ND de entrada de esquema
|
###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 configuraci\u00f3n de esquema se ha actualizado para que utilice un nuevo conjunto de atributos definidos por el usuario
|
###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=Se ha producido un error que impide que se restablezca correctamente la copia de seguridad del esquema. Sin embargo, los archivos de esquema originales, presentes al inicio del proceso de restablecimiento, se han conservado y se encuentran actualmente en su ubicaci\u00f3n original %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 recopilaci\u00f3n de mensajes calculada a partir del archivo de copia de seguridad coincide con la recopilaci\u00f3n almacenada en la informaci\u00f3n de copia de seguridad
|
###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 recopilaci\u00f3n firmada que se ha calculado a partir del archivo de copia de seguridad coincide con la firma almacenada en la informaci\u00f3n de copia de seguridad
|
###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=Todas las pruebas realizadas en la copia de seguridad del esquema %s del directorio %s indican que el archivo parece v\u00e1lido
|
NOTICE_SCHEMA_RESTORE_SUCCESSFUL_90=La copia de seguridad del esquema %s se ha restablecido satisfactoriamente a partir del archivo ubicado en el directorio %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_SCHEDULE_ATTRIBUTE_104=The provided recurring task \
|
### entry does not contain attribute %s which is needed to specify recurring task \
|
### schedule
|
###SEVERE_ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_TYPES_105=The provided recurring \
|
### task entry contains multiple attributes with type %s, which is used to hold \
|
### recurring task schedule, but only a single instance is allowed
|
###SEVERE_ERR_RECURRINGTASK_NO_SCHEDULE_VALUES_106=The provided recurring task \
|
### entry does not contain any values for the %s attribute, which is used to \
|
### specify recurring task schedule
|
###SEVERE_ERR_RECURRINGTASK_MULTIPLE_SCHEDULE_VALUES_107=The provided recurring \
|
### task entry contains multiple values for the %s attribute, which is used to \
|
### specify recurring task schedule, 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=Periodo de tiempo, en segundos, que debe conservarse la informaci\u00f3n de la tarea una vez finalizado el procesamiento de dicha tarea. Una vez transcurrido este periodo, la informaci\u00f3n de la tarea se suprimir\u00e1 autom\u00e1ticamente para conservar espacio en el disco y memoria
|
###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=La ruta al archivo de copia de seguridad del servidor de fondo de tareas. El archivo LDIF albergar\u00e1 la configuraci\u00f3n completa de las tareas programadas y peri\u00f3dicas definidas
|
###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=El tiempo de retenci\u00f3n de las tareas completadas se ha actualizado a %d segundos. Este cambio se aplicar\u00e1 inmediatamente
|
INFO_TASKBE_UPDATED_BACKING_FILE_129=La ruta al archivo de copia de seguridad de los datos de tareas se ha cambiado a %s. Se ha incluido una captura de la configuraci\u00f3n de tareas actual en ese archivo, que se seguir\u00e1 utilizando en futuras actualizaciones
|
###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=El archivo contiene los datos utilizados por el servidor de fondo del programador de tareas del servidor de directorios. No modifique directamente este archivo, ya que es posible que esos cambios se pierdan. Las definiciones de tareas programadas y peri\u00f3dicas s\u00f3lo deben modificarse mediante las utilidades de administraci\u00f3n proporcionadas con el servidor de directorios
|
###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_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 work as \
|
### expected
|
###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=Se est\u00e1 cerrando el servidor de fondo de tareas
|
INFO_ROOTDSE_DESCRIPTION_SHOW_ALL_ATTRIBUTES_157=Indica si todos los atributos del DSE ra\u00edz deben considerarse como atributos de usuario (y, por lo tanto, devolverse a los clientes de forma predeterminada), independientemente de la configuraci\u00f3n de esquema del servidor de directorios
|
###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 configuraci\u00f3n del DSE ra\u00edz se ha actualizado para que el atributo de configuraci\u00f3n %s utilice el valor %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=El conjunto de directorios al que se acceder\u00e1 de forma predeterminada para las operaciones de b\u00fasqueda del servidor de fondo de copia de seguridad. A\u00fan se puede acceder a los directorios de copia de seguridad que no aparezcan en esta lista. Para ello, especifique el directorio de copia de seguridad en el ND de base de b\u00fasqueda. Los cambios realizados en este atributo de configuraci\u00f3n se aplicar\u00e1n inmediatamente
|
###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=Indica si los atributos de la entrada del subesquema deben considerarse como atributos de usuarios, aunque est\u00e9n marcados como operativos. Esto puede proporcionar compatibilidad con algunas aplicaciones que esperan que se incluyan, de forma predeterminada, atributos como "attributeType" y "objectClasses", aunque no se soliciten. Tenga en cuenta que el atributo "ldapSyntaxes" se considerar\u00e1 siempre como operativo para evitar problemas al intentar modificar el esquema a trav\u00e9s del protocolo
|
###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=El servidor de fondo del esquema no admite actualmente la eliminaci\u00f3n de elementos de esquema existentes
|
MILD_ERR_SCHEMA_INVALID_MODIFICATION_TYPE_212=El servidor de fondo del esquema no admite el tipo de modificaci\u00f3n %s
|
MILD_ERR_SCHEMA_MODIFY_UNSUPPORTED_ATTRIBUTE_TYPE_213=El servidor de fondo del esquema no admite la modificaci\u00f3n del tipo de atributo %s. S\u00f3lo se pueden modificar los tipos de atributos, las clases de objetos, los formatos de nombre, las reglas de contenido de DIT, las reglas de estructura de DIT y el uso de las reglas de coincidencia
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_ATTRTYPE_214=Se ha producido un error al intentar descodificar el tipo de atributo "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_ATTRTYPE_ALREADY_EXISTS_215=No se puede agregar el tipo de atributo %s al esquema del servidor porque hay un tipo de atributo existente con un nombre u OID conflictivo: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_OBJECTCLASS_216=Se ha producido un error al intentar descodificar el clase de objeto "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_OBJECTCLASS_217=No se puede agregar la clase de objeto %s porque su clase superior %s no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OC_UNDEFINED_REQUIRED_ATTR_218=No se puede agregar la clase de objeto %s porque necesita el atributo %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OC_UNDEFINED_OPTIONAL_ATTR_219=No se puede agregar la clase de objeto %s porque permite el atributo %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OBJECTCLASS_ALREADY_EXISTS_220=No se puede agregar la clase de objeto %s al esquema del servidor porque hay una clase de objeto existente con un nombre u OID conflictivo: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_READ_EXISTING_USER_SCHEMA_221=Se ha producido un error al intentar leer el contenido del archivo de esquema %s: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_SCHEMA_222=Se ha producido un error al intentar escribir el esquema actualizado: %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_NAME_FORM_223=Se ha producido un error al intentar descodificar el formato de nombre "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_DCR_224=Se ha producido un error al intentar descodificar la regla de contenido de DIT "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_DSR_225=Se ha producido un error al intentar descodificar la regla de estructura de DIT "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_MR_USE_226=Se ha producido un error al intentar descodificar el uso de la regla de coincidencia "%s": %s
|
MILD_ERR_SCHEMA_MODIFY_DELETE_NO_VALUES_227=El servidor no permitir\u00e1 la eliminaci\u00f3n de todos los valores del tipo de atributo %s del esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_ATTRTYPE_228=No se puede agregar el tipo de atributo %s porque entra en conflicto con varios tipos de atributos existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_UNDEFINED_SUPERIOR_ATTRIBUTE_TYPE_229=No se puede agregar el tipo de atributo %s porque hace referencia al tipo de atributo superior %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_OBJECTCLASS_230=No se puede agregar la clase de objeto %s porque entra en conflicto con varias clases de objetos existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_NAME_FORM_231=No se puede agregar el formato de nombre %s porque entra en conflicto con varios formatos de nombre existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_STRUCTURAL_OC_232=No se puede agregar el formato de nombre %s porque hace referencia a la clase de objeto estructural %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_REQUIRED_ATTR_233=No se puede agregar el formato de nombre %s porque hace referencia al tipo de atributo necesario %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_NF_UNDEFINED_OPTIONAL_ATTR_234=No se puede agregar el formato de nombre %s porque hace referencia al tipo de atributo opcional %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DCR_235=No se puede agregar la regla de contenido de DIT %s porque entra en conflicto con varias reglas de contenido de DIT existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_DCR_236=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto estructural %s, que ya se ha asociado a otra regla de contenido de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_STRUCTURAL_OC_237=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto estructural %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_AUXILIARY_OC_238=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto auxiliar %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_REQUIRED_ATTR_239=No se puede agregar la regla de contenido de DIT %s porque hace referencia al tipo de atributo necesario %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_OPTIONAL_ATTR_240=No se puede agregar la regla de contenido de DIT %s porque hace referencia al tipo de atributo opcional %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_UNDEFINED_PROHIBITED_ATTR_241=No se puede agregar la regla de contenido de DIT %s porque hace referencia al tipo de atributo prohibido %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_DSR_242=No se puede agregar la regla de estructura de DIT %s porque entra en conflicto con varias reglas de estructura de DIT existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_NAME_FORM_CONFLICT_FOR_ADD_DSR_243=No se puede agregar la regla de estructura de DIT %s porque hace referencia al formato de nombre %s, que ya se ha asociado a otra regla de estructura de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_DSR_UNDEFINED_NAME_FORM_244=No se puede agregar la regla de estructura de DIT %s porque hace referencia al formato de nombre %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_MR_USE_245=No se puede agregar el uso de la regla de coincidencia %s porque entra en conflicto con varios usos de reglas de coincidencia existentes (%s y %s)
|
MILD_ERR_SCHEMA_MODIFY_MR_CONFLICT_FOR_ADD_MR_USE_246=No se puede agregar el uso de la regla de coincidencia %s porque hace referencia a la regla de coincidencia %s, que ya se ha asociado a otro uso de la regla de coincidencia %s
|
MILD_ERR_SCHEMA_MODIFY_MRU_UNDEFINED_ATTR_247=No se puede agregar el uso de la regla de coincidencia %s porque hace referencia al tipo de atributo %s, que no se ha definido en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_AT_248=La referencia circular detectada para el tipo de atributo %s en el que la cadena de tipo superior hace referencia al propio tipo de atributo
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_OC_249=La referencia circular detectada para la clase de objeto %s en la que la cadena de clase superior hace referencia la propia clase de objeto
|
MILD_ERR_SCHEMA_MODIFY_CIRCULAR_REFERENCE_DSR_250=La referencia circular detectada para la regla de estructura de DIT %s en la que la cadena de regla superior hace referencia a la propia regla de estructura de DIT
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_CLEANED_251=Se ha producido un error al intentar crear copias de los archivos de esquema existentes antes de aplicar las actualizaciones: %s. El servidor pudo restablecer la configuraci\u00f3n de esquema original, por lo que no ser\u00e1 necesario realizar ninguna limpieza adicional
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_ORIG_FILES_NOT_CLEANED_252=Se ha producido un error al intentar crear copias de los archivos de esquema existentes antes de aplicar las actualizaciones: %s. Tambi\u00e9n se ha producido un problema al intentar restablecer la configuraci\u00f3n de esquema original, por lo que es posible que el servidor permanezca en un estado incoherente y podr\u00eda requerir una limpieza manual
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_RESTORED_253=Se ha producido un error al intentar escribir nuevas versiones de los archivos de esquema del servidor: %s. El servidor pudo restablecer la configuraci\u00f3n de esquema original, por lo que no ser\u00e1 necesario realizar ninguna limpieza adicional
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_WRITE_NEW_FILES_NOT_RESTORED_254=Se ha producido un error al intentar escribir nuevas versiones de los archivos de esquema del servidor: %s. Tambi\u00e9n se ha producido un problema al intentar restablecer la configuraci\u00f3n de esquema original, por lo que es posible que el servidor permanezca en un estado incoherente y podr\u00eda requerir una limpieza manual
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_ATTRIBUTE_TYPE_255=No se puede suprimir el tipo de atributo %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_SUPERIOR_TYPE_256=No se puede suprimir el tipo de atributo %s del esquema del servidor porque se hace referencia a \u00e9l como tipo superior para el tipo de atributo %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_OC_257=No se puede suprimir el tipo de atributo %s del esquema del servidor porque se hace referencia a \u00e9l como tipo de atributo necesario u opcional en la clase de objeto (ND) %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_NF_258=No se puede suprimir el tipo de atributo %s del esquema del servidor porque se hace referencia a \u00e9l como tipo de atributo necesario u opcional en el formato de nombre %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_DCR_259=No se puede suprimir el tipo de atributo %s del esquema del servidor porque se hace referencia a \u00e9l como tipo de atributo necesario, opcional o prohibido en la regla de contenido de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_AT_IN_MR_USE_260=No se puede suprimir el tipo de atributo %s del esquema del servidor porque se hace referencia a \u00e9l en el uso de la regla de coincidencia %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_OBJECTCLASS_261=No se puede suprimir la clase de objeto %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_SUPERIOR_CLASS_262=No se puede suprimir la clase de objeto %s del esquema del servidor porque se hace referencia a ella como clase superior para la clase de objeto %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_IN_NF_263=No se puede suprimir la clase de objeto %s del esquema del servidor porque se hace referencia a ella como clase estructural para el formato de nombre %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_OC_IN_DCR_264=No se puede suprimir la clase de objeto %s del esquema del servidor porque se hace referencia a ella como clase estructural o auxiliar para la regla de contenido de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_NAME_FORM_265=No se puede suprimir el formato de nombre %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NF_IN_DSR_266=No se puede suprimir el formato de nombre %s del esquema del servidor porque se hace referencia a \u00e9l en la regla de estructura de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DCR_267=No se puede suprimir la regla de contenido de DIT %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_DSR_268=No se puede suprimir la regla de estructura de DIT %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_DSR_SUPERIOR_RULE_269=No se puede suprimir la regla de estructura de DIT %s porque se hace referencia a ella como regla superior para la regla de estructura de DIT %s
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_MR_USE_270=No se puede suprimir el uso de la regla de coincidencia %s del esquema del servidor porque no se ha definido
|
MILD_ERR_SCHEMA_MODIFY_NF_OC_NOT_STRUCTURAL_271=No se puede agregar el formato de nombre %s porque hace referencia a la clase de objeto %s, que se ha definido en el esquema del servidor, pero no es una clase de objeto estructural
|
MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_STRUCTURAL_272=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto estructural %s, que se ha definido en el esquema del servidor, pero no es estructural
|
MILD_ERR_SCHEMA_MODIFY_STRUCTURAL_OC_CONFLICT_FOR_ADD_NF_273=No se puede agregar el formato de nombre %s porque hace referencia a la clase de objeto estructural %s, que ya se ha asociado a otro formato de nombre %s
|
MILD_ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_ATTRIBUTE_TYPE_274=No se puede agregar el tipo de atributo %s porque el tipo superior %s se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_ATTRTYPE_OBSOLETE_MR_275=No se puede agregar el tipo de atributo %s porque la regla de coincidencia asociada % se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OBSOLETE_SUPERIOR_OBJECTCLASS_276=No se puede agregar la clase de objeto %s porque la clase superior %s se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OC_OBSOLETE_REQUIRED_ATTR_277=No se puede agregar la clase de objeto %s porque el atributo necesario %s se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_OC_OBSOLETE_OPTIONAL_ATTR_278=No se puede agregar la clase de objeto %s porque el atributo opcional %s se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_NF_OC_OBSOLETE_279=No se puede agregar el formato de nombre %s porque la clase de objeto estructural %s se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_NF_OBSOLETE_REQUIRED_ATTR_280=No se puede agregar el formato de nombre %s porque necesita el tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_NF_OBSOLETE_OPTIONAL_ATTR_281=No se puede agregar el formato de nombre %s porque permite el tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_STRUCTURAL_OC_OBSOLETE_282=No se puede agregar la regla de contenido de DIT %s porque la clase de objeto estructural %s se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_OC_NOT_AUXILIARY_283=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto auxiliar %s, que se ha definido en el esquema del servidor, pero no es una clase auxiliar
|
MILD_ERR_SCHEMA_MODIFY_DCR_AUXILIARY_OC_OBSOLETE_284=No se puede agregar la regla de contenido de DIT %s porque permite la clase de objeto auxiliar %s, que se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_REQUIRED_ATTR_285=No se puede agregar la regla de contenido de DIT %s porque necesita el tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_OPTIONAL_ATTR_286=No se puede agregar la regla de contenido de DIT %s porque permite el tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_PROHIBITED_ATTR_287=No se puede agregar la regla de contenido de DIT %s porque proh\u00edbe el tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_NAME_FORM_288=No se puede agregar la regla de estructura de DIT %s porque su formato de nombre %s se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DSR_OBSOLETE_SUPERIOR_RULE_289=No se puede agregar la regla de estructura de DIT %s porque hace referencia a la regla superior %s, que se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MRU_OBSOLETE_MR_290=No se puede agregar el uso de la regla de coincidencia %s porque su regla de coincidencia %s se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_MRU_OBSOLETE_ATTR_291=No se puede agregar el uso de la regla de coincidencia %s porque hace referencia al tipo de atributo %s, que se ha marcado como OBSOLETO en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_DCR_OBSOLETE_AUXILIARY_OC_292=No se puede agregar la regla de contenido de DIT %s porque hace referencia a la clase de objeto auxiliar %s, que se ha marcado como OBSOLETA en el esquema del servidor
|
MILD_ERR_SCHEMA_MODIFY_INSUFFICIENT_PRIVILEGES_293=No dispone de suficientes privilegios para modificar el esquema del servidor de directorios
|
###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=El entorno de la base de datos JE correspondiente al Id. de servidor de fondo %s est\u00e1 da\u00f1ado. Reinicie Directory Server para volver a abrir el entorno
|
###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 tarea: %s\r\nEstado de la tarea: %s\r\nHora de inicio programada: %s\r\nHora de inicio real: %s\r\nHora de finalizaci\u00f3n: %s\r\n\r\nMensajes del registro:\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=Una solicitud de modificaci\u00f3n para cancelar la tarea ha interrumpido el procesamiento de las tareas
|
###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=El archivo LDIF %s configurado para su uso con el servidor de fondo de LDIF definido en la entrada de configuraci\u00f3n %s presenta varias entradas con el ND %s
|
MILD_ERR_LDIF_BACKEND_ENTRY_OUT_OF_SCOPE_343=El archivo LDIF %s configurado para su uso con el servidor de fondo de LDIF definido en la entrada de configuraci\u00f3n %s incluye la entrada %s, que no se encuentra por debajo del ND de base definido para ese servidor de fondo
|
MILD_ERR_LDIF_BACKEND_MISSING_PARENT_344=El archivo LDIF %s configurado para su uso con el servidor de fondo de LDIF definido en la entrada de configuraci\u00f3n %s contiene la entrada %s, pero a\u00fan no se ha le\u00eddo su entrada principal
|
###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=La entrada %s ya existe en el servidor de seguridad de LDIF
|
MILD_ERR_LDIF_BACKEND_ADD_MISSING_PARENT_349=El elemento principal de la entrada %s no existe
|
MILD_ERR_LDIF_BACKEND_DELETE_NO_SUCH_ENTRY_350=La entrada %s no existe
|
MILD_ERR_LDIF_BACKEND_DELETE_NONLEAF_351=La entrada %s presenta una o varias entradas subordinadas y no puede eliminarse hasta que se hayan suprimido primero sus entradas subordinadas
|
MILD_ERR_LDIF_BACKEND_MODIFY_NO_SUCH_ENTRY_352=La entrada %s no existe
|
MILD_ERR_LDIF_BACKEND_MODDN_NO_SUCH_SOURCE_ENTRY_353=La entrada de origen %s no existe
|
MILD_ERR_LDIF_BACKEND_MODDN_TARGET_ENTRY_ALREADY_EXISTS_354=La entrada de destino %s no existe
|
MILD_ERR_LDIF_BACKEND_MODDN_NEW_PARENT_DOESNT_EXIST_355=El nuevo ND principal %s no existe
|
MILD_ERR_LDIF_BACKEND_SEARCH_NO_SUCH_BASE_356=La entrada %s especificada como ND de base de b\u00fasqueda no existe
|
###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=El servidor de fondo de LDIF no proporciona actualmente ning\u00fan mecanismo de copia de seguridad o restablecimiento. En su lugar, utilice las operaciones de importaci\u00f3n y exportaci\u00f3n de LDIF
|
MILD_ERR_LDIF_BACKEND_LDIF_DOESNT_EXIST_362=El archivo LDIF %s, al que se hace referencia en la entrada de configuraci\u00f3n del servidor de fondo de LDIF %s, no existe
|
INFO_LDIF_BACKEND_LDIF_FILE_CHANGED_363=El cambio realizado en la ruta del archivo LDIF no se aplicar\u00e1 hasta que se deshabilite y se vuelva a habilitar el servidor de fondo
|
INFO_LDIF_BACKEND_BASE_DN_CHANGED_364=El cambio realizado en el ND de base del servidor de fondo de LDIF no se aplicar\u00e1 hasta que se deshabilite y se vuelva a habilitar el servidor de fondo
|
MILD_ERR_LDIF_BACKEND_HAS_SUBORDINATES_NO_SUCH_ENTRY_365=La entrada de destino %s no existe
|
MILD_ERR_LDIF_BACKEND_NUM_SUBORDINATES_NO_SUCH_ENTRY_366=La entrada de destino %s no existe
|
###SEVERE_ERR_TRUSTSTORE_ERROR_READING_KEY_367=Error reading key %s from key \
|
### store %s: %s
|
MILD_ERR_HAS_SUBORDINATES_NOT_SUPPORTED_368=Este servidor de fondo no proporciona compatibilidad con el atributo operativo "hasSubordinates"
|
MILD_ERR_NUM_SUBORDINATES_NOT_SUPPORTED_369=Este servidor de fondo no proporciona compatibilidad con el atributo operativo "numSubordinates"
|
NOTICE_BACKEND_OFFLINE_370=El servidor de fondo %s se ha establecido sin conexi\u00f3n
|
###SEVERE_ERR_RECURRINGTASK_INVALID_N_TOKENS_371=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid number \
|
### of tokens
|
###SEVERE_ERR_RECURRINGTASK_INVALID_MINUTE_TOKEN_372=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid minute \
|
### token
|
###SEVERE_ERR_RECURRINGTASK_INVALID_HOUR_TOKEN_373=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid hour \
|
### token
|
###SEVERE_ERR_RECURRINGTASK_INVALID_DAY_TOKEN_374=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid day of \
|
### the month token
|
###SEVERE_ERR_RECURRINGTASK_INVALID_MONTH_TOKEN_375=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid month of \
|
### the year token
|
###SEVERE_ERR_RECURRINGTASK_INVALID_WEEKDAY_TOKEN_376=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid day of the \
|
### week token
|
###SEVERE_ERR_RECURRINGTASK_INVALID_TOKENS_COMBO_377=The provided recurring task \
|
### entry attribute %s holding the recurring task schedule has invalid tokens \
|
### combination yielding a nonexistent calendar date
|
###SEVERE_ERR_TASKS_CANNOT_EXPORT_TO_FILE_378=An error occurred while \
|
### attempting to export task backend data: %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_MAC_379=An error occurred while attempting \
|
### to obtain the %s MAC provider to create the signed hash for the backup: %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_DIGEST_380=An error occurred while \
|
### attempting to obtain the %s message digest to create the hash for the backup: \
|
### %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_CREATE_ARCHIVE_FILE_381=An error occurred \
|
### while trying to create the tasks archive file %s in directory %s: %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_GET_CIPHER_382=An error occurred while \
|
### attempting to obtain the cipher to use to encrypt the backup: %s
|
###SEVERE_ERR_TASKS_BACKUP_ZIP_COMMENT_383=%s tasks backup %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_BACKUP_TASKS_FILE_384=An error occurred while \
|
### attempting to back up tasks file %s: %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_CLOSE_ZIP_STREAM_385=An error occurred while \
|
### trying to close the tasks archive file %s in directory %s: %s
|
###SEVERE_ERR_TASKS_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_386=An error occurred \
|
### while attempting to update the backup descriptor file %s with information \
|
### about the tasks backup: %s
|
###SEVERE_ERR_TASKS_RESTORE_NO_SUCH_BACKUP_387=Unable to restore or verify \
|
### tasks backup %s in directory %s because no such backup exists
|
###SEVERE_ERR_TASKS_RESTORE_NO_BACKUP_FILE_388=Unable to restore or verify \
|
### tasks backup %s in directory %s because the archive filename could not be \
|
### determined
|
###SEVERE_ERR_TASKS_RESTORE_NO_SUCH_FILE_389=Unable to restore or verify tasks \
|
### backup %s because the specified archive file %s does not exist
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_CHECK_FOR_ARCHIVE_390=Unable to restore or \
|
### verify tasks backup %s because an error occurred while trying to determine \
|
### whether backup archive %s exists: %s
|
###SEVERE_ERR_TASKS_RESTORE_UNKNOWN_DIGEST_391=Unable to restore or verify \
|
### tasks 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_TASKS_RESTORE_CANNOT_GET_DIGEST_392=Unable to restore or verify \
|
### tasks backup %s because it has an unsigned hash that uses an unknown or \
|
### unsupported digest algorithm of %s
|
###SEVERE_ERR_TASKS_RESTORE_UNKNOWN_MAC_393=Unable to restore or verify tasks \
|
### 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_TASKS_RESTORE_CANNOT_GET_MAC_394=Unable to restore or verify \
|
### tasks backup %s because it has a signed hash that uses an unknown or \
|
### unsupported MAC algorithm of %s
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_OPEN_BACKUP_FILE_395=Unable to restore or \
|
### verify tasks backup %s because an error occurred while attempting to open \
|
### the backup archive file %s: %s
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_CIPHER_396=Unable to restore or verify \
|
### tasks backup %s because it is encrypted using an unknown or unsupported \
|
### cipher: %s
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_GET_ZIP_ENTRY_397=Unable to restore or verify \
|
### tasks backup %s because an error occurred while trying to read the next \
|
### entry from the archive file %s: %s
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_CREATE_FILE_398=Unable to restore tasks \
|
### backup %s because an error occurred while trying to recreate file %s: %s
|
###SEVERE_ERR_TASKS_RESTORE_CANNOT_PROCESS_ARCHIVE_FILE_399=Unable to restore or \
|
### verify tasks backup %s because an error occurred while processing archived \
|
### file %s: %s
|
###SEVERE_ERR_TASKS_RESTORE_ERROR_ON_ZIP_STREAM_CLOSE_400=Unable to restore or \
|
### verify tasks backup %s because an unexpected error occurred while trying to \
|
### close the archive file %s: %s
|
NOTICE_TASKS_RESTORE_UNSIGNED_HASH_VALID_401=La recopilaci\u00f3n de mensajes calculada a partir del archivo de copia de seguridad coincide con la recopilaci\u00f3n almacenada en la informaci\u00f3n de copia de seguridad
|
###SEVERE_ERR_TASKS_RESTORE_UNSIGNED_HASH_INVALID_402=Unable to restore or \
|
### verify tasks backup %s because the message digest calculated from the backup \
|
### archive does not match the digest stored with the backup information
|
NOTICE_TASKS_RESTORE_SIGNED_HASH_VALID_403=La recopilaci\u00f3n firmada que se ha calculado a partir del archivo de copia de seguridad coincide con la firma almacenada en la informaci\u00f3n de copia de seguridad
|
###SEVERE_ERR_TASKS_RESTORE_SIGNED_HASH_INVALID_404=Unable to restore or verify \
|
### tasks backup %s because the signed digest calculated from the backup archive \
|
### does not match the signature stored with the backup information
|
NOTICE_TASKS_RESTORE_VERIFY_SUCCESSFUL_405=Todas las pruebas realizadas en la copia de seguridad de las tareas %s desde el directorio %s indican que el archivo parece ser v\u00e1lido
|
NOTICE_TASKS_RESTORE_SUCCESSFUL_406=La copia de seguridad de las tareas %s se ha restablecido correctamente desde el archivo del directorio %s
|
###SEVERE_ERR_BACKUP_MISSING_BACKUPID_407=The information for backup %s could \
|
### not be found in the backup directory %s
|
###SEVERE_ERR_BACKUP_CANNOT_UPDATE_BACKUP_DESCRIPTOR_408=An error occurred \
|
### while attempting to update the backup descriptor file %s with information \
|
### about the backup: %s
|
MILD_ERR_SCHEMA_MODIFY_RULEID_CONFLICTS_FOR_ADD_DSR_409=No se puede agregar la regla de estructura de DIT %s porque el identificador de reglas entra en conflicto con una regla de estructura de DIT existente (%s)
|
INFO_ERGONOMIC_SIZING_OF_JE_CLEANER_THREADS_410=La copia de seguridad de DB local %s no especifica el n\u00famero de subprocesos del depurador: estableciendo de forma predeterminada en %d subprocesos
|
INFO_ERGONOMIC_SIZING_OF_JE_LOCK_TABLES_411=La copia de seguridad de DB local %s no especifica el n\u00famero de tablas de bloqueo: estableciendo de forma predeterminada en %d
|
###SEVERE_ERR_TASKSCHED_DEPENDENCY_MISSING_412=Unable to schedule task %s \
|
###because its dependency task %s is missing
|
NOTICE_TASK_STARTED_413=%s tarea %s ha iniciado la ejecuci\u00f3n
|
NOTICE_TASK_FINISHED_414=%s tarea %s ha finalizado la ejecuci\u00f3n
|
MILD_ERR_SCHEMA_MODIFY_MULTIPLE_CONFLICTS_FOR_ADD_LDAP_SYNTAX_415=No se puede agregar la descripci\u00f3n de sintaxis LDAP con OID %s porque est\u00e1 en conflicto con una descripci\u00f3n de sintaxis de LDAP existente
|
MILD_ERR_SCHEMA_MODIFY_REMOVE_NO_SUCH_LSD_416=No se puede suprimir la descripci\u00f3n de sintaxis LDAP %s del esquema de servidor porque no se ha definido dicha descripci\u00f3n de sintaxis LDAP
|
MILD_ERR_ATTR_SYNTAX_INVALID_LDAP_SYNTAX_417=No se pudo analizar el valor proporcionado "%s" como sintaxis LDAP porque su OID %s corresponde a una sintaxis de atributo que ya se ha implementado
|
MILD_ERR_SCHEMA_MODIFY_CANNOT_DECODE_LDAP_SYNTAX_418=Se ha producido un error al intentar descodificar la descripci\u00f3n de sintaxis LDAP "%s": %s
|
