Pular para conteúdo

lib codes en US

App Return Codes

-10 - -000000A

  • D_SOCKET_FAILED
  • Failed to create socket.
  • The socket creation has failed. Possible causes: system error. See logs for more details.

-11 - -000000B

  • D_GETHOSTNAME_FAILED
  • Failed to resolve HSM address.
  • The HSM address can not be resolved. Verify the informed HSM address. If load balance is in use, verify the addresses in the configuration file. If the address is correct, see logs for details.

-12 - -000000C

  • D_CONNECT_FAILED
  • Failed to connect to the HSM.
  • The connection to the HSM has failed. Possible cases for this error are: unavailable Network/HSM; failure in the network subsystem. Other less likable causes are: connection rejected by the HSM; internal socket error. See logs for more details.

-13 - -000000D

  • D_SEND_FAILED
  • Failed to send data.
  • Client could not successfully send data. Most possible causes to this error are: session timeout (client or HSM side); unavailable Network/HSM; failure in the network subsystem. Unlikely causes: socket internal error. See logs for more details.

-14 - -000000E

  • D_RECV_FAILED
  • Failed to receive data.
  • Client could not successfully receive data. Most possible causes to this error are: session timeout (client or HSM side); unavailable Network/HSM; Failure in the network subsystem. Unlikely causes: socket internal error. See logs for more details.

-15 - -000000F

  • D_INVALID_PACKAGE_SIZE
  • Invalid package size.
  • The size of the received data package differs from the expected data. See logs for more details.

-16 - -0000010

  • D_SETSOCKOPT_FAILED
  • Failed to set socket options.
  • Set socket options has failed. Probable causes: invalid parameter; failure in the network subsystem; connection time-out; socket internal failure. See logs for more details.

-17 - -0000011

  • D_GETSOCKOPT_FAILED
  • Failed to get socket options.
  • Get socket options has failed. Probable causes: invalid parameter buffer length; failure in the network subsystem; socket internal failure. See logs for more details.

-18 - -0000012

  • D_ALL_LOAD_BALANCE_HSM_FAILED
  • All HSM in the load balance list are unavailable.
  • The HSMs in the load balance list are all unavailable. After unsuccessfully trying to access all HSMs in the list this error is returned. In this specific case, after this error is returned, all the addresses registered in the list are available again for new connection retries without the suspension time. Possible causes: client machine network failure; failure when accessing the HSMs network; failure in all HSMs.

-19 - -0000013

  • D_RESET_BY_PEER_ERROR
  • Connection reset by peer.
  • The connection was focibly closed by the remote host.

-20 - -0000014

  • D_CONNECTION_REFUSED_ERROR
  • Connection refused.
  • No connection could be made because the remote host actively refused it.

-21 - -0000015

  • D_CONNECTION_TIMEDOUT_ERROR
  • Connection timedout.
  • The connection attempt failed because the target did not respond after a period of time, or estabilished connection failed because target has failed to respond.

-22 - -0000016

  • D_NETWORK_DOWN_ERROR
  • Network down.
  • The socket operation encountered a dead network.

-23 - -0000017

  • D_SSL_ZERO_RETURN_ERROR
  • Zero return.
  • The TLS/SSL peer has closed the connection for writing by sending the close_notify alert. No more data can be read.

-24 - -0000018

  • D_SSL_ERROR
  • SSL error.
  • A non-recoverable, fatal error in the SSL library occurred, usually a protocol error. See logs for more details.

1 - 80000001

  • D_SSL_CTX_NEW_FAILED
  • Failed to create new SSL context.
  • The SSL context creation has failed. Possible causes: system or internal error. See logs for more details.

2 - 80000002

  • D_SSL_NEW_FAILED
  • Failed to create TLS structure.
  • The TLS structure creation has failed. Possible causes: system or internal error. See logs for more details.

3 - 80000003

  • D_SSL_CONNECT_FAILED
  • Failed to initiate TLS handshake with HSM.
  • The TLS handshake initialization with the HSM has failed. At this moment the socket connection with the HSM is already established and the failure occurred at the TLS handshake. Possible causes: failure at the TLS handshake, use of older (very old versions) versions of the HSM with newer client library (vice versa), protocol level failure, connection failure. See logs for more details.

4 - 80000004

  • D_SSL_GENERAL_ERROR
  • General underlying crypto library error.
  • The underlying crypto library failed. One of the causes can be related to unsufficient local machine resources(memory). See logs for more details.

