Skip to main content

Secure Sockets Layer (SSL) return codes / Secure Sockets Layer / SSL

Secure Sockets Layer (SSL) return codes
========================================

The table in this appendix documents the return codes, in decimal form, from the Secure Sockets Layer (SSL) that can be returned in messages from the distributed queuing component.

If the return code is not listed, or if you want more information, refer to the IBM Global Security Kit return codes here:

Table 1. SSL return codesReturn code (decimal) Explanation

1 Handle is not valid.
3 An internal error has occured.
4 Insufficient storage is available
5 Handle is in the incorrect state.
6 Key label is not found.
7 No certificates available.
8 Certificate validation error.
9 Cryptographic processing error.
10 ASN processing error.
11 LDAP processing error.
12 An unexpected error has occurred.
102 Error detected while reading key database or SAF key ring.
103 Incorrect key database record format.
106 Incorrect key database password.
109 No certification authority certificates.
201 No key database password supplied.
202 Error detected while opening the key database.
203 Unable to generate temporary key pair
204 Key database password is expired.
302 Connection is active.
401 Certificate is expired or is not valid yet.
402 No SSL cipher specifications.
403 No certificate received from partner.
405 Certificate format is not supported.
406 Error while reading or writing data.
407 Key label does not exist.
408 Key database password is not correct.
410 SSL message format is incorrect.
411 Message authentication code is incorrect.
412 SSL protocol or certificate type is not supported.
413 Certificate signature is incorrect.
414 Certificate is not valid.
415 SSL protocol violation.
416 Permission denied.
417 Self-signed certificate cannot be validated.
420 Socket closed by remote partner.
421 SSL V2 cipher is not valid.
422 SSL V3 cipher is not valid.
427 LDAP is not available.
428 Key entry does not contain a private key.
429 SSL V2 header is not valid.
431 Certificate is revoked.
432 Session renegotiation is not allowed.
433 Key exceeds allowable export size.
434 Certificate key is not compatible with cipher suite.
435 Certification authority is unknown.
436 Certificate revocation list cannot be processed.
437 Connection closed.
438 Internal error reported by remote partner.
439 Unknown alert received from remote partner.
501 Buffer size is not valid.
502 Socket request would block.
503 Socket read request would block.
504 Socket write request would block.
505 Record overflow.
601 Protocol is not SSL V3 or TLS V1.
602 Function identifier is not valid.
701 Attribute identifier is not valid.
702 The attribute has a negative length, which is invalid.
703 The enumeration value is invalid for the specified enumeration type.
704 Invalid parameter list for replacing the SID cache routines.
705 The value is not a valid number.
706 Conflicting parameters were set for additional certificate validation
707 The AES cryptographic algorithm is not supported.
708 The PEERID does not have the correct length.
1501 GSK_SC_OK
1502 GSK_SC_CANCEL
1601 The trace started successfully.
1602 The trace stopped successfully.
1603 No trace file was previously started so it cannot be stopped.
1604 Trace file already started so it cannot be started again.
1605 Trace file cannot be opened. The first parameter of gsk_start_trace() must be a valid full pathfilename.

Comments

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201

IBM WebSphere MQ – Common install/uninstall issues for MQ Version on Windows - Middleware News

Creating a log file when you install or uninstall WebSphere MQ WebSphere MQ for Windows is installed using the Microsoft Installer (MSI). If you install the MQ server or client through launchpad , MQPARMS or setup.exe , then a log file is automatically generated in %temp% during installation. Alternatively you can supply parameters on the installation MSI command msiexec to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). If you uninstall through the Windows Add/Remove programs option, no log file is generated. You should either uninstall from the MSI command line and supply parameters to generate a log file, or enable MSI logging system-wide (which generates MSI logs for all install and uninstall operations). For details on how to enable MSI logging, see the following article in the WebSphere MQ product documentation: Advanced installation using msiexec For details on how to enable system-w