From 67405dde9ba213331dab1fc46cb18c485070fd5b Mon Sep 17 00:00:00 2001 From: matthew_swift <matthew_swift@localhost> Date: Fri, 05 Jun 2009 09:04:50 +0000 Subject: [PATCH] svn merge -r5333:5417 https://opends.dev.java.net/svn/opends/branches/b2.0 --- opends/src/messages/messages/protocol_es.properties | 542 ++++++++++++++++++++++++++++++++++++++---------------- 1 files changed, 381 insertions(+), 161 deletions(-) diff --git a/opends/src/messages/messages/protocol_es.properties b/opends/src/messages/messages/protocol_es.properties index 1ff5d41..d97e77f 100644 --- a/opends/src/messages/messages/protocol_es.properties +++ b/opends/src/messages/messages/protocol_es.properties @@ -20,15 +20,11 @@ # # CDDL HEADER END # -# Copyright 2006-2008 Sun Microsystems, Inc. - - - +# Copyright 2006-2009 Sun Microsystems, Inc. # # Global directives # global.category=PROTOCOL - # # Format string definitions # @@ -47,50 +43,21 @@ # # ORDINAL is an integer unique among other ordinals in this file # -MILD_ERR_ASN1_NULL_ELEMENT_1=No es posible descodificar la matriz de byte proporcionada como elemento ASN.1, la matriz era nula -MILD_ERR_ASN1_SHORT_ELEMENT_2=No es posible descodificar la matriz de byte proporcionada como elemento ASN.1, la longitud de la matriz (%d bytes) es inferior al m\u00ednimo necesario para un elemento ASN.1 (2 bytes) -MILD_ERR_ASN1_INVALID_NUM_LENGTH_BYTES_3=No es posible descodificar la matriz de byte proporcionada como elemento ASN.1, ya que conten\u00eda una longitud multibyte con un n\u00famero de bytes (%d) no v\u00e1lido -MILD_ERR_ASN1_TRUNCATED_LENGTH_4=No es posible descodificar la matriz de byte proporcionada como elemento ASN.1, ya que conten\u00eda una longitud multibyte de %d bytes pero la matriz era demasiado corta como para contener toda la longitud -MILD_ERR_ASN1_LENGTH_MISMATCH_5=No es posible descodificar la matriz de byte proporcionada como elemento ASN.1, ya que la longitud del valor descodificado (%d bytes) no es igual al n\u00famero de bytes restante en la matriz proporcionada (%d) -MILD_ERR_ASN1_ELEMENT_SET_NULL_6=No es posible descodificar la matriz de byte proporcionada como un conjunto de elementos ASN.1, la matriz era nula -MILD_ERR_ASN1_ELEMENT_SET_NO_LENGTH_7=No es posible descodificar la matriz de byte proporcionada como conjunto de elementos ASN.1, ya que se lleg\u00f3 al final de la matriz despu\u00e9s de haber le\u00eddo el tipo BER pero ninguno de los valores de un elemento -MILD_ERR_ASN1_ELEMENT_SET_INVALID_NUM_LENGTH_BYTES_8=No es posible descodificar la matriz de byte proporcionada como un conjunto de elementos ASN.1, ya que conten\u00eda una longitud multibyte con un n\u00famero de bytes (%d) no v\u00e1lido -MILD_ERR_ASN1_ELEMENT_SET_TRUNCATED_LENGTH_9=No es posible descodificar la matriz de byte proporcionada como un conjunto de elementos ASN.1, ya que conten\u00eda una longitud multibyte de %d bytes pero la matriz era demasiado corta como para contener toda la longitud -MILD_ERR_ASN1_ELEMENT_SET_TRUNCATED_VALUE_10=No es posible descodificar la matriz de byte proporcionada como un conjunto de elementos ASN.1, ya que la longitud decodificada de un elemento (%d) es superior al n\u00famero de bytes restantes (%d) -MILD_ERR_ASN1_BOOLEAN_SET_VALUE_NULL_11=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento booleano ASN.1, la matriz era nula -MILD_ERR_ASN1_BOOLEAN_SET_VALUE_INVALID_LENGTH_12=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento booleano ASN.1, la longitud de la matriz no era exactamente un byte (la longitud proporcionada era %d) -MILD_ERR_ASN1_BOOLEAN_DECODE_ELEMENT_NULL_13=No es posible descodificar el elemento ASN.1 proporcionado como elemento booleano, ya que el elemento proporcionado era nulo -MILD_ERR_ASN1_BOOLEAN_DECODE_ELEMENT_INVALID_LENGTH_14=No es posible descodificar el elemento ASN.1 proporcionado como elemento booleano, ya que la longitud del valor del elemento no era exactamente un byte (la longitud real era %d) -MILD_ERR_ASN1_BOOLEAN_DECODE_ARRAY_NULL_15=No es posible descodificar la matriz de byte proporcionada como elemento booleano ASN.1, la matriz era nula -MILD_ERR_ASN1_BOOLEAN_SHORT_ELEMENT_16=No es posible descodificar la matriz de byte proporcionada como elemento booleano ASN.1, la longitud de la matriz (%d bytes) es inferior al m\u00ednimo necesario para un elemento booleano (3 bytes) -MILD_ERR_ASN1_BOOLEAN_DECODE_ARRAY_INVALID_LENGTH_17=No es posible descodificar la matriz de byte proporcionada como elemento booleano ASN.1, la longitud del valor decodificado no era exactamente un byte (la longitud descodificada era %d) -MILD_ERR_ASN1_NULL_SET_VALUE_INVALID_LENGTH_18=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento nulo ASN.1, la longitud de la matriz no era exactamente cero bytes (la longitud proporcionada era %d) -MILD_ERR_ASN1_NULL_DECODE_ELEMENT_NULL_19=No es posible descodificar el elemento ASN.1 proporcionado como elemento nulo, ya que el elemento proporcionado era nulo -MILD_ERR_ASN1_NULL_DECODE_ELEMENT_INVALID_LENGTH_20=No es posible descodificar el elemento ASN.1 proporcionado como elemento nulo, ya que la longitud del valor del elemento no era exactamente cero bytes (la longitud real era %d) -MILD_ERR_ASN1_NULL_DECODE_ARRAY_NULL_21=No es posible descodificar la matriz de byte proporcionada como elemento nulo ASN.1, la matriz era nula -MILD_ERR_ASN1_NULL_DECODE_ARRAY_INVALID_LENGTH_22=No es posible descodificar la matriz de byte proporcionada como elemento nulo ASN.1, la longitud del valor descodificado no era exactamente cero bytes (la longitud descodificada era %d) -MILD_ERR_ASN1_OCTET_STRING_DECODE_ELEMENT_NULL_23=No es posible descodificar el elemento ASN.1 proporcionado como elemento de cadena de octetos, el elemento proporcionado era nulo -MILD_ERR_ASN1_OCTET_STRING_DECODE_ARRAY_NULL_24=No es posible descodificar la matriz de byte proporcionada como cadena de octetos ASN.1, la matriz era nula -MILD_ERR_ASN1_INTEGER_SET_VALUE_NULL_25=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento entero ASN.1, la matriz era nula -MILD_ERR_ASN1_INTEGER_SET_VALUE_INVALID_LENGTH_26=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento entero ASN.1, la longitud de la matriz no era de entre 1 y 4 bytes (la longitud proporcionada era %d) -MILD_ERR_ASN1_INTEGER_DECODE_ELEMENT_NULL_27=No es posible descodificar el elemento ASN.1 proporcionado como elemento entero, el elemento proporcionado era nulo -MILD_ERR_ASN1_INTEGER_DECODE_ELEMENT_INVALID_LENGTH_28=No es posible descodificar el elemento ASN.1 proporcionado como elemento entero, la longitud del valor del elemento no era de entre uno y cuatro bytes (la longitud real era %d) -MILD_ERR_ASN1_INTEGER_DECODE_ARRAY_NULL_29=No es posible descodificar la matriz de byte proporcionada como elemento entero ASN.1, la matriz era nula -MILD_ERR_ASN1_INTEGER_SHORT_ELEMENT_30=No es posible descodificar la matriz de byte proporcionada como elemento entero ASN.1, la longitud de la matriz (%d bytes) es inferior al m\u00ednimo necesario para un elemento entero (3 bytes) -MILD_ERR_ASN1_INTEGER_DECODE_ARRAY_INVALID_LENGTH_31=No es posible descodificar la matriz de byte proporcionada como elemento entero ASN.1, la longitud del valor decodificado no era de entre 1 y 4 bytes (la longitud decodificada era %d) -MILD_ERR_ASN1_ENUMERATED_SET_VALUE_NULL_32=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento enumerado ASN.1, la matriz era nula -MILD_ERR_ASN1_ENUMERATED_SET_VALUE_INVALID_LENGTH_33=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento enumerado ASN.1, la longitud de la matriz no era de entre 1 y 4 bytes (la longitud proporcionada era %d) -MILD_ERR_ASN1_ENUMERATED_DECODE_ELEMENT_NULL_34=No es posible descodificar el elemento ASN.1 proporcionado como elemento enumerado, el elemento proporcionado era nulo -MILD_ERR_ASN1_ENUMERATED_DECODE_ELEMENT_INVALID_LENGTH_35=No es posible descodificar el elemento ASN.1 proporcionado como elemento enumerado, la longitud del valor del elemento no era de entre uno y cuatro bytes (la longitud real era %d) -MILD_ERR_ASN1_ENUMERATED_DECODE_ARRAY_NULL_36=No es posible descodificar la matriz de byte proporcionada como elemento enumerado ASN.1, la matriz era nula -MILD_ERR_ASN1_ENUMERATED_SHORT_ELEMENT_37=No es posible descodificar la matriz de byte proporcionada como elemento enumerado ASN.1, la longitud de la matriz (%d bytes) es inferior al m\u00ednimo necesario para un elemento entero (3 bytes) -MILD_ERR_ASN1_ENUMERATED_DECODE_ARRAY_INVALID_LENGTH_38=No es posible descodificar la matriz de byte proporcionada como elemento enumerado ASN.1, la longitud del valor descodificado no era de entre 1 y 4 bytes (la longitud descodificada era %d) -MILD_ERR_ASN1_SEQUENCE_SET_VALUE_NULL_39=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento de secuencia ASN.1, la matriz era nula -MILD_ERR_ASN1_SEQUENCE_DECODE_ELEMENT_NULL_40=No es posible descodificar el elemento ASN.1 proporcionado como elemento de secuencia, ya que el elemento proporcionado era nulo -MILD_ERR_ASN1_SEQUENCE_DECODE_ARRAY_NULL_41=No es posible descodificar la matriz de byte proporcionada como elemento de secuencia ASN.1, la matriz era nula -MILD_ERR_ASN1_SET_SET_VALUE_NULL_42=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento de conjunto ASN.1, la matriz era nula -MILD_ERR_ASN1_SET_DECODE_ELEMENT_NULL_43=No es posible descodificar el elemento ASN.1 proporcionado como un elemento de conjunto, ya que el elemento proporcionado era nulo -MILD_ERR_ASN1_SET_DECODE_ARRAY_NULL_44=No es posible descodificar la matriz de byte proporcionada como un elemento de conjunto ASN.1, la matriz era nula +MILD_ERR_ASN1_TRUCATED_TYPE_BYTE_1=No es posible decodificar el elemento ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00eda el byte del tipo +MILD_ERR_ASN1_TRUNCATED_LENGTH_BYTE_2=No es posible decodificar el elemento ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00eda el primer byte de longitud +MILD_ERR_ASN1_INVALID_NUM_LENGTH_BYTES_3=No es posible decodificar el elemento ASN.1 porque conten\u00eda una longitud multibyte con un n\u00famero de bytes no v\u00e1lido (%d) +MILD_ERR_ASN1_TRUNCATED_LENGTH_BYTES_4=No es posible decodificar el elemento ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00eda una longitud de multibyte de %d bytes +MILD_ERR_ASN1_BOOLEAN_TRUNCATED_VALUE_5=No es posible decodificar el elemento booleano ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) +MILD_ERR_ASN1_BOOLEAN_INVALID_LENGTH_6=No es posible decodificar el elemento booleano ASN.1 porque la longitud del valor decodificado no era exactamente un byte (la longitud decodificada era %d) +MILD_ERR_ASN1_NULL_TRUNCATED_VALUE_7=No es posible decodificar el elemento nulo ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) +MILD_ERR_ASN1_NULL_INVALID_LENGTH_8=No es posible decodificar el elemento ASN.1 nulo porque la longitud del valor decodificado no era exactamente cero bytes (la longitud decodificada era %d) +MILD_ERR_ASN1_OCTET_STRING_TRUNCATED_VALUE_9=No es posible decodificar el elemento de la cadena de octeto ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) +MILD_ERR_ASN1_INTEGER_TRUNCATED_VALUE_10=No es posible decodificar el elemento ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) +MILD_ERR_ASN1_INTEGER_INVALID_LENGTH_11=No es posible decodificar el elemento entero ASN.1 porque la longitud del valor del elemento no era de entre uno y cuatro bytes (la longitud real era %d) +MILD_ERR_ASN1_SEQUENCE_READ_NOT_STARTED_12=No es posible decodificar el final de la secuencia o del conjunto ASN.1 porque no se ley\u00f3 el inicio de la secuencia +MILD_ERR_ASN1_SEQUENCE_READ_NOT_ENDED_13=No es posible decodificar el final de la secuencia o del conjunto ASN.1 porque no se pueden leer %d bytes en la secuencia de %d bytes de longitud +MILD_ERR_ASN1_SKIP_TRUNCATED_VALUE_14=No es posible omitir el elemento ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) +MILD_ERR_ASN1_SEQUENCE_SET_TRUNCATED_VALUE_15=No es posible decodificar el elemento de la secuencia o del conjunto ASN.1 porque se alcanz\u00f3 un final de archivo inesperado mientras se le\u00edan los bytes del valor (%d) MILD_ERR_LDAP_MESSAGE_DECODE_NULL_45=No es posible descodificar la secuencia ASN.1 proporcionada como un mensaje LDAP, la secuencia era nula MILD_ERR_LDAP_MESSAGE_DECODE_INVALID_ELEMENT_COUNT_46=No es posible descodificar la secuencia ASN.1 como mensaje LDAP, la secuencia conten\u00eda un n\u00famero de elementos no v\u00e1lido (se esperaba 2 o 3, se recibi\u00f3 %d) MILD_ERR_LDAP_MESSAGE_DECODE_MESSAGE_ID_47=No es posible descodificar la secuencia ASN.1 proporcionada como mensaje LDAP, el primer elemento de la secuencia no pudo descodificarse como un ID de mensaje entero: %s @@ -128,7 +95,7 @@ MILD_ERR_LDAP_BIND_REQUEST_DECODE_PASSWORD_79=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de enlace LDAP, no se pudo descodificar la contrase\u00f1a que se deb\u00eda utilizar para la autenticaci\u00f3n sencilla: %s MILD_ERR_LDAP_BIND_REQUEST_DECODE_SASL_INFO_80=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de enlace LDAP, no se pudo descodificar la informaci\u00f3n de autenticaci\u00f3n SASL: %s MILD_ERR_LDAP_BIND_REQUEST_DECODE_INVALID_CRED_TYPE_81=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de enlace LDAP, el elemento de informaci\u00f3n de autenticaci\u00f3n ten\u00eda un tipo BER no v\u00e1lido (se esperaba 80 o A3, se recibi\u00f3 %x) -MILD_ERR_LDAP_BIND_REQUEST_DECODE_CREDENTIALS_82=Cannot decode the provided ASN.1 element as an LDAP bind request protocol op because an unexpected error occurred while trying to decode the authentication info element: %s +MILD_ERR_LDAP_BIND_REQUEST_DECODE_CREDENTIALS_82=No es posible decodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de enlace LDAP porque se produjo un error inesperado al intentar decodificar el elemento de informaci\u00f3n de autenticaci\u00f3n: %s MILD_ERR_LDAP_COMPARE_REQUEST_DECODE_SEQUENCE_83=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de comparaci\u00f3n LDAP, el elemento no pudo descodificarse como una secuencia: %s MILD_ERR_LDAP_COMPARE_REQUEST_DECODE_INVALID_ELEMENT_COUNT_84=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de comparaci\u00f3n LDAP, la secuencia de petici\u00f3n ten\u00eda un n\u00famero de elementos no v\u00e1lido (se esperaba 2, se recibi\u00f3 %d) MILD_ERR_LDAP_COMPARE_REQUEST_DECODE_DN_85=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de solicitud de comparaci\u00f3n LDAP, no pudo descodificarse correctamente el ND de destino: %s @@ -218,25 +185,51 @@ MILD_ERR_LDAP_CLIENT_DECODE_INVALID_MULTIBYTE_LENGTH_169=El cliente envi\u00f3 una solicitud a Directory Server con un elemento ASN.1 utilizando varios bytes para expresar la longitud del valor. La solicitud indic\u00f3 que fueron necesarios %d bytes para expresar la longitud, pero supera el l\u00edmite m\u00e1ximo permitido de cuatro bytes MILD_ERR_LDAP_CLIENT_DECODE_ASN1_FAILED_170=El cliente envi\u00f3 una solicitud a Directory Server que no pudo descodificarse correctamente como un elemento ASN.1: %s MILD_ERR_LDAP_CLIENT_DECODE_LDAP_MESSAGE_FAILED_171=El cliente envi\u00f3 una solicitud a Directory Server que no pudo descodificarse correctamente como un elemento mensaje LDAP: %s -SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has occurred within the Directory Server to cause it to lose track of where it is in decoding requests on this client connection. It had an invalid decode state of %d, and this connection must be terminated +###SEVERE_ERR_LDAP_CLIENT_INVALID_DECODE_STATE_172=An internal error has \ +### occurred within the Directory Server to cause it to lose track of where it is \ +### in decoding requests on this client connection. It had an invalid decode \ +### state of %d, and this connection must be terminated MILD_ERR_LDAP_CLIENT_DECODE_INVALID_REQUEST_TYPE_173=El cliente envi\u00f3 un mensaje LDAP a Directory Server que no era un mensaje v\u00e1lido para una solicitud de cliente: %s MILD_ERR_LDAP_CLIENT_CANNOT_CONVERT_MESSAGE_TO_OPERATION_174=Directory Server no pudo convertir el mensaje LDAP le\u00eddo desde el cliente (%s) a una operaci\u00f3n interna para su procesamiento: %s MILD_ERR_LDAP_ABANDON_INVALID_MESSAGE_TYPE_175=No es posible convertir el mensaje LDAP proporcionado (%s) a una operaci\u00f3n de abandono: %s MILD_ERR_LDAP_UNBIND_INVALID_MESSAGE_TYPE_176=No es posible convertir el mensaje LDAP proporcionado (%s) a una operaci\u00f3n de desconexi\u00f3n: %s -FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection handler defined in configuration entry %s was unable to open a selector to allow it to multiplex the associated accept sockets: %s. This connection handler will be disabled -SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection handler defined in configuration entry %s was unable to create a server socket channel to accept connections on %s:%d: %s. The Directory Server will not listen for new connections on that address -FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler defined in configuration entry %s was unable to create any of the socket channels on any of the configured addresses. This connection handler will be disabled +###FATAL_ERR_LDAP_CONNHANDLER_OPEN_SELECTOR_FAILED_177=The LDAP connection \ +### handler defined in configuration entry %s was unable to open a selector to \ +### allow it to multiplex the associated accept sockets: %s. This connection \ +### handler will be disabled +###SEVERE_ERR_LDAP_CONNHANDLER_CREATE_CHANNEL_FAILED_178=The LDAP connection \ +### handler defined in configuration entry %s was unable to create a server \ +### socket channel to accept connections on %s:%d: %s. The Directory Server \ +### will not listen for new connections on that address +###FATAL_ERR_LDAP_CONNHANDLER_NO_ACCEPTORS_179=The LDAP connection handler \ +### defined in configuration entry %s was unable to create any of the socket \ +### channels on any of the configured addresses. This connection handler will be \ +### disabled MILD_ERR_LDAP_CONNHANDLER_DENIED_CLIENT_180=El intento de conexi\u00f3n desde el cliente %s a %s se ha rechazado, el cliente se incluy\u00f3 en uno de los rangos de direcciones denegados MILD_ERR_LDAP_CONNHANDLER_DISALLOWED_CLIENT_181=El intento de conexi\u00f3n desde el cliente %s a %s se ha rechazado, el cliente no se incluy\u00f3 en uno de los rangos de direcciones permitidos INFO_LDAP_CONNHANDLER_UNABLE_TO_REGISTER_CLIENT_182=Un error interno impidi\u00f3 a Directory Server registrar correctamente la conexi\u00f3n de cliente de %s a %s con un controlador de solicitud adecuado: %s MILD_ERR_LDAP_CONNHANDLER_CANNOT_ACCEPT_CONNECTION_183=El controlador de conexi\u00f3n LDAP definido en la entrada de configuraci\u00f3n %s no pudo aceptar una nueva conexi\u00f3n de cliente: %s -FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP connection handler defined in configuration entry %s has experienced consecutive failures while trying to accept client connections: %s. This connection handler will be disabled -FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler defined in configuration entry %s caught an unexpected error while trying to listen for new connections: %s. This connection handler will be disabled -FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a selector to multiplex reads from clients: %s. This request handler cannot continue processing -FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this client connection with the selector: %s -FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could not be registered with a request handler because the Directory Server is shutting down -FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could not be registered with a request handler because the pending queue associated with %s is too full -FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client connection is being deregistered from the associated request handler because the Directory Server is shutting down +###FATAL_ERR_LDAP_CONNHANDLER_CONSECUTIVE_ACCEPT_FAILURES_184=The LDAP \ +### connection handler defined in configuration entry %s has experienced \ +### consecutive failures while trying to accept client connections: %s. This \ +### connection handler will be disabled +###FATAL_ERR_LDAP_CONNHANDLER_UNCAUGHT_ERROR_185=The LDAP connection handler \ +### defined in configuration entry %s caught an unexpected error while trying to \ +### listen for new connections: %s. This connection handler will be disabled +###FATAL_ERR_LDAP_REQHANDLER_OPEN_SELECTOR_FAILED_186=%s was unable to open a \ +### selector to multiplex reads from clients: %s. This request handler cannot \ +### continue processing +###FATAL_ERR_LDAP_REQHANDLER_CANNOT_REGISTER_187=%s was unable to register this \ +### client connection with the selector: %s +###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_SHUTDOWN_188=This connection could \ +### not be registered with a request handler because the Directory Server is \ +### shutting down +###FATAL_ERR_LDAP_REQHANDLER_REJECT_DUE_TO_QUEUE_FULL_189=This connection could \ +### not be registered with a request handler because the pending queue associated \ +### with %s is too full +###FATAL_ERR_LDAP_REQHANDLER_DEREGISTER_DUE_TO_SHUTDOWN_190=This client \ +### connection is being deregistered from the associated request handler because \ +### the Directory Server is shutting down MILD_ERR_ASN1_READER_MAX_SIZE_EXCEEDED_191=No es posible descodificar los datos le\u00eddos como un elemento ASN.1, la longitud del elemento descodificado de %d bytes era mayor que la longitud del elemento permitido m\u00e1ximo de %d bytes. La secuencia de entrada subyacente se ha cerrado, ya no es posible utilizar este lector MILD_ERR_LDAP_FILTER_STRING_NULL_192=No es posible descodificar la cadena proporcionada como un filtro de b\u00fasqueda LDAP, la cadena era nula MILD_ERR_LDAP_FILTER_UNCAUGHT_EXCEPTION_193=No es posible descodificar la cadena proporcionada %s como un filtro de b\u00fasqueda LDAP, se lanz\u00f3 una excepci\u00f3n inesperada durante el procesamiento: %s @@ -249,7 +242,9 @@ MILD_ERR_LDAP_FILTER_SUBSTRING_NO_ASTERISKS_200=El filtro de b\u00fasqueda especificado "%s" no se pudo decodificar porque el valor de filtro de subcadena previsto entre las posiciones %d y %d no ten\u00eda ning\u00fan car\u00e1cter comod\u00edn de asterisco MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_COLON_201=El filtro de b\u00fasqueda especificado "%s" no se pudo decodificar porque el componente de coincidencia extensible que comenzaba en la posici\u00f3n %d no presentaba dos puntos para denotar el final del nombre de tipo de atributo MILD_ERR_LDAP_DISCONNECT_DUE_TO_INVALID_REQUEST_TYPE_202=Cerrando esta conexi\u00f3n, el cliente envi\u00f3 un mensaje no v\u00e1lido de tipo %s (ID de mensaje LDAP %d) que no se permite para mensajes de solicitud -SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected failure occurred while trying to process a request of type %s (LDAP message ID %d): %s. The client connection will be terminated +###SEVERE_ERR_LDAP_DISCONNECT_DUE_TO_PROCESSING_FAILURE_203=An unexpected \ +### failure occurred while trying to process a request of type %s (LDAP message \ +### ID %d): %s. The client connection will be terminated MILD_ERR_LDAP_INVALID_BIND_AUTH_TYPE_204=El mensaje de solicitud de enlace (ID de mensaje LDAP %d) inclu\u00eda un tipo de autenticaci\u00f3n no v\u00e1lido %s. Esto es un error de protocolo, y se cerrar\u00e1 esta conexi\u00f3n seg\u00fan lo expuesto en la secci\u00f3n 4.2.3 de RFC 2251 MILD_ERR_LDAP_DISCONNECT_DUE_TO_BIND_PROTOCOL_ERROR_205=Esta conexi\u00f3n de cliente se est\u00e1 cerrando, se produjo un error de protocolo al intentar procesar una solicitud de enlace. El ID de mensaje LDAP era %d y el mensaje de error de la respuesta de enlace era %s MILD_ERR_LDAPV2_SKIPPING_EXTENDED_RESPONSE_206=Se podr\u00eda haber enviado un mensaje de respuesta ampliada a un cliente LDAPv2 (ID de conexi\u00f3n=%d, ID de operaci\u00f3n=%d): %s. LDAPv2 no permite operaciones ampliadas, por lo que no se enviar\u00e1 esta respuesta @@ -259,7 +254,10 @@ MILD_ERR_LDAPV2_CLIENTS_NOT_ALLOWED_210=Directory Server se ha configurado para denegar el acceso a los clientes LDAPv2. Se cerrar\u00e1 esta conexi\u00f3n MILD_ERR_LDAPV2_EXTENDED_REQUEST_NOT_ALLOWED_211=El cliente con ID de conexi\u00f3n %d se autentic\u00f3 en Directory Server utilizando LDAPv2, pero intent\u00f3 enviar una solicitud de operaci\u00f3n ampliada (ID de mensaje LDAP %d), que no se permite para clientes LDAPv2. Esta conexi\u00f3n finalizar\u00e1 MILD_ERR_LDAP_STATS_INVALID_MONITOR_INITIALIZATION_212=Se intent\u00f3 inicializar el proveedor supervisor de estad\u00edsticas LDAP tal y como se define en la entrada de configuraci\u00f3n %s. Este proveedor de supervisi\u00f3n deber\u00e1 crearse solo de forma din\u00e1mica dentro del mismo Directory Server, y no dentro de la configuraci\u00f3n -SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request handler thread "%s" encountered an unexpected error that would have caused the thread to die: %s. The error has been caught and the request handler should continue operating as normal +###SEVERE_ERR_LDAP_REQHANDLER_UNEXPECTED_SELECT_EXCEPTION_213=The LDAP request \ +### handler thread "%s" encountered an unexpected error that would have caused \ +### the thread to die: %s. The error has been caught and the request handler \ +### should continue operating as normal MILD_ERR_LDAP_CONNHANDLER_REJECTED_BY_SERVER_214=Se rechaz\u00f3 el intento de registrar esta conexi\u00f3n con Directory Server. Esto podr\u00eda indicar que el servidor ya tiene establecido el n\u00famero m\u00e1ximo permitido de conexiones, o que se encuentra en modo de acceso restringido INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_ADDRESS_215=Direcci\u00f3n o conjunto de direcciones en las que este controlador de conexi\u00f3n puede aceptar conexiones de cliente. Si no se especific\u00f3 ning\u00fan valor, el servidor aceptar\u00e1 conexiones en todas las direcciones activas. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_216=Puerto TCP en el que este controlador de conexi\u00f3n puede aceptar conexiones de cliente. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server @@ -276,26 +274,86 @@ INFO_LDAP_CONNHANDLER_DESCRIPTION_ALLOW_STARTTLS_227=Indica si este controlador de conexi\u00f3n debe permitir a los clientes utilizar la operaci\u00f3n ampliada StartTLS para iniciar comunicaci\u00f3n segura a trav\u00e9s de una conexi\u00f3n que no sea LDAP SSL. Esto no puede utilizarse si est\u00e1 activado el SSL para el controlador de conexi\u00f3n. Los cambios realizados en este atributo de configuraci\u00f3n se aplicar\u00e1n inmediatamente en los clientes LDAP INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CLIENT_AUTH_POLICY_228=Directiva que deber\u00e1 utilizarse a la hora de solicitar o requerir al cliente que presente su propio certificado al establecer una conexi\u00f3n basada en SSL o utilizando StartTLS para iniciar un canal seguro en una conexi\u00f3n establecida. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_229=Sobrenombre del certificado que debe utilizar el controlador de conexi\u00f3n al aceptar conexiones basadas en SSL o al realizar la negociaci\u00f3n StartTLS. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen address "%s" in configuration entry "%s" could not be resolved: %s. Please make sure that name resolution is properly configured on this system -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected error occurred while processing the ds-cfg-listen-address attribute in configuration entry %s, which is used to specify the address or set of addresses on which to listen for client connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An unexpected error occurred while processing the ds-cfg-allowed-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are allowed to establish connections to this connection handler: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected error occurred while processing the ds-cfg-denied-client attribute in configuration entry %s, which is used to specify the address mask(s) of the clients that are not allowed to establish connections to this connection handler: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected error occurred while processing the ds-cfg-allow-ldap-v2 attribute in configuration entry %s, which is used to indicate whether LDAPv2 clients will be allowed to access this connection handler: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An unexpected error occurred while processing the ds-cfg-num-request-handlers attribute in configuration entry %s, which is used to specify the number of request handlers to use to read requests from clients: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=An unexpected error occurred while processing the ds-cfg-send-rejection-notice attribute in configuration entry %s, which is used to indicate whether to send a notice of disconnection message to rejected client connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive attribute in configuration entry %s, which is used to periodically send TCP Keep-Alive messages over idle connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An unexpected error occurred while processing the ds-cfg-use-tcp-no-delay attribute in configuration entry %s, which is used to determine whether to immediately flush responses to clients: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address attribute in configuration entry %s, which is used to determine whether to set the SO_REUSEADDR option on the listen socket: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An unexpected error occurred while processing the ds-cfg-max-request-size attribute in configuration entry %s, which is used to determine the maximum size in bytes that can be used for a client request: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP connection handler defined in configuration entry %s is configured to communicate over SSL and also to allow clients to use the StartTLS extended operation. These options can not be used at the same time, so clients will not be allowed to use the StartTLS operation -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected error occurred while processing the ds-cfg-allow-start-tls attribute in configuration entry %s, which is used to indicate whether clients can use the StartTLS extended operation: %s -SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client authentication policy "%s" specified in attribute ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The value must be one of "disabled", "optional", or "required" -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy attribute in configuration entry %s, which is used to specify the policy that should be used for requesting/requiring SSL client authentication: %s -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s -SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in attribute %s of configuration entry %s could not be decoded as a valid address mask: %s +###SEVERE_ERR_LDAP_CONNHANDLER_UNKNOWN_LISTEN_ADDRESS_230=The specified listen \ +### address "%s" in configuration entry "%s" could not be resolved: %s. Please \ +### make sure that name resolution is properly configured on this system +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_ADDRESS_231=An unexpected \ +### error occurred while processing the ds-cfg-listen-address attribute in \ +### configuration entry %s, which is used to specify the address or set of \ +### addresses on which to listen for client connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_NO_LISTEN_PORT_232=No listen port was defined \ +### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ +### required attribute +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_233=An unexpected \ +### error occurred while processing the ds-cfg-listen-port attribute in \ +### configuration entry %s, which is used to specify the port on which to listen \ +### for client connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOWED_CLIENTS_234=An \ +### unexpected error occurred while processing the ds-cfg-allowed-client \ +### attribute in configuration entry %s, which is used to specify the address \ +### mask(s) of the clients that are allowed to establish connections to this \ +### connection handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_DENIED_CLIENTS_235=An unexpected \ +### error occurred while processing the ds-cfg-denied-client attribute in \ +### configuration entry %s, which is used to specify the address mask(s) of the \ +### clients that are not allowed to establish connections to this connection \ +### handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_LDAPV2_236=An unexpected \ +### error occurred while processing the ds-cfg-allow-ldap-v2 attribute in \ +### configuration entry %s, which is used to indicate whether LDAPv2 clients will \ +### be allowed to access this connection handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_NUM_REQUEST_HANDLERS_237=An \ +### unexpected error occurred while processing the ds-cfg-num-request-handlers \ +### attribute in configuration entry %s, which is used to specify the number of \ +### request handlers to use to read requests from clients: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SEND_REJECTION_NOTICE_238=An \ +### unexpected error occurred while processing the ds-cfg-send-rejection-notice \ +### attribute in configuration entry %s, which is used to indicate whether to \ +### send a notice of disconnection message to rejected client connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_KEEPALIVE_239=An \ +### unexpected error occurred while processing the ds-cfg-use-tcp-keep-alive \ +### attribute in configuration entry %s, which is used to periodically send TCP \ +### Keep-Alive messages over idle connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_TCP_NODELAY_240=An \ +### unexpected error occurred while processing the ds-cfg-use-tcp-no-delay \ +### attribute in configuration entry %s, which is used to determine whether to \ +### immediately flush responses to clients: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_REUSE_ADDRESS_241=An \ +### unexpected error occurred while processing the ds-cfg-allow-tcp-reuse-address \ +### attribute in configuration entry %s, which is used to determine whether to \ +### set the SO_REUSEADDR option on the listen socket: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_MAX_REQUEST_SIZE_242=An \ +### unexpected error occurred while processing the ds-cfg-max-request-size \ +### attribute in configuration entry %s, which is used to determine the maximum \ +### size in bytes that can be used for a client request: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_243=An unexpected error \ +### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ +### %s, which is used to indicate whether to use SSL when accepting client \ +### connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_HAVE_SSL_AND_STARTTLS_244=The LDAP \ +### connection handler defined in configuration entry %s is configured to \ +### communicate over SSL and also to allow clients to use the StartTLS extended \ +### operation. These options can not be used at the same time, so clients will \ +### not be allowed to use the StartTLS operation +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_ALLOW_STARTTLS_245=An unexpected \ +### error occurred while processing the ds-cfg-allow-start-tls attribute in \ +### configuration entry %s, which is used to indicate whether clients can use the \ +### StartTLS extended operation: %s +###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_SSL_CLIENT_AUTH_POLICY_246=The SSL client \ +### authentication policy "%s" specified in attribute \ +### ds-cfg-ssl-client-auth-policy of configuration entry %s is invalid. The \ +### value must be one of "disabled", "optional", or "required" +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CLIENT_AUTH_POLICY_247=An \ +### unexpected error occurred while processing the ds-cfg-ssl-client-auth-policy \ +### attribute in configuration entry %s, which is used to specify the policy that \ +### should be used for requesting/requiring SSL client authentication: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_248=An \ +### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ +### attribute in configuration entry %s, which is used to specify the nickname of \ +### the certificate to use for accepting SSL/TLS connections: %s +###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_ADDRESS_MASK_249=The string %s defined in \ +### attribute %s of configuration entry %s could not be decoded as a valid \ +### address mask: %s INFO_LDAP_CONNHANDLER_NEW_ALLOWED_CLIENTS_250=Se ha aplicado un nuevo conjunto de m\u00e1scaras de direcci\u00f3n de cliente permitido para la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_NEW_DENIED_CLIENTS_251=Se ha aplicado un nuevo conjunto de m\u00e1scaras de direcci\u00f3n de cliente denegado para la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_NEW_ALLOW_LDAPV2_252=El valor del atributo ds-cfg-allow-ldap-v2 se ha actualizado a %s en la entrada de configuraci\u00f3n %s @@ -305,16 +363,26 @@ INFO_LDAP_CONNHANDLER_NEW_MAX_REQUEST_SIZE_256=El valor del atributo ds-cfg-max-request-size se ha actualizado a %s en la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_NEW_ALLOW_STARTTLS_257=El valor del atributo ds-cfg-allow-start-tls se ha actualizado a %s en la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_DESCRIPTION_KEEP_STATS_258=Indica si el controlador de conexi\u00f3n deber\u00eda conservar estad\u00edsticas relacionadas con la comunicaci\u00f3n de cliente LDAP. El hecho de mantener esta informaci\u00f3n puede provocar una ligera reducci\u00f3n de rendimiento, pero puede resultar \u00fatil a la hora de comprender los patrones de uso del cliente. Los cambios realizados en este atributo de configuraci\u00f3n tendr\u00e1n efecto inmediatamente, pero solo se aplicar\u00e1n a nuevas conexiones y tendr\u00e1n el efecto secundario de borrar todos los tipos estad\u00edsticos existentes que pudieran haberse recopilado -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected error occurred while processing the ds-cfg-keep-stats attribute in configuration entry %s, which is used to indicate whether LDAP usage statistics should be enabled for this connection handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEEP_STATS_259=An unexpected \ +### error occurred while processing the ds-cfg-keep-stats attribute in \ +### configuration entry %s, which is used to indicate whether LDAP usage \ +### statistics should be enabled for this connection handler: %s INFO_LDAP_CONNHANDLER_NEW_KEEP_STATS_260=El valor del atributo ds-cfg-keep-stats se ha actualizado a %s en la entrada de configuraci\u00f3n %s MILD_ERR_ASN1_LONG_SET_VALUE_INVALID_LENGTH_261=No es posible descodificar la matriz de byte proporcionada como el valor de un elemento largo ASN.1, la longitud de la matriz no estaba entre 1 y 8 bytes (la longitud proporcionada era %d) MILD_ERR_ASN1_LONG_DECODE_ELEMENT_INVALID_LENGTH_262=No es posible descodificar el elemento ASN.1 proporcionado como elemento largo, la longitud del valor del elemento no era de entre uno y ocho bytes (la longitud real era %d) MILD_ERR_ASN1_LONG_DECODE_ARRAY_INVALID_LENGTH_263=No es posible descodificar la matriz de byte proporcionada como elemento largo ASN.1, la longitud del valor descodificado no era de entre 1 y 8 bytes (la longitud descodificada era %d) -SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while trying to decode the DN %s used for internal operations as a root user: %s -INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_PROTOCOLS_265=Nombres de los protocolos SSL que se permitir\u00e1n utilizar en comunicaci\u00f3n SSL o StartTLS. Changes to this configuration attribute will take effect immediately but will only impact new SSL/TLS-based sessions created after the change -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL protocols to allow for SSL/TLS sessions: %s +###SEVERE_ERR_INTERNAL_CANNOT_DECODE_DN_264=An unexpected error occurred while \ +### trying to decode the DN %s used for internal operations as a root user: %s +INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_PROTOCOLS_265=Nombres de los protocolos SSL que se permitir\u00e1n utilizar en comunicaci\u00f3n SSL o StartTLS. Los cambios realizados en este atributo de configuraci\u00f3n tendr\u00e1n efecto inmediatamente, pero s\u00f3lo afectar\u00e1n a las nuevas sesiones basadas en SSL/TLS que se hayan creado tras la modificaci\u00f3n +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_PROTOCOLS_266=An unexpected \ +### error occurred while processing the ds-cfg-ssl-protocol attribute in \ +### configuration entry %s, which is used to specify the names of the SSL \ +### protocols to allow for SSL/TLS sessions: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_SSL_ENABLED_CIPHERS_267=Nombres de los conjuntos de cifrado SSL que se permitir\u00e1n utilizar en comunicaci\u00f3n SSL o StartTLS. Los cambios realizados en este atributo de configuraci\u00f3n tendr\u00e1n efecto inmediatamente, pero solo afectar\u00e1n a nuevas sesiones basadas en SSL o TLS creadas tras la modificaci\u00f3n -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected error occurred while processing the ds-cfg-ssl-protocol attribute in configuration entry %s, which is used to specify the names of the SSL cipher suites to allow for SSL/TLS sessions: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_SSL_CIPHERS_268=An unexpected \ +### error occurred while processing the ds-cfg-ssl-protocol attribute in \ +### configuration entry %s, which is used to specify the names of the SSL cipher \ +### suites to allow for SSL/TLS sessions: %s INFO_LDAP_CONNHANDLER_NEW_SSL_PROTOCOLS_269=El valor del atributo ds-cfg-ssl-protocol se ha actualizado a %s en la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_NEW_SSL_CIPHERS_270=El valor del atributo ds-cfg-ssl-cipher-suite se ha actualizado a %s en la entrada de configuraci\u00f3n %s MILD_ERR_LDAP_TLS_EXISTING_SECURITY_PROVIDER_271=El proveedor de seguridad de conexiones TLS no puede activarse en esta conexi\u00f3n de cliente, ya est\u00e1 utilizando el proveedor %s. StartTLS s\u00f3lo puede utilizarse en conexiones de texto plano @@ -361,51 +429,121 @@ MILD_ERR_ECN_CANNOT_DECODE_VALUE_312=No es posible descodificar el control de notificaci\u00f3n de cambio de entrada proporcionado, se produjo un error al intentar descodificar el valor de control: %s MILD_ERR_AUTHZIDRESP_NO_CONTROL_VALUE_313=No es posible descodificar el control de respuesta de la identidad de autorizaci\u00f3n proporcionado, no tiene un valor MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_DECODE_SEQUENCE_314=No es posible descodificar el elemento ASN.1 proporcionado como un op de protocolo de respuesta intermedia LDAP, el elemento no pudo descodificarse como una secuencia: %s -MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_DECODE_INVALID_ELEMENT_COUNT_315=Cannot decode the provided ASN.1 element as an LDAP intermediate response protocol op because the request sequence had an invalid number of elements (expected 0, 1, or 2, got %d) +MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_DECODE_INVALID_ELEMENT_COUNT_315=No es posible decodificar el elemento ASN.1 proporcionado como un op de protocolo de respuesta intermedia LDAP porque la secuencia de solicitud ten\u00eda un n\u00famero de elementos no v\u00e1lido (se esperaba 0, 1 o 2 y se recibi\u00f3 %d) MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_OID_316=Se produjo un error al intentar descodificar el OID de respuesta intermedia: %s MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_CANNOT_DECODE_VALUE_317=Se produjo un error al intentar descodificar el valor de respuesta intermedia: %s MILD_ERR_LDAP_INTERMEDIATE_RESPONSE_INVALID_ELEMENT_TYPE_318=El elemento de secuencia de respuesta intermedia conten\u00eda un tipo BER no v\u00e1lido %s que no era apropiado para el OID o para el valor INFO_LDAP_CONNHANDLER_DESCRIPTION_BACKLOG_319=Tama\u00f1o de cola de aceptaci\u00f3n, que controla el n\u00famero de nuevos intentos de conexi\u00f3n que se podr\u00eda permitir en la cola de reserva antes de que se rechace. Modificar este valor solo ser\u00e1 necesario si se espera que Directory Server va a recibir n\u00fameros elevados de nuevos intentos de conexi\u00f3n de forma simult\u00e1nea. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error occurred while processing the ds-cfg-accept-backlog attribute in configuration entry %s, which is used to specify the accept backlog size: %s -SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter "%s" cannot be used as a matched values filter because filters of type %s are not allowed for use in matched values filters -SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter "%s" cannot be used as a matched values filter because it is an extensible match filter that contains the dnAttributes flag, which is not allowed for matched values filters -SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values filter could not be decoded because there were an invalid number of elements in the attribute value assertion (expected 2, got %d) -SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting to decode the attribute value assertion in the provided matched values filter: %s -SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched values filter could not be decoded because there were an invalid number of elements in the substring sequence (expected 2, got %d) -SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values filter could not be decoded because there were no subInitial, subAny, or subFinal components in the substring filter -SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values filter could not be decoded because there were multiple subInitial components in the substring filter -SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter could not be decoded because there were multiple subFinal components in the substring filter -SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched values filter could not be decoded because there was an invalid element of type %s in the substring filter -SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values filter could not be decoded because an error occurred while decoding the substring filter component: %s -SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched values filter could not be decoded because an error occurred while decoding the presence filter component: %s -SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched values filter could not be decoded because there were an invalid number of elements in the extensible match sequence (expected 2 or 3, found %d) -SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched values filter could not be decoded because there were multiple matching rule ID elements found in the extensible match filter sequence -SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values filter could not be decoded because there were multiple attribute type elements found in the extensible match filter sequence -SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values filter could not be decoded because there were multiple assertion value elements found in the extensible match filter sequence -SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched values filter could not be decoded because there was an invalid element of type %s in the extensible match filter -SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched values filter could not be decoded because an error occurred while decoding the extensible match filter component: %s -SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values filter could not be decoded because it had an invalid BER type of %s -SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided matched values control because it does not have a value -SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode the provided matched values control because an error occurred while attempting to decode the value as an ASN.1 sequence: %s -SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched values control because the control value does not specify any filters for use in matching attribute values -SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided control as a password expired control because the provided control had a value that could not be parsed as an integer -SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided password expiring control because it does not have a value -SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot decode the provided control as a password expiring control because an error occurred while attempting to decode the number of seconds until expiration: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_BACKLOG_320=An unexpected error \ +### occurred while processing the ds-cfg-accept-backlog attribute in \ +### configuration entry %s, which is used to specify the accept backlog size: %s +###SEVERE_ERR_MVFILTER_INVALID_LDAP_FILTER_TYPE_321=The provided LDAP filter \ +### "%s" cannot be used as a matched values filter because filters of type %s are \ +### not allowed for use in matched values filters +###SEVERE_ERR_MVFILTER_INVALID_DN_ATTRIBUTES_FLAG_322=The provided LDAP filter \ +### "%s" cannot be used as a matched values filter because it is an extensible \ +### match filter that contains the dnAttributes flag, which is not allowed for \ +### matched values filters +###SEVERE_ERR_MVFILTER_INVALID_AVA_SEQUENCE_SIZE_323=The provided matched values \ +### filter could not be decoded because there were an invalid number of elements \ +### in the attribute value assertion (expected 2, got %d) +###SEVERE_ERR_MVFILTER_CANNOT_DECODE_AVA_324=An error occurred while attempting \ +### to decode the attribute value assertion in the provided matched values \ +### filter: %s +###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_SEQUENCE_SIZE_325=The provided matched \ +### values filter could not be decoded because there were an invalid number of \ +### elements in the substring sequence (expected 2, got %d) +###SEVERE_ERR_MVFILTER_NO_SUBSTRING_ELEMENTS_326=The provided matched values \ +### filter could not be decoded because there were no subInitial, subAny, or \ +### subFinal components in the substring filter +###SEVERE_ERR_MVFILTER_MULTIPLE_SUBINITIALS_327=The provided matched values \ +### filter could not be decoded because there were multiple subInitial components \ +### in the substring filter +###SEVERE_ERR_MVFILTER_MULTIPLE_SUBFINALS_328=The provided matched values filter \ +### could not be decoded because there were multiple subFinal components in the \ +### substring filter +###SEVERE_ERR_MVFILTER_INVALID_SUBSTRING_ELEMENT_TYPE_329=The provided matched \ +### values filter could not be decoded because there was an invalid element of \ +### type %s in the substring filter +###SEVERE_ERR_MVFILTER_CANNOT_DECODE_SUBSTRINGS_330=The provided matched values \ +### filter could not be decoded because an error occurred while decoding the \ +### substring filter component: %s +###SEVERE_ERR_MVFILTER_CANNOT_DECODE_PRESENT_TYPE_331=The provided matched \ +### values filter could not be decoded because an error occurred while decoding \ +### the presence filter component: %s +###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_SEQUENCE_SIZE_332=The provided matched \ +### values filter could not be decoded because there were an invalid number of \ +### elements in the extensible match sequence (expected 2 or 3, found %d) +###SEVERE_ERR_MVFILTER_MULTIPLE_MATCHING_RULE_IDS_333=The provided matched \ +### values filter could not be decoded because there were multiple matching rule \ +### ID elements found in the extensible match filter sequence +###SEVERE_ERR_MVFILTER_MULTIPLE_ATTRIBUTE_TYPES_334=The provided matched values \ +### filter could not be decoded because there were multiple attribute type \ +### elements found in the extensible match filter sequence +###SEVERE_ERR_MVFILTER_MULTIPLE_ASSERTION_VALUES_335=The provided matched values \ +### filter could not be decoded because there were multiple assertion value \ +### elements found in the extensible match filter sequence +###SEVERE_ERR_MVFILTER_INVALID_EXTENSIBLE_ELEMENT_TYPE_336=The provided matched \ +### values filter could not be decoded because there was an invalid element of \ +### type %s in the extensible match filter +###SEVERE_ERR_MVFILTER_CANNOT_DECODE_EXTENSIBLE_MATCH_337=The provided matched \ +### values filter could not be decoded because an error occurred while decoding \ +### the extensible match filter component: %s +###SEVERE_ERR_MVFILTER_INVALID_ELEMENT_TYPE_338=The provided matched values \ +### filter could not be decoded because it had an invalid BER type of %s +###SEVERE_ERR_MATCHEDVALUES_NO_CONTROL_VALUE_339=Cannot decode the provided \ +### matched values control because it does not have a value +###SEVERE_ERR_MATCHEDVALUES_CANNOT_DECODE_VALUE_AS_SEQUENCE_340=Cannot decode \ +### the provided matched values control because an error occurred while \ +### attempting to decode the value as an ASN.1 sequence: %s +###SEVERE_ERR_MATCHEDVALUES_NO_FILTERS_341=Cannot decode the provided matched \ +### values control because the control value does not specify any filters for use \ +### in matching attribute values +###SEVERE_ERR_PWEXPIRED_CONTROL_INVALID_VALUE_342=Cannot decode the provided \ +### control as a password expired control because the provided control had a \ +### value that could not be parsed as an integer +###SEVERE_ERR_PWEXPIRING_NO_CONTROL_VALUE_343=Cannot decode the provided \ +### password expiring control because it does not have a value +###SEVERE_ERR_PWEXPIRING_CANNOT_DECODE_SECONDS_UNTIL_EXPIRATION_344=Cannot \ +### decode the provided control as a password expiring control because an error \ +### occurred while attempting to decode the number of seconds until expiration: \ +### %s MILD_WARN_LDAP_CLIENT_DUPLICATE_MESSAGE_ID_345=Directory Server ya est\u00e1 procesando otra solicitud en la misma conexi\u00f3n de cliente con el mismo ID de mensaje %d MILD_WARN_LDAP_CLIENT_CANNOT_ENQUEUE_346=Directory Server detect\u00f3 un error inesperado al intentar agregar la solicitud de cliente a la cola de trabajo: %s INFO_JMX_CONNHANDLER_DESCRIPTION_LISTEN_PORT_347=Puerto TCP en el que este controlador de conexi\u00f3n puede aceptar conexiones administrativas. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute -SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s +###SEVERE_ERR_JMX_CONNHANDLER_NO_LISTEN_PORT_348=No listen port was defined \ +### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ +### required attribute +###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_349=An unexpected \ +### error occurred while processing the ds-cfg-listen-port attribute in \ +### configuration entry %s, which is used to specify the port on which to listen \ +### for client connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_USE_SSL_350=Indica si este controlador de conexi\u00f3n deber\u00eda utilizar SSL al aceptar conexiones de clientes. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error occurred while processing the ds-cfg-use-ssl attribute in configuration entry %s, which is used to indicate whether to use SSL when accepting client connections: %s +###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_USE_SSL_351=An unexpected error \ +### occurred while processing the ds-cfg-use-ssl attribute in configuration entry \ +### %s, which is used to indicate whether to use SSL when accepting client \ +### connections: %s INFO_JMX_CONNHANDLER_DESCRIPTION_SSL_CERT_NICKNAME_352=Sobrenombre del certificado que debe utilizar el controlador de conexi\u00f3n al aceptar conexiones basadas en SSL o al realizar la negociaci\u00f3n StartTLS. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An unexpected error occurred while processing the ds-cfg-ssl-cert-nickname attribute in configuration entry %s, which is used to specify the nickname of the certificate to use for accepting SSL/TLS connections: %s -SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided control as a password policy request control because the provided control had a value but the password policy request control should not have a value -SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided password policy response control because it does not have a value -SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided password policy response control because the warning element has an invalid type of %s -SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided password policy response control because the error element has an invalid type of %d -SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided password policy response control because the value sequence has an element with an invalid type of %s -SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password policy response control: %s +###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_SSL_CERT_NICKNAME_353=An \ +### unexpected error occurred while processing the ds-cfg-ssl-cert-nickname \ +### attribute in configuration entry %s, which is used to specify the nickname of \ +### the certificate to use for accepting SSL/TLS connections: %s +###SEVERE_ERR_PWPOLICYREQ_CONTROL_HAS_VALUE_354=Cannot decode the provided \ +### control as a password policy request control because the provided control had \ +### a value but the password policy request control should not have a value +###SEVERE_ERR_PWPOLICYRES_NO_CONTROL_VALUE_355=Cannot decode the provided \ +### password policy response control because it does not have a value +###SEVERE_ERR_PWPOLICYRES_INVALID_WARNING_TYPE_356=Cannot decode the provided \ +### password policy response control because the warning element has an invalid \ +### type of %s +###SEVERE_ERR_PWPOLICYRES_INVALID_ERROR_TYPE_357=Cannot decode the provided \ +### password policy response control because the error element has an invalid \ +### type of %d +###SEVERE_ERR_PWPOLICYRES_INVALID_ELEMENT_TYPE_358=Cannot decode the provided \ +### password policy response control because the value sequence has an element \ +### with an invalid type of %s +###SEVERE_ERR_PWPOLICYRES_DECODE_ERROR_359=Cannot decode the provided password \ +### policy response control: %s INFO_PWPERRTYPE_DESCRIPTION_PASSWORD_EXPIRED_360=passwordExpired INFO_PWPERRTYPE_DESCRIPTION_ACCOUNT_LOCKED_361=accountLocked INFO_PWPERRTYPE_DESCRIPTION_CHANGE_AFTER_RESET_362=changeAfterReset @@ -421,35 +559,77 @@ MILD_ERR_PROXYAUTH1_UNUSABLE_ACCOUNT_372=No se permite que la configuraci\u00f3n de la directiva de contrase\u00f1a utilice el control V1 de autorizaci\u00f3n por proxy para el usuario %s MILD_ERR_PROXYAUTH2_CANNOT_LOCK_USER_373=No se pudo obtener un bloqueo en la entrada de usuario %s para la validaci\u00f3n del control V2 de autorizaci\u00f3n por proxy MILD_ERR_PROXYAUTH2_UNUSABLE_ACCOUNT_374=No se permite que la configuraci\u00f3n de la directiva de contrase\u00f1a utilice el control V2 de autorizaci\u00f3n por proxy para el usuario %s -SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided control as an account availability request control because the provided control had a value but the account availability request control should not have a value -SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided account availability response control because it does not have a value -SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account availability response control indicated that the account was unavailable but had an unknown unavailable element type of %s -SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account availability response control had an unknown ACCOUNT_USABLE_RESPONSE element type of %s -SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account availability response control: %s -SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided address mask prefix because an invalid value was specified. The permitted values for IPv4are 0 to32 and for IPv6 0 to128 -SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided address mask because an prefix mask was specified with an wild card "*" match character -SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided address mask because the it has an invalid format +###SEVERE_ERR_ACCTUSABLEREQ_CONTROL_HAS_VALUE_375=Cannot decode the provided \ +### control as an account availability request control because the provided \ +### control had a value but the account availability request control should not \ +### have a value +###SEVERE_ERR_ACCTUSABLERES_NO_CONTROL_VALUE_376=Cannot decode the provided \ +### account availability response control because it does not have a value +###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_UNAVAILABLE_TYPE_377=The account \ +### availability response control indicated that the account was unavailable but \ +### had an unknown unavailable element type of %s +###SEVERE_ERR_ACCTUSABLERES_UNKNOWN_VALUE_ELEMENT_TYPE_378=The account \ +### availability response control had an unknown ACCOUNT_USABLE_RESPONSE element \ +### type of %s +###SEVERE_ERR_ACCTUSABLERES_DECODE_ERROR_379=Cannot decode the provided account \ +### availability response control: %s +###SEVERE_ERR_ADDRESSMASK_PREFIX_DECODE_ERROR_380=Cannot decode the provided \ +### address mask prefix because an invalid value was specified. The permitted \ +### values for IPv4are 0 to32 and for IPv6 0 to128 +###SEVERE_ERR_ADDRESSMASK_WILDCARD_DECODE_ERROR_381=Cannot decode the provided \ +### address mask because an prefix mask was specified with an wild card "*" match \ +### character +###SEVERE_ERR_ADDRESSMASK_FORMAT_DECODE_ERROR_382=Cannot decode the provided \ +### address mask because the it has an invalid format MILD_ERR_LDAP_NO_CLEAR_SECURITY_PROVIDER_383=El controlador de conexi\u00f3n LDAP %s no pudo enviar una respuesta de texto plano al cliente, no tiene una referencia a un proveedor de seguridad de conexi\u00f3n plana MILD_ERR_LDAP_ATTRIBUTE_DUPLICATE_VALUES_384=El atributo LDAP proporcionado %s contiene valores duplicados MILD_ERR_LDAP_FILTER_UNKNOWN_MATCHING_RULE_385=El filtro de b\u00fasqueda LDAP proporcionado hace referencia a una regla de coincidencia desconocida %s MILD_ERR_LDAP_FILTER_VALUE_WITH_NO_ATTR_OR_MR_386=El filtro de b\u00fasqueda LDAP proporcionado tiene un valor de aserci\u00f3n, pero no incluye un tipo de atributo o un ID de regla de coincidencia -FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call select() in the LDAP connection handler: %s. It appears that your JVM may be susceptible to the issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable to handle LDAP requests in its current configuration. Please upgrade to a newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) or set the number of available file descriptors to a value greater than or equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting the Directory Server +###FATAL_ERR_LDAP_REQHANDLER_DETECTED_JVM_ISSUE_CR6322825_387=Unable to call \ +### select() in the LDAP connection handler: %s. It appears that your JVM may \ +### be susceptible to the issue described at \ +### http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6322825, and it is unable \ +### to handle LDAP requests in its current configuration. Please upgrade to a \ +### newer JVM that does not exhibit this behavior (Java 5.0 Update 8 or higher) \ +### or set the number of available file descriptors to a value greater than or \ +### equal to 8193 (e.g., by issuing the command 'ulimit -n 8193') before starting \ +### the Directory Server MILD_ERR_PROXYAUTH1_CONTROL_NOT_CRITICAL_388=No se puede procesar la solicitud, contiene un control V1 de autorizaci\u00f3n por proxy que no est\u00e1 marcado como cr\u00edtico. El control de autorizaci\u00f3n por proxy debe tener siempre una criticalidad de "true" MILD_ERR_PROXYAUTH2_CONTROL_NOT_CRITICAL_389=No se puede procesar la solicitud, contiene un control V2 de autorizaci\u00f3n por proxy que no est\u00e1 marcado como cr\u00edtico. El control de autorizaci\u00f3n por proxy debe tener siempre una criticalidad de "true" INFO_LDAP_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_390=ND de la entrada de configuraci\u00f3n del proveedor del administrador de claves que deber\u00eda utilizarse con este controlador de conexi\u00f3n LDAP. Los cambios efectuados en este atributo tendr\u00e1n efecto de forma inmediata, pero \u00fanicamente para los intentos posteriores de acceder al proveedor del administrador de claves de las conexiones de cliente asociadas -SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute ds-cfg-key-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled key manager provider -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the key manager provider for use with the LDAP connection handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_KEYMANAGER_DN_391=Configuration attribute \ +### ds-cfg-key-manager-provider of configuration entry %s has an invalid value \ +### %s which does not reference an enabled key manager provider +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_392=An error \ +### occurred while processing the ds-cfg-key-manager-provider attribute in \ +### configuration entry %s, which is used to specify the key manager provider for \ +### use with the LDAP connection handler: %s INFO_LDAP_CONNHANDLER_DESCRIPTION_TRUSTMANAGER_DN_393=ND de la entrada de configuraci\u00f3n del proveedor del administrador de confianza que deber\u00eda utilizarse con este controlador de conexi\u00f3n LDAP. Los cambios efectuados en este atributo tendr\u00e1n efecto de forma inmediata, pero \u00fanicamente para los intentos posteriores de acceder al proveedor del administrador de confianza de las conexiones de cliente asociadas -SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration attribute ds-cfg-trust-manager-provider of configuration entry %s has an invalid value %s which does not reference an enabled trust manager provider -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error occurred while processing the ds-cfg-trust-manager-provider attribute in configuration entry %s, which is used to specify the trust manager provider for use with the LDAP connection handler: %s +###SEVERE_ERR_LDAP_CONNHANDLER_INVALID_TRUSTMANAGER_DN_394=Configuration \ +### attribute ds-cfg-trust-manager-provider of configuration entry %s has an \ +### invalid value %s which does not reference an enabled trust manager provider +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_DETERMINE_TRUSTMANAGER_DN_395=An error \ +### occurred while processing the ds-cfg-trust-manager-provider attribute in \ +### configuration entry %s, which is used to specify the trust manager provider \ +### for use with the LDAP connection handler: %s INFO_LDAP_CONNHANDLER_NEW_KEYMANAGER_DN_396=El valor del atributo ds-cfg-key-manager-provider se ha actualizado a %s en la entrada de configuraci\u00f3n %s INFO_LDAP_CONNHANDLER_NEW_TRUSTMANAGER_DN_397=El valor del atributo ds-cfg-trust-manager-provider se ha actualizado a %s en la entrada de configuraci\u00f3n %s INFO_JMX_CONNHANDLER_DESCRIPTION_KEYMANAGER_DN_398=ND del proveedor del administrador de claves que debe utilizar el controlador de conexi\u00f3n al aceptar conexiones basadas en SSL o al realizar la negociaci\u00f3n StartTLS. Los cambios realizados en este atributo de configuraci\u00f3n se aplicar\u00e1n inmediatamente -SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, because the provided key manager DN %s does not refer to an enabled key manager provider -SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected error occurred while processing the ds-cfg-key-manager-provider attribute in configuration entry %s, which is used to specify the DN of the key manager provider to use for accepting SSL/TLS connections: %s +###SEVERE_ERR_JMX_CONNHANDLER_INVALID_KEYMANAGER_DN_399=An error occurred while \ +### processing the ds-cfg-key-manager-provider attribute in configuration \ +### entry %s, because the provided key manager DN %s does not refer to an enabled \ +### key manager provider +###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_DETERMINE_KEYMANAGER_DN_400=An unexpected \ +### error occurred while processing the ds-cfg-key-manager-provider attribute \ +### in configuration entry %s, which is used to specify the DN of the key manager \ +### provider to use for accepting SSL/TLS connections: %s MILD_ERR_LDAP_CONNHANDLER_CANNOT_SET_SECURITY_PROVIDER_401=Se produjo un error al intentar configurar el proveedor de seguridad de conexi\u00f3n de la conexi\u00f3n de cliente: %s -SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which key manager provider should be used -SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection handler defined in configuration entry %s is configured to use either SSL or StartTLS, but does not specify which trust manager provider should be used +###SEVERE_ERR_LDAP_CONNHANDLER_NO_KEYMANAGER_DN_402=The LDAP connection handler \ +### defined in configuration entry %s is configured to use either SSL or \ +### StartTLS, but does not specify which key manager provider should be used +###SEVERE_ERR_LDAP_CONNHANDLER_NO_TRUSTMANAGER_DN_403=The LDAP connection \ +### handler defined in configuration entry %s is configured to use either SSL or \ +### StartTLS, but does not specify which trust manager provider should be used INFO_LDAPS_CONNHANDLER_DESCRIPTION_ENABLE_404=Especifica si se debe habilitar el controlador de conexi\u00f3n LDAPS MILD_ERR_LDAP_FILTER_NOT_EXACTLY_ONE_405=El filtro de b\u00fasqueda especificado "%s" no se pudo decodificar porque el filtro NOT ubicado entre las posiciones %d y %d no conten\u00eda exactamente un componente de filtro INFO_SORTREQ_CONTROL_NO_VALUE_406=No se pudo descodificar el control proporcionado como un control de solicitud de ordenaci\u00f3n en servidor, no incluye un valor de control @@ -470,7 +650,7 @@ INFO_VLVRES_CONTROL_NO_VALUE_421=No se pudo descodificar el control proporcionado como un control de respuesta VLV, no incluye un valor de control INFO_VLVRES_CONTROL_INVALID_ELEMENT_COUNT_422=No se pudo descodificar el control proporcionado como control de respuesta VLV, contiene un n\u00famero de elementos no v\u00e1lido: %d INFO_VLVRES_CONTROL_CANNOT_DECODE_VALUE_423=No se pudo procesar el control de respuesta VLV, se produjo un error al intentar descodificar el valor de control: %s -INFO_GETEFFECTIVERIGHTS_INVALID_AUTHZID_424=El Id. de autorizaci\u00f3n "%s" contenido en el control geteffectiverights no es v\u00e1lido ya que no empieza por "dn:" para indicar un ND de usuario +INFO_GETEFFECTIVERIGHTS_INVALID_AUTHZID_424=El ID de autorizaci\u00f3n "%s" que contiene el control geteffectiverights no es v\u00e1lido, no comienza por "dn:" para indicar un ND de usuario INFO_GETEFFECTIVERIGHTS_DECODE_ERROR_425=No es posible descodificar el control de solicitud geteffectiverights proporcionado: %s INFO_CANNOT_DECODE_GETEFFECTIVERIGHTS_AUTHZID_DN_426=No se pudo descodificar la cadena ND authzid "%s" como nombre distinguido v\u00e1lido: %s MILD_ERR_LDAP_FILTER_ENCLOSED_IN_APOSTROPHES_427=Un filtro LDAP entre ap\u00f3strofes no es v\u00e1lido: %s @@ -478,8 +658,10 @@ MILD_ERR_LDAP_FILTER_INVALID_CHAR_IN_ATTR_TYPE_429=El filtro de b\u00fasqueda proporcionado contiene un tipo de atributo no v\u00e1lido "%s" con un car\u00e1cter no v\u00e1lido "%s" en la posici\u00f3n %d MILD_ERR_LDAP_FILTER_EXTENSIBLE_MATCH_NO_AD_OR_MR_430=El filtro de b\u00fasqueda especificado "%s" no se pudo descodificar porque el componente de coincidencia extensible que comenzaba en la posici\u00f3n %d no inclu\u00eda ninguna descripci\u00f3n de atributo ni ID. de regla coincidente. Debe especificarse, al menos, uno de estos elementos MILD_ERR_LDAPV2_CONTROLS_NOT_ALLOWED_431=No se permite a los clientes LDAPv2 utilizar controles de solicitud -SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler defined in configuration entry %s was unable to bind to %s:%d: %s -SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined in configuration entry %s was unable to bind to port %d: %s +###SEVERE_ERR_LDAP_CONNHANDLER_CANNOT_BIND_432=The LDAP connection handler \ +### defined in configuration entry %s was unable to bind to %s:%d: %s +###SEVERE_ERR_JMX_CONNHANDLER_CANNOT_BIND_433=The JMX connection handler defined \ +### in configuration entry %s was unable to bind to port %d: %s MILD_ERR_JMX_ADD_INSUFFICIENT_PRIVILEGES_434=No cuenta con privilegios suficientes para efectuar operaciones de adici\u00f3n a trav\u00e9s de JMX MILD_ERR_JMX_DELETE_INSUFFICIENT_PRIVILEGES_435=No cuenta con privilegios suficientes para efectuar operaciones de eliminaci\u00f3n a trav\u00e9s de JMX MILD_ERR_JMX_MODIFY_INSUFFICIENT_PRIVILEGES_436=No cuenta con privilegios suficientes para efectuar operaciones de modificaci\u00f3n a trav\u00e9s de JMX @@ -491,26 +673,64 @@ MILD_ERR_INTERNALOS_INVALID_REQUEST_442=El mensaje LDAP proporcionado ten\u00eda un tipo de operaci\u00f3n no v\u00e1lido (%s) para una solicitud MILD_ERR_INTERNALOS_SASL_BIND_NOT_SUPPORTED_443=Las operaciones de conexi\u00f3n SASL no son compatibles a trav\u00e9s de sockets LDAP internos MILD_ERR_INTERNALOS_STARTTLS_NOT_SUPPORTED_444=Las operaciones StartTLS no son compatibles a trav\u00e9s de sockets LDAP internos -SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s specified as the LDIF directory path for the LDIF connection handler defined in configuration entry %s exists but is not a directory. The specified path must be a directory. The LDIF connection handler will start, but will not be able to proces any changes until this path is changed to a directory +###SEVERE_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_NOT_DIRECTORY_445=The value %s \ +### specified as the LDIF directory path for the LDIF connection handler defined \ +### in configuration entry %s exists but is not a directory. The specified path \ +### must be a directory. The LDIF connection handler will start, but will not \ +### be able to proces any changes until this path is changed to a directory MILD_WARN_LDIF_CONNHANDLER_LDIF_DIRECTORY_MISSING_446=El directorio %s al que hace referencia el controlador de conexi\u00f3n LDIF definido en la entrada de configuraci\u00f3n %s no existe. El controlador de conexi\u00f3n LDIF se iniciar\u00e1, pero no podr\u00e1 procesar ning\u00fan cambio hasta que se cree este directorio -MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL_447=An error occurred while trying to read a change record from the LDIF file: %s. This change will be skipped but processing on the LDIF file will continue -MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL_448=An error occurred while trying to read a change record from the LDIF file: %s. No further processing on this LDIF file can be performed +MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_NONFATAL_447=Se produjo un error al intentar leer un registro de cambios en el archivo LDIF: %s. Este cambio se omitir\u00e1 aunque el archivo LDIF seguir\u00e1 proces\u00e1ndose +MILD_ERR_LDIF_CONNHANDLER_CANNOT_READ_CHANGE_RECORD_FATAL_448=Se produjo un error al intentar leer un registro de cambios en el archivo LDIF: %s. No se puede seguir procesando el archivo LDIF INFO_LDIF_CONNHANDLER_UNKNOWN_CHANGETYPE_449=Tipo de cambio no admitido %s -INFO_LDIF_CONNHANDLER_RESULT_CODE_450=Result Code: %d (%s) +INFO_LDIF_CONNHANDLER_RESULT_CODE_450=C\u00f3digo de resultado: %d (%s) INFO_LDIF_CONNHANDLER_ERROR_MESSAGE_451=Informaci\u00f3n adicional: %s INFO_LDIF_CONNHANDLER_MATCHED_DN_452=ND coincidente: %s INFO_LDIF_CONNHANDLER_REFERRAL_URL_453=URL de referencia: %s -SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF connection handler was processing LDIF file %s: %s -SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the LDIF connection handler was attempting to rename partially-processed file from %s to %s: %s -SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the LDIF connection handler was attempting to delete processed file %s: %s -SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use +###SEVERE_ERR_LDIF_CONNHANDLER_IO_ERROR_454=An I/O error occurred while the LDIF \ +### connection handler was processing LDIF file %s: %s +###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_RENAME_455=An error occurred while the \ +### LDIF connection handler was attempting to rename partially-processed file \ +### from %s to %s: %s +###SEVERE_ERR_LDIF_CONNHANDLER_CANNOT_DELETE_456=An error occurred while the \ +### LDIF connection handler was attempting to delete processed file %s: %s +###SEVERE_ERR_CONNHANDLER_ADDRESS_INUSE_457=Address already in use INFO_SNMP_CONNHANDLER_DESCRIPTION_LISTEN_PORT_1458=Puerto SNMP en el que este controlador de conexi\u00f3n acepta solicitudes SNMP. Los cambios efectuados en este atributo de configuraci\u00f3n no tendr\u00e1n efecto hasta que el controlador de conexi\u00f3n se desactive y se vuelva a activar, o hasta que se reinicie Directory Server -SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined using configuration ds-cfg-listen-port in configuration entry %s. This is a required attribute -SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected error occurred while processing the ds-cfg-listen-port attribute in configuration entry %s, which is used to specify the port on which to listen for client connections: %s -SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected error occurred when this connection handler started -SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined for this connection handler. The configuration parameters ds-cfg-listen-port and ds-cfg-trap-port are required by the connection handler to start -SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is an unknown host. Traps will not be sent to this destination -SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the appropriated OpenDMK jar files to enable the SNMP Connection Handler. Please go under http://opendmk.dev.java.net and set the ds-cfg-opendmk-jarfile configuration parameter to set the full path of the required jdmkrt.jar file. The SNMP connection Handler didn't started -SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=An unexpected error occurred while trying to initialize the SNMP Connection Handler. Please check the configuration attributes -SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap destinations has been found. No trap will be sent - +###SEVERE_ERR_SNMP_CONNHANDLER_NO_LISTEN_PORT_1459=No listen port was defined \ +### using configuration ds-cfg-listen-port in configuration entry %s. This is a \ +### required attribute +###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_DETERMINE_LISTEN_PORT_1460=An unexpected \ +### error occurred while processing the ds-cfg-listen-port attribute in \ +### configuration entry %s, which is used to specify the port on which to listen \ +### for client connections: %s +###SEVERE_ERR_SNMP_CONNHANDLER_CANNOT_BE_STARTED_1461=An unexpected \ +### error occurred when this connection handler started +###SEVERE_ERR_SNMP_CONNHANDLER_NO_CONFIGURATION_1462=No Configuration was defined \ +### for this connection handler. The configuration parameters ds-cfg-listen-port \ +### and ds-cfg-trap-port are required by the connection handler to start +###SEVERE_ERR_SNMP_CONNHANDLER_TRAPS_DESTINATION_1463=Traps Destination %s is \ +### an unknown host. Traps will not be sent to this destination +###SEVERE_ERR_SNMP_CONNHANDLER_NO_OPENDMK_JARFILES_1464=You do not have the \ +### appropriate OpenDMK jar files to enable the SNMP Connection Handler. \ +### Please go under http://opendmk.dev.java.net and set the \ +### opendmk-jarfile configuration parameter to set the full path \ +### of the required jdmkrt.jar file. The SNMP connection Handler didn't started +###SEVERE_ERR_SNMP_CONNHANDLER_BAD_CONFIGURATION_1465=Cannot initialize the \ +### SNMP Connection Handler. Please check the configuration attributes +###SEVERE_ERR_SNMP_CONNHANDLER_NO_VALID_TRAP_DESTINATIONS_1466=No valid trap \ +### destinations has been found. No trap will be sent +###SEVERE_ERR_ASN1_READ_ERROR_1500=An error occured while accessing the \ +### underlying data source: %s +###SEVERE_ERR_ASN1_EOF_ERROR_1501=An unexpected end of file reached while trying \ +### to read %d bytes from the underlying data source +###SEVERE_ERR_ASN1_INVALID_STATE_1502=Invalid reader state: %d +###SEVERE_ERR_SUBTREE_DELETE_INVALID_CONTROL_VALUE_1503=Cannot decode the provided \ +### subtree delete control because it contains a value + SEVERE_ERR_CONNHANDLER_SSL_CANNOT_INITIALIZE_1504=Se produjo un error al intentar inicializar el contexto SSL para su uso en el controlador de conexi\u00f3n LDAP: %s +MILD_ERR_LDAP_UNSUPPORTED_PROTOCOL_VERSION_1505=Directory Server no admite la versi\u00f3n %d del protocolo LDAP; esta conexi\u00f3n se cerrar\u00e1 +###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_DOES_NOT_EXIST_1506=The specified \ +### OpenDMK jar file '%s' could not be found. Verify that the value set in the \ +### opendmk-jarfile configuration parameter of the SNMP connection handler is the \ +### valid path to the jdmkrt.jar file and that the file is accessible +###SEVERE_ERR_SNMP_CONNHANDLER_OPENDMK_JARFILES_NOT_OPERATIONAL_1507=The required \ +### classes could not be loaded using jar file '%s'. Verify that the jar file \ +### is not corrupted -- Gitblit v1.10.0