5 - 80000005

  • D_PIX_HTTP_CACHE_FULL
  • PIX HTTP connection cache is full.
  • The PIX connection cache already holds the configured maximum number of handles and no free handle matched the request. The cap is hard: no handle is created outside the cache and the request does not wait. Set it with the HSM_PIX_POOL_MAX_HANDLES environment variable or DPIXSetCacheParam(PIXCP_MAX_HANDLES); zero, the default, means no cap. Possible causes: caller concurrency above the cap, handles kept in use for too long. See logs for more details.

101 - 80000065

  • D_CRL_GENERAL_ERROR
  • General underlying crypto connection library error.
  • The underlying crypto connection library failed. One of the causes can be related to unsufficient local machine resources(memory). See logs for more details. Related to the communication between the local machine and the destination server.

102 - 80000066

  • D_CRL_SSL_CACERT_BADFILE
  • Could not load peer chain file.
  • The peer chain/CA certificate is either missing or in a wrong format. Related to the communication between the local machine and the destination server.

103 - 80000067

  • D_CRL_COULDNT_RESOLVE_HOST
  • Could not resolve host.
  • The host name could not be resolved or is malformed. Check the host name. Related to the communication between the local machine and the destination server.

104 - 80000068

  • D_CRL_COULDNT_CONNECT
  • Could not connect to host.
  • Failed to connect to host. Check the host name. Related to the communication between the local machine and the destination server.

105 - 80000069

  • D_CRL_OPERATION_TIMEDOUT
  • Operation timed out.
  • The operation exceeded the timeout time. Related to the communication between the local machine and the destination server.

106 - 8000006A

  • D_CRL_PEER_FAILED_VERIFICATION
  • Failed to verify peer certificate/fingerprint.
  • The peer certificate/fingerprint could not be verified. Related to the communication between the local machine and the destination server.

107 - 8000006B

  • D_CRL_SSL_CONNECT_ERROR
  • Failed do SSL handshake.
  • A problem occurred in the SSL/TLS handshake. Could be certificates (file formats, paths, permissions), passwords, and others. Related to the communication between the local machine and the destination server.

108 - 8000006C

  • D_CRL_SEND_ERROR
  • Failed send data.
  • A problem ocurred when sending data. Verify the network conection. Related to the communication between the local machine and the destination server.

109 - 8000006D

  • D_CRL_RECV_ERROR
  • Failed receive data.
  • A problem ocurred when receiving data. Verify the network conection. Related to the communication between the local machine and the destination server.

110 - 8000006E

  • D_CRL_SSL_CERTPROBLEM
  • Failure using the local certificate.
  • A problem ocurred when using the local certificate. Related to the communication between the local machine and the destination server.

111 - 8000006F

  • D_CRL_SSL_ISSUER_ERROR
  • Failed to check the certificate's issuer.
  • A problem ocurred when verifying the certificate's issuer. Related to the communication between the local machine and the destination server.

112 - 80000070

  • D_CRL_AUTH_ERROR
  • Failed authenticate.
  • A problem occurred in the authentication function. Related to the communication between the local machine and the destination server.

113 - 80000071

  • D_CRL_GOT_NOTHING
  • Nothing was returned from HTTP server.
  • Nothing was returned from the server and in this case it is an error. Related to the communication between the local machine and the destination server.

114 - 80000072

  • D_CRL_UNSUPPORTED_PROTOCOL
  • Unsupported protocol.
  • The protocol passed in the URL is not supported. Related to the communication between the local machine and the destination server.

115 - 80000073

  • D_CRL_URL_MALFORMAT
  • URL malformat.
  • The URL was not properly formatted. Related to the communication between the local machine and the destination server.

116 - 80000074

  • D_CRL_WEIRD_SERVER_REPLY
  • Unrecognized server reply.
  • The server sent a response that couldn't understand. Related to the communication between the local machine and the destination server.

117 - 80000075

  • D_CRL_REMOTE_ACCESS_DENIED
  • Access denied to remote resource.
  • The access was denied to the resource at the given URL. Related to the communication between the local machine and the destination server.

118 - 80000076

  • D_CRL_HTTP2
  • Error in HTTP2 framing layer.
  • This error can have serveral causes, see log for more details. Related to the communication between the local machine and the destination server.

119 - 80000077

  • D_CRL_WRITE_ERROR
  • Internal write callback failed.
  • This error can have serveral causes, see log for more details. Related to the communication between the local machine and the destination server.

120 - 80000078

  • D_CRL_READ_ERROR
  • Internal send callback failed.
  • This error can have serveral causes, see log for more details. Related to the communication between the local machine and the destination server.

121 - 80000079

  • D_CRL_HTTP_POST_ERROR
  • Error in HTTP POST.
  • This error can have serveral causes, see log for more details. Related to the communication between the local machine and the destination server.

122 - 8000007A

  • D_CRL_ABORTED_BY_CALLBACK
  • Operation aborted by internal callback.
  • This error can have serveral causes, see log for more details. Related to the communication between the local machine and the destination server.

123 - 8000007B

  • D_CRL_TOO_MANY_REDIRECTS
  • Too many redirects.
  • The maximum redirection count was reached. Related to the communication between the local machine and the destination server.

124 - 8000007C

  • D_CRL_SSL_CIPHER
  • Failed to use the specified cipher.
  • Couldn't use the specified cipher. Related to the communication between the local machine and the destination server.

125 - 8000007D

  • D_CRL_BAD_CONTENT_ENCODING
  • Unrecognized content encoding.
  • The content encoding is not recongnized. Related to the communication between the local machine and the destination server.

126 - 8000007E

  • D_CRL_LOGIN_DENIED
  • Login denied.
  • The remote server denied the login. Related to the communication between the local machine and the destination server.

127 - 8000007F

  • D_CRL_INSTALL_SIGN_CALL_FAILED
  • Signature calls instalation failed.
  • The installation of signature calls have failed. These calls are related to the signature used in the TLS tunnel between the local machine and the destination server. Please generate the debug logs and contact the technical support.

128 - 80000080

  • D_CRL_CERT_LOAD_FAILED
  • Failed to load TLS certificate.
  • Failed to load the TLS certificate stored in the HSM. Please check if the certificate exists in the HSM and if it's name and type (x.509) are correct.

129 - 80000081

  • D_CRL_CHAIN_LOAD_FAILED
  • Failed to load TLS certificate chain.
  • Failed to load the TLS certificate chain stored in the HSM. Please check if the certificate chain exists in the HSM and if it's name and type (X.509 or PKCS#7) are correct.

130 - 80000082

  • D_CRL_PRIVATE_KEY_LOAD_FAILED
  • Failed to load TLS private key.
  • Failed to load the TLS private key stored in the HSM. Please check if the private key exists in the HSM and if it's name is correct.

2001 - 800007D1

  • D_WSASTARTUP
  • Invalid Winsock (Windows Socket) DLL version.
  • The Winsock DLL version is not supported by the HSM client library. Verify the minimum requirements for Windows machines. This error is only valid in Windows platform.

2002 - 800007D2

  • D_MEMORY_ALLOC
  • Memory allocation failure.
  • It was not possible to allocate the requested memory space. Verify available memory for the process and the machine.

1001 - 800003E9

  • D_INVALID_PARAM
  • Invalid parameter passed to the API.
  • The parameter passed to the API is invalid. Verify the passed parameters (e.g. Passing a parameter flag inválida, not passing a key handle when creating a HMAC in DCreateHash, etc.). See logs for more details.

1002 - 800003EA

  • D_INVALID_TYPE
  • Invalid type passed to the API.
  • The parameter type passed to the API is invalid. This is a generic error. Can be related to data types, keys, blobs passed as parameters in APIs at certain situations. (e.g., Use a symmetric key in an asymmetric operation, unsupported output data type, etc.). See logs for more details.

1003 - 800003EB

  • D_INVALID_STATE
  • The handle state is invalid.
  • Invalid handle state. This error can occur when the handle is used without proper initialization. (e.g.: A session cannot execute other operations while in remote log.). See logs for more details.

1004 - 800003EC

  • D_LOGGING_NOT_STARTED
  • Logging not started.
  • Currently not in use.

1005 - 800003ED

  • D_MORE_DATA
  • More data required.
  • The provided buffer passed as a parameter is not big enough to receive all the output data. Verify the called API documentation at the manual and if the API returned the required size for the output buffer. See logs for more details.

1006 - 800003EE

  • D_INVALID_RESPONSE
  • Invalid response from the HSM.
  • The response from the request sent to the HSM is not recognized. A possible cause is that the client library is outdated in relation to the HSM. In this case, download the latest version of the client library. Another possibility is a failure in the HSM (rare). In this case, please, contact support.

1007 - 800003EF

  • D_INVALID_CONTEXT
  • Invalid context.
  • The context (session handle, key handle, etc.) passed to the API is invalid. Most of the times is a invalid session context. Verify if the context is valid, not NULL and properly initialized.

1008 - 800003F0

  • D_KEY_GEN_ERROR
  • Failure at key generation.
  • Currently not in use.

1009 - 800003F1

  • D_KEY_DEL_ERROR
  • Falha ao remover chave.
  • Currently not in use.

1010 - 800003F2

  • D_KEY_NOT_EXISTS
  • Key does not exist.
  • Currently not in use.

1011 - 800003F3

  • D_INVALID_DATA_LENGTH
  • Invalid input data size.
  • The input data/buffer size is invalid. Verify needed values at the called API documentation. See logs for more details.

1012 - 800003F4

  • D_INVALID_KEY_ALG
  • Invalid key algorithm.
  • The used key algorithm is invalid to this operation. Possible causes: use a symmetric key in asymmetric key operations (vice versa), etc. Verify the passed key type, the called API documentation and cryptography foundations for the correct use of the keys. See logs for more details.

1013 - 800003F5

  • D_INVALID_PADDING
  • Invalid padding.
  • The requested padding type for the API is invalid/not recognized. Verify the passed padding type and the documentation for the accepted padding type. See logs for more details.

1014 - 800003F6

  • D_INVALID_KEY
  • Invalid key.
  • The key passed to the API is not valid or is not suitable for this use. Verify if: the key context is not NULL, the key context is properly initialized, the algorithm is suitable for the operation. See the called API documentation about the accepted key types. See logs for more details.

1015 - 800003F7

  • D_BAD_DATA
  • Invalid input data.
  • The input data is invalid or is corrupted. See API documentation for the proper input data. See logs for more details.

1016 - 800003F8

  • D_INVALID_PUBKEY
  • Invalid public key.
  • The public key used in this operation is invalid or could not be used. Possible causes: invalid key format, unavailable public key, inconsistent/corrupted key, etc. See logs for more details.

1017 - 800003F9

  • D_INVALID_ALG_ID
  • Invalid algorithm.
  • The algorithm used is invalid for this operation. The algorithm can be any accepted HSM object. The algorithm can be valid, but invalid for certain operations. See API documentation for accepted algorithms. See logs for more details.

1018 - 800003FA

  • D_INVALID_HASH
  • Invalid hash.
  • The hash handle passed to the API is invalid. Possible causes: NULL hash handle, not initialized hash handle, etc.

1019 - 800003FB

  • D_INIT_HASH_FAILED
  • Failed to initiate hash operation.
  • The hash operation could not be initialized (rare). See logs for more details. Contact support.

1020 - 800003FC

  • D_INVALID_HASH_STATE
  • Invalid hash state.
  • The hash state is invalid. Hash operations works in a well-defined fashion of beginning/middle/end. Operations that do not follow this sequence can fail by this error. (e.g.: Finalize a hash operation that was not initialized or was already finalized, etc.). See API documentation for the proper use information. See logs for more details.

1021 - 800003FD

  • D_END_HASH_FAILED
  • Failed to end hash operation.
  • Hash operation has failed. Possible causes: internal error or server error. See client and HSM logs for more details.

1022 - 800003FE

  • D_GET_INFO_ERROR
  • Failed to recover HSM informations.
  • The client failed to recover HSM information. Possible causes: server error. See HSM logs for more details.

1023 - 800003FF

  • D_INVALID_PIN_LEN
  • Invalid PIN length.
  • The PIN length is invalid. (e.g.: Backup PIN length is smaller or bigger than the accepted.). See API documentation for more format details. See logs for more details.

1025 - 80000401

  • D_OPEN_FILE_FAILED
  • Failed to open local machine file.
  • The name/path of the file passed as an parameter cannot be opened/created. Possible causes: file access permissions, file path, etc. See logs for more details.

1026 - 80000402

  • D_BACKUP_FAILED
  • Failed to backup HSM.
  • The HSM backup operation has failed. Possible causes: HSM error. See HSM and client library logs for more details.

1027 - 80000403

  • D_RESTORE_FAILED
  • Failed to restore HSM.
  • Currently not in use.

1028 - 80000404

  • D_INVALID_CALLBACK
  • Invalid callback function.
  • Callback function is invalid. See API documentation. Verify if it's not NULL. See logs for more details.

1029 - 80000405

  • D_NOT_IMPLEMENTED
  • Functionality not implemented.
  • The requested functionality is not implemented. Verify if the latest client library it's installed. See API documentation.

1030 - 80000406

  • D_AUTH_FAILED
  • Authentication failed.
  • The authentication in this operation has failed. Verify user/password/OTP, or any password or credential passed to this function call. See HSM and client library for more details.

1031 - 80000407

  • D_INVALID_CLEAR_OP
  • Invalid clear session operation.
  • This operation cannot be executed in a clear session (insecure). Restart the operation using a encrypted session (secure).

1032 - 80000408

  • D_CHANGE_PWD_ERROR
  • Failed to change user's password.
  • The user's password change operation has failed. Possible causes: password does not follow HSM's password policy. See HSM logs for more details.

1033 - 80000409

  • D_PWD_SIZE_ERROR
  • Invalid password size.
  • The password size is invalid. See documentation about the allowed size of the password. See logs for more details.

1034 - 8000040A

  • D_IMPORT_KEY_ERROR
  • Failed to import key.
  • Currently not in use.

1035 - 8000040B

  • D_INVALID_KEY_ID
  • Invalid key name.
  • The key name is invalid. Key names must follow the rules defined in the HSM's manual.

1036 - 8000040C

  • D_INVALID_FLAG
  • Invalid flag passed to the API.
  • The flag passed to the API is invalid. Possible causes: old client library version that doesn't support the flag, invalid flag, etc. See API documentation for flags details. See logs for more details.

1037 - 8000040D

  • D_INVALID_SIGNATURE
  • Invalid signature.
  • The signature verification has failed. The public key was found and used but the verification of the containing signature data didn't match the expected result. See logs for more details.

1038 - 8000040E

  • D_INVALID_PUB_KEY
  • Invalid public key.
  • Currently not in use.

1039 - 8000040F

  • D_INVALID_KEY_STATE
  • Invalid key state.
  • The state of the key is invalid for the requested operation. See logs for more details.

1040 - 80000410

  • D_CREATE_USER_ERROR
  • Failed to create user.
  • Currently not in use.

1041 - 80000411

  • D_NO_MORE_OBJECT
  • No more objects to receive from HSM.
  • Internal error. Please, contact support.

1042 - 80000412

  • D_PUT_ENV_VAR_FAILED
  • Failed to set environment variable.
  • The creation of the environment variable has failed. See logs for more details.

1043 - 80000413

  • D_INVALID_FILE_SIZE
  • Invalid file size.
  • The size of the file passed to the API is invalid to this operation. E.g.: When passing a file bigger than the allowed to be written to the HSM, this error will be returned. See logs for more details.

1044 - 80000414

  • D_INVALID_TEXT_SIZE
  • Invalid text size.
  • Currently not in use.

1045 - 80000415

  • D_FILE_ACCESS_ERROR
  • Failed to access file.
  • The access to the file has failed. Verify access permissions. See logs for more details.

1046 - 80000416

  • D_INVALID_COUNTER
  • Invalid counter.
  • Currently not in use.

1047 - 80000417

  • D_INVALID_MODE
  • Invalid encryption mode.
  • The requested encryption mode is invalid for this operation. Verify if the requested encryption mode is accepted for this operation. See API documentation for the acceptable modes. See logs for more details.

1048 - 80000418

  • D_INVALID_STRUCT_ID
  • Invalid structure ID.
  • Currently not in use.

1049 - 80000419

  • D_INVALID_IP_ADDRESS
  • Invalid IP Address.
  • Currently not in use.

1050 - 8000041A

  • D_GET_PEER_IP_ERROR
  • Failed to get peer IP address.
  • Currently not in use.

1051 - 8000041B

  • D_CERTIFICATE_PARSE_FAILED
  • Failed to parse certificate.
  • The certificate parse has failed. This failure can occur when decoding a certificate at X.509 level or in a specific expected certificate data (e.g.: SPB certificates where specific fields are necessary.). See API documentation for acceptable types. See logs for more details.

1052 - 8000041C

  • D_INVALID_KEY_PART_1
  • Invalid key part 1.
  • The first part of the key is invalid. The KCV (Key Check Value) of the first Visa ZCMK (Zone Control Master Key) component is invalid. Verify typing of the key or KCV.

1053 - 8000041D

  • D_INVALID_KEY_PART_2
  • Invalid key part 2.
  • The second part of the key is invalid. The KCV (Key Check Value) of the second Visa ZCMK (Zone Control Master Key) component is invalid. Verify typing of the key or KCV.

1054 - 8000041E

  • D_INVALID_KEY_PART_3
  • Invalid key part 3.
  • The third part of the key is invalid. The KCV (Key Check Value) of the third Visa ZCMK (Zone Control Master Key) component is invalid. Verify typing of the key or KCV.

1055 - 8000041F

  • D_VERIFY_DAC_FAILED
  • DAC verification failed.
  • Failed to verify DAC (Data Authentication Code). The informed DAC is not the expected one. See the API documentation for more details.

1056 - 80000420

  • D_DEPRECATED
  • This functionality is deprecated.
  • The requested functionality is not supported anymore.

1057 - 80000421

  • D_NO_MATCHING_KEY_FOUND
  • No matching key found.
  • Currently not in use.

1058 - 80000422

  • D_CALLBACK_ERROR
  • Callback function failed.
  • Currently not in use.

1059 - 80000423

  • D_INTERNAL_ERROR
  • Internal failure.
  • This failure can occur for many internal reasons. See logs for more details.

1060 - 80000424

  • D_KEY_NOT_EXPORTABLE_ERROR
  • The key is not exportable.
  • The requested operation is trying to export a non-exportable key.

1062 - 80000426

  • D_INVALID_SPB_ID
  • Invalid SPB ID.
  • The passed SPB ID is invalid. Please verify the proper format at the API documentation.

1063 - 80000427

  • D_JSON_PARSE_ERROR
  • The JSON parse has failed.
  • Failed when trying to parse JSON. See logs for more details.

1064 - 80000428

  • D_JSON_PARSE_WRONG_TYPE_ERROR
  • The JSON parse has failed because of a wrong type request.
  • Failed when trying to parse JSON. The the data type differs from the expected by the requested operation. i.e.: Requesting a string from a int data type. See logs for more details.

1065 - 80000429

  • D_JSON_SET_VALUE_ERROR
  • The JSON has failed to set new value to object.
  • Failed to set new value to JSON object. See logs for more details.

1066 - 8000042A

  • D_JSON_UNSET_VALUE_ERROR
  • The JSON has failed to unset the value from the object.
  • Failed to unset the value from the JSON object. See logs for more details.

1067 - 8000042B

  • D_JSON_VALUE_NOT_FOUND
  • The JSON value was not found in the requested object.
  • Failed locate the value in the JSON object. See logs for more details.

1068 - 8000042C

  • D_JSON_OBJ_CREATE_ERROR
  • The JSON object could not be created.
  • Failed JSON object. See logs for more details.

1069 - 8000042D

  • D_SLP_PARSE_ERROR
  • Failed to parse server SLP response.
  • The server SLP response could not be parsed as expected. See logs for more details.

1070 - 8000042E

  • D_SLP_INTERNAL_ERROR
  • Failed to execute SLP operation.
  • The SLP operation was not successfully executed. See logs for more details.

1071 - 8000042F

  • D_SLP_TOO_MANY_SERVERS_ERROR
  • Failure due to excessive HSM server responses.
  • The number of HSM server SLP responses exceeded the limits. See logs for more details.

1072 - 80000430

  • D_INVALID_SERVER_VERSION
  • The server version is not compatible with the operation.
  • This operation failed because the server does not have a compatible firmware version. See logs for more details.

1073 - 80000431

  • D_GENERATE_PKCS12_ERROR
  • Failed to generate PKCS#12.
  • The PKCS#12 package gereration have failed. See logs for more details.

1074 - 80000432

  • D_SET_LOAD_BALANCE_LIST_ERROR
  • Failed to set load balance list.
  • The load balance list could not be set. See logs for more details.

1075 - 80000433

  • D_OATH_BLOB_UPDATE
  • The OATH blob must be updated.
  • This OATH blob must be updated. See OATH_CHECK_UPDATE_BLOB flag in the API documentation. See API documentation for more details.

1076 - 80000434

  • D_GZIP_DEFLATE_ERROR
  • Failed to deflate buffer.
  • Failed to compress buffer using gzip. See logs for more details.

1077 - 80000435

  • D_HTTP_UNEXPECTED_STATUS_CODE
  • Unexpected HTTP status code.
  • The returned HTTP status code is not expected. See logs for more details.

1078 - 80000436

  • D_BASE64_ERROR
  • Base64 error.
  • Failed to do base64 operation. This error is related to encode and decode operations. See logs for more details.

1079 - 80000437

  • D_SC_READER_NOT_READY
  • Smart-card reader is not ready.
  • Check if the smart-card reader is connected and ready to use and the smart-card is inserted.

1080 - 80000438

  • D_SC_NOT_FORMATTED
  • Smart-card is not formatted.
  • Please, format the card before use.

1081 - 80000439

  • D_SC_INVALID_PIN
  • Smart-card PIN is invalid.
  • Verify if the PIN is correct and try again.

1082 - 8000043A

  • D_SC_READ_FAILED
  • Smart-card read operation failed.
  • Verify if the smart-card is compatible. Please contact support.

1083 - 8000043B

  • D_SC_UNEXPECTED_SVMK_STATUS
  • Unexpected smart-card SVMK status.
  • Verify if the smart-card is written with a valid m of n SVMK.

1084 - 8000043C

  • D_SC_FAILED_USB_LIB_LOAD
  • Failed to load USB library.
  • Verify if the USB library is installed and the user has permission to access it.

1085 - 8000043D

  • D_SC_INVALID_ATR_LEN
  • Invalid ATR length.
  • Invalid ATR (Answer To Reset) size. Verify if the smart-card is compatible.

1086 - 8000043E

  • D_SC_PIN_LOCKED
  • PIN blocked.
  • PIN cannot be changed.

1087 - 8000043F

  • D_SC_KATS_NEGOTIATION_FAILED
  • KATS negotiation failed.
  • KATS negotiation failed. Verify if the smart-card is compatible.

1088 - 80000440

  • D_SC_CHANGE_PIN_FAILED
  • PIN change failed.
  • Failed to change PIN. Verify if the PIN is 8 digits and if the smart-card is compatible.

1089 - 80000441

  • D_INVALID_DATA_FORMAT
  • Data format is invalid.
  • Data format is invalid. Verify if the data is compabtible with the API documentation.

1090 - 80000442

  • D_SC_FREEZE_FAILED
  • Freeze operation failed.
  • Failed to freeze smart-card PIN. Verify if the smart-card is compatible or try again.

1091 - 80000443

  • D_SC_LEGACY_CARD_NOT_SUPPORTED
  • Legacy card is not supported.
  • Legacy smart-card is not supported. Verify if the smart-card is compatible.

1092 - 80000444

  • D_SC_WOULD_OVERWRITE_SVMK
  • This operation would overwrite the card's SVMK.
  • This operation would overwrite the smart-card's SVMK. If you want to proceed, use the overwrite flag.

1093 - 80000445

  • D_SC_INVALID_SVMK_TYPE
  • This operation would overwrite the card's SVMK.
  • This operation would overwrite the smart-card's SVMK. If you want to proceed, use the overwrite flag.

1094 - 80000446

  • D_SC_WRITE_FAILED
  • Failed to write to card.
  • Failed to write to smart-card. Verify if the smart-card is compatible or try again.

1095 - 80000447

  • D_SC_ERASE_FAILED
  • Erase card failed.
  • Failed to erase smart-card data. Verify if the smart-card is compatible or try again.

1096 - 80000448

  • D_SC_SELECT_FAILED
  • Select operation failed.
  • Failed in select operation on smart-card. Verify if the smart-card is compatible or try again.

1097 - 80000449

  • D_INVALID_HSM_OP_MODE
  • Invalid HSM operation mode.
  • This functionality is not supported in this HSM operation mode. See API documentation for more details.

3001 - 80000BB9

  • D_KEEP_ALIVE_ERROR
  • Keep alive error.
  • Currently not in use.

3002 - 80000BBA

  • D_RECEIVE_LOG_ERROR
  • Failed to receive logs.
  • The remote monitoring logs receival has failed. Possible causes: HSM error. See HSM logs for more details.

3003 - 80000BBB

  • D_ERROR_NOTIFY
  • Notification failure from server.
  • This error is a generic error. See logs for more details.