The IBM® Tivoli® Storage Manager server and client use the IBM Global Security Kit (GSKit) for SSL (Secure Sockets Layer) processing between the Tivoli Storage Manager server and the backup-archive client. Some messages that are issued for SSL processing include GSKit return codes.
regedit /e gskitinfo.txt "HKEY_LOCAL_MACHINE\software\ibm\gsk8\"
notepad gskitinfo.txtSee Table 1 for the GSKit SSL return codes.
The Tivoli Storage Manager server uses the GSKit Key Management API to automatically create the key management database and Tivoli Storage Manager server private and public keys. Some messages that are issued for this processing might include GSKit Key Management return codes. See Table 2 for the key management return codes.
| Return code (hex) | Return code (decimal) | Constant | Explanation |
|---|---|---|---|
| 0x00000000 | 0 | GSK_OK | The task completes successfully. Issued by every function call that completes successfully. |
| 0x00000001 | 1 | GSK_INVALID_HANDLE | The environment or SSL handle is not valid. The specified handle was not the result of a successful open() function call. |
| 0x00000002 | 2 | GSK_API_NOT_AVAILABLE | The dynamic link library (DLL) was unloaded and is not available (occurs on Microsoft Windows systems only). |
| 0x00000003 | 3 | GSK_INTERNAL_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000004 | 4 | GSK_INSUFFICIENT_STORAGE | Insufficient memory is available to complete the operation. |
| 0x00000005 | 5 | GSK_INVALID_STATE | The handle is not in a valid state for operation, such as completing an init() operation on a handle twice. |
| 0x00000006 | 6 | GSK_KEY_LABEL_NOT_FOUND | Specified key label is not found in key file. |
| 0x00000007 | 7 | GSK_CERTIFICATE_NOT_AVAILABLE | Certificate is not received from the partner. |
| 0x00000008 | 8 | GSK_ERROR_CERT_VALIDATION | Certificate validation error. |
| 0x00000009 | 9 | GSK_ERROR_CRYPTO | Error processing cryptography. |
| 0x0000000a | 10 | GSK_ERROR_ASN | Error validating ASN fields in certificate. |
| 0x0000000b | 11 | GSK_ERROR_LDAP | Error connecting to user registry. |
| 0x0000000c | 12 | GSK_ERROR_UNKNOWN_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000065 | 101 | GSK_OPEN_CIPHER_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000066 | 102 | GSK_KEYFILE_IO_ERROR | I/O error reading the key file. |
| 0x00000067 | 103 | GSK_KEYFILE_INVALID_FORMAT | The key file does not have a valid internal format. Recreate the key file. |
| 0x00000068 | 104 | GSK_KEYFILE_DUPLICATE_KEY | The key file has two entries with the same key. |
| 0x00000069 | 105 | GSK_KEYFILE_DUPLICATE_LABEL | The key file has two entries with the same label. |
| 0x0000006a | 106 | GSK_BAD_FORMAT_OR_INVALID_PASSWORD | The key file password is used as an integrity check. Either the key file is corrupted or the password ID is incorrect. |
| 0x0000006b | 107 | GSK_KEYFILE_CERT_EXPIRED | The default key in the key file has an expired certificate. |
| 0x0000006c | 108 | GSK_ERROR_LOAD_GSKLIB | An error occurred loading one of the GSK dynamic link libraries. Check that GSK was installed correctly. |
| 0x0000006d | 109 | GSK_PENDING_CLOSE_ERROR | Indicates that a connection is trying to be made in a GSK environment after the GSK_ENVIRONMENT_ CLOSE_OPTIONS was set to GSK_DELAYED_ ENVIRONMENT_CLOSE and gsk_environment_close() function was called. |
| 0x000000c9 | 201 | GSK_NO_KEYFILE_PASSWORD | Both the password and the stash-file name were not specified. The key file is not initialized. |
| 0x000000ca | 202 | GSK_KEYRING_OPEN_ERROR | Unable to open the key file. Either the path was specified incorrectly or the file permissions did not allow the file to be opened. |
| 0x000000cb | 203 | GSK_RSA_TEMP_KEY_PAIR | Unable to generate a temporary key pair. Report this error to IBM Software Support. |
| 0x000000cc | 204 | GSK_ERROR_LDAP_NO_SUCH_OBJECT | A user name object was specified that is not found. |
| 0x000000cd | 205 | GSK_ERROR_LDAP_INVALID_CREDENTIALS | A password that is used for an LDAP (lightweight directory access protocol) query is not correct. |
| 0x000000ce | 206 | GSK_ERROR_BAD_INDEX | An index into the Fail Over list of LDAP servers was not correct. |
| 0x000000cf | 207 | GSK_ERROR_FIPS_NOT_SUPPORTED | This installation of GSKit does not support FIPS mode of operation. |
| 0x0000012d | 301 | GSK_CLOSE_FAILED | Indicates that the GSK environment close request was not properly managed. Cause is most likely due to a gsk_secure_socket*() command that is attempted after a gsk_close_environment() call. |
| 0x00000191 | 401 | GSK_ERROR_BAD_DATE | The system date was not set to a valid value. |
| 0x00000192 | 402 | GSK_ERROR_NO_CIPHERS | The SSLv2 and the SSLv3 are not enabled. |
| 0x00000193 | 403 | GSK_ERROR_NO_CERTIFICATE | The required certificate was not received from the partner. |
| 0x00000194 | 404 | GSK_ERROR_BAD_CERTIFICATE | The received certificate was formatted incorrectly. |
| 0x00000195 | 405 | GSK_ERROR_UNSUPPORTED_CERTIFICATE_TYPE | The received certificate type was not supported. |
| 0x00000196 | 406 | GSK_ERROR_IO | An I/O error occurred on a data read or write operation. |
| 0x00000197 | 407 | GSK_ERROR_BAD_KEYFILE_LABEL | The specified label in the key file is not found. |
| 0x00000198 | 408 | GSK_ERROR_BAD_KEYFILE_PASSWORD | The specified key file password is incorrect. The key file cannot be used. The key file also might be corrupt. |
| 0x00000199 | 409 | GSK_ERROR_BAD_KEY_LEN_FOR_EXPORT | In a restricted cryptography environment, the key size is too long to be supported. |
| 0x0000019a | 410 | GSK_ERROR_BAD_MESSAGE | An incorrectly formatted SSL message was received from the partner. |
| 0x0000019b | 411 | GSK_ERROR_BAD_MAC | The message authentication code (MAC) was not successfully verified. |
| 0x0000019c | 412 | GSK_ERROR_UNSUPPORTED | Unsupported SSL protocol or unsupported certificate type. |
| 0x0000019d | 413 | GSK_ERROR_BAD_CERT_SIG | The received certificate contained an incorrect signature. |
| 0x0000019e | 414 | GSK_ERROR_BAD_CERT | Incorrectly formatted certificate is received from the partner. |
| 0x0000019f | 415 | GSK_ERROR_BAD_PEER | Did not receive a valid SSL protocol from the partner. |
| 0x000001a0 | 416 | GSK_ERROR_PERMISSION_DENIED | Report this error to IBM Software Support. |
| 0x000001a1 | 417 | GSK_ERROR_SELF_SIGNED | The self-signed certificate is not valid. |
| 0x000001a2 | 418 | GSK_ERROR_NO_READ_FUNCTION | The read() failed. Report this error to IBM Software Support. |
| 0x000001a3 | 419 | GSK_ERROR_NO_WRITE_FUNCTION | The write() failed. Report this error to IBM Software Support. |
| 0x000001a4 | 420 | GSK_ERROR_SOCKET_CLOSED | The partner closed the socket before the protocol completed. |
| 0x000001a5 | 421 | GSK_ERROR_BAD_V2_CIPHER | The specified V2 cipher is not valid. |
| 0x000001a6 | 422 | GSK_ERROR_BAD_V3_CIPHER | The specified V3 cipher is not valid. |
| 0x000001a7 | 423 | GSK_ERROR_BAD_SEC_TYPE | Report this error to IBM Software Support. |
| 0x000001a8 | 424 | GSK_ERROR_BAD_SEC_TYPE_COMBINATION | Report this error to IBM Software Support. |
| 0x000001a9 | 425 | GSK_ERROR_HANDLE_CREATION_FAILED | The handle cannot be created. Report this error to IBM Software Support. |
| 0x000001aa | 426 | GSK_ERROR_INITIALIZATION_FAILED | Initialization failed. Report this internal error to service. |
| 0x000001ab | 427 | GSK_ERROR_LDAP_NOT_AVAILABLE | Not able to access the specified user registry when a certificate is being validated. |
| 0x000001ac | 428 | GSK_ERROR_NO_PRIVATE_KEY | The specified key did not contain a private key. |
| 0x000001ad | 429 | GSK_ERROR_PKCS11_LIBRARY_NOTLOADED | A failed attempt was made to load the specified PKCS11 shared library. |
| 0x000001ae | 430 | GSK_ERROR_PKCS11_TOKEN_LABELMISMATCH | The PKCS #11 driver failed to find the token that is specified by the caller. |
| 0x000001af | 431 | GSK_ERROR_PKCS11_TOKEN_NOTPRESENT | A PKCS #11 token is not present in the slot. |
| 0x000001b0 | 432 | GSK_ERROR_PKCS11_TOKEN_BADPASSWORD | The password/pin to access the PKCS #11 token is not valid. |
| 0x000001b1 | 433 | GSK_ERROR_INVALID_V2_HEADER | The SSL header received was not a properly formatted SSLv2 header. |
| 0x000001b2 | 434 | GSK_CSP_OPEN_ERROR | Cannot open the hardware-based cryptographic service provider. Either the CSP name is not specified correctly or a failed attempt was made to access the specified CSP certificate store. |
| 0x000001b3 | 435 | GSK_CSP_OPEN_ERROR | Some conflicting attributes for SSL operation were defined. |
| 0x000001b4 | 436 | GSK_CSP_OPEN_ERROR | The Microsoft Crypto API is only supported on Microsoft Windows 2000 with Service Pack 2 applied. |
| 0x000001b5 | 437 | GSK_CSP_OPEN_ERROR | System is running in IPv6 mode without setting a PEERID. |
| 0x000001f5 | 501 | GSK_INVALID_BUFFER_SIZE | The buffer size is negative or zero. |
| 0x000001f6 | 502 | GSK_WOULD_BLOCK | Used with nonblocking I/O. Refer to the nonblocking section for usage. |
| 0x00000259 | 601 | GSK_ERROR_NOT_SSLV3 | SSLv3 is required for reset_cipher(), and the connection uses SSLv2. |
| 0x0000025a | 602 | GSK_MISC_INVALID_ID | A valid ID was not specified for the gsk_secure_soc_misc() function call. |
| 0x000002bd | 701 | GSK_ATTRIBUTE_INVALID_ID | The function call does not have a valid ID. This issue might also be caused by specifying an environment handle when a handle for an SSL connection should be used. |
| 0x000002be | 702 | GSK_ATTRIBUTE_INVALID_LENGTH | The attribute has a negative length, which is not valid. |
| 0x000002bf | 703 | GSK_ATTRIBUTE_INVALID_ENUMERATION | The enumeration value is not valid for the specified enumeration type. |
| 0x000002c0 | 704 | GSK_ATTRIBUTE_INVALID_SID_CACHE | A parameter list that is not valid for replacing the SID cache routines. |
| 0x000002c1 | 705 | GSK_ATTRIBUTE_INVALID_NUMERIC_VALUE | When a numeric attribute is set, the specified value is not valid for the specific attribute that is being set. |
| 0x000002c2 | 706 | GSK_CONFLICTING_VALIDATION_SETTING | Conflicting parameters were set for additional certificate validation. |
| 0x000002c3 | 707 | GSK_AES_UNSUPPORTED | The AES cryptographic algorithm is not supported. |
| 0x000002c4 | 708 | GSK_PEERID_LENGTH_ERROR | The PEERID does not have the correct length. |
| 0x000002c5 | 709 | GSK_CIPHER_INVALID_WHEN_FIPS_MODE_OFF | The particular cipher is not allowed when FIPS mode of operation is off. |
| 0x000002c6 | 710 | GSK_CIPHER_INVALID_WHEN_FIPS_MODE_ON | No approved FIPS ciphers are selected in FIPS mode of operation. |
| 0x00000641 | 1601 | GSK_TRACE_STARTED | The trace started successfully. |
| 0x00000642 | 1602 | GSK_TRACE_STOPPED | The trace stopped successfully. |
| 0x00000643 | 1603 | GSK_TRACE_NOT_STARTED | No trace file was previously started, so it cannot be stopped. |
| 0x00000644 | 1604 | GSK_TRACE_ALREADY_STARTED | Trace file is started, so it cannot be restarted. |
| 0x00000645 | 1605 | GSK_TRACE_OPEN_FAILED | Trace file cannot be opened. The first parameter of gsk_start_trace() must be a valid full path file name. |
| Return code (hex) | Return code (decimal) | Constant | Explanation |
|---|---|---|---|
| 0x00000000 | 0 | GSK_OK | The task completes successfully. This message is issued by every function call that completes successfully. |
| 0x00000001 | 1 | GSK_INVALID_HANDLE | The environment or SSL handle is not valid. The specified handle was not the result of a successful open() function call. |
| 0x00000002 | 2 | GSK_API_NOT_AVAILABLE | The DLL (dynamic link library) was unloaded and is not available (occurs on Microsoft Windows systems only). |
| 0x00000003 | 3 | GSK_INTERNAL_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000004 | 4 | GSK_INSUFFICIENT_STORAGE | Insufficient memory is available to complete the operation. |
| 0x00000005 | 5 | GSK_INVALID_STATE | The handle is in an incorrect state for operation, such as completing an init() operation on a handle twice. |
| 0x00000006 | 6 | GSK_KEY_LABEL_NOT_FOUND | Specified key label is not found in key file. |
| 0x00000007 | 7 | GSK_CERTIFICATE_NOT_AVAILABLE | Certificate is not received from the partner. |
| 0x00000008 | 8 | GSK_ERROR_CERT_VALIDATION | Certificate validation error. |
| 0x00000009 | 9 | GSK_ERROR_CRYPTO | Error processing cryptography. |
| 0x0000000a | 10 | GSK_ERROR_ASN | Error validating ASN fields in certificate. |
| 0x0000000b | 11 | GSK_ERROR_LDAP | Error connecting to user registry. |
| 0x0000000c | 12 | GSK_ERROR_UNKNOWN_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000065 | 101 | GSK_OPEN_CIPHER_ERROR | Internal error. Report this error to IBM Software Support. |
| 0x00000066 | 102 | GSK_KEYFILE_IO_ERROR | I/O error reading the key file. |
| 0x00000067 | 103 | GSK_KEYFILE_INVALID_FORMAT | The key file has an internal format that is not valid. Recreate key file. |
| 0x00000068 | 104 | GSK_KEYFILE_DUPLICATE_KEY | The key file has two entries with the same key. |
| 0x00000069 | 105 | GSK_KEYFILE_DUPLICATE_LABEL | The key file has two entries with the same label. |
| 0x0000006a | 106 | GSK_BAD_FORMAT_OR_INVALID_ PASSWORD | The key file password is used as an integrity check. Either the key file is corrupted or the password ID is incorrect. |
| 0x0000006b | 107 | GSK_KEYFILE_CERT_EXPIRED | The default key in the key file has an expired certificate. |
| 0x0000006c | 108 | GSK_ERROR_LOAD_GSKLIB | An error occurred while one of the GSK dynamic link libraries is loaded. Check GSK was installed correctly. |
| 0x0000006d | 109 | GSK_PENDING_CLOSE_ERROR | This message indicates that a connection is trying to be made in a GSK environment after the GSK_ENVIRONMENT_ CLOSE_OPTIONS was set to GSK_DELAYED_ ENVIRONMENT_CLOSE and gsk_environment_close() function was called. |
| 0x000000c9 | 201 | GSK_NO_KEYFILE_PASSWORD | Both the password and the stash-file name were not specified, so the key file is not initialized. |
| 0x000000ca | 202 | GSK_KEYRING_OPEN_ERROR | Unable to open the key file. Either the path was specified incorrectly or the file permissions did not allow the file to be opened. |
| 0x000000cb | 203 | GSK_RSA_TEMP_KEY_PAIR | Unable to generate a temporary key pair. Report this error to IBM Software Support. |
| 0x000000cc | 204 | GSK_ERROR_LDAP_NO_SUCH_OBJECT | A user name object was specified that is not found. |
| 0x000000cd | 205 | GSK_ERROR_LDAP_INVALID_ CREDENTIALS | A Password that is used for an LDAP query is not correct. |
| 0x000000ce | 206 | GSK_ERROR_BAD_INDEX | An index into the Fail Over list of LDAP servers was not correct. |
| 0x000000cf | 207 | GSK_ERROR_FIPS_NOT_SUPPORTED | This installation of GSKit does not support FIPS mode of operation. |
| 0x0000012d | 301 | GSK_CLOSE_FAILED | Indicates that the GSK environment close request was not properly managed. Cause is most likely due to attempting a gsk_secure_socket*() command after a gsk_close_environment() call. |
| 0x00000191 | 401 | GSK_ERROR_BAD_DATE | The system date was set to a value that is not valid. |
| 0x00000192 | 402 | GSK_ERROR_NO_CIPHERS | SSLv2 and SSLv3 are not enabled. |
| 0x00000193 | 403 | GSK_ERROR_NO_CERTIFICATE | The required certificate was not received from the partner. |
| 0x00000194 | 404 | GSK_ERROR_BAD_CERTIFICATE | The received certificate was formatted incorrectly. |
| 0x00000195 | 405 | GSK_ERROR_UNSUPPORTED_ CERTIFICATE_TYPE | The received certificate type was not supported. |
| 0x00000196 | 406 | GSK_ERROR_IO | An I/O error occurred on a data read-or-write operation. |
| 0x00000197 | 407 | GSK_ERROR_BAD_KEYFILE_LABEL | The specified label in the key file is not found. |
| 0x00000198 | 408 | GSK_ERROR_BAD_KEYFILE_PASSWORD | The specified key file password is incorrect. The key file cannot be used. The key file might also be corrupt. |
| 0x00000199 | 409 | GSK_ERROR_BAD_KEY_LEN_ FOR_EXPORT | In a restricted cryptography environment, the key size is too long to be supported. |
| 0x0000019a | 410 | GSK_ERROR_BAD_MESSAGE | An incorrectly formatted SSL message was received from the partner. |
| 0x0000019b | 411 | GSK_ERROR_BAD_MAC | The MAC was not successfully verified. |
| 0x0000019c | 412 | GSK_ERROR_UNSUPPORTED | Unsupported SSL protocol or unsupported certificate type. |
| 0x0000019d | 413 | GSK_ERROR_BAD_CERT_SIG | The received certificate contained an incorrect signature. |
| 0x0000019e | 414 | GSK_ERROR_BAD_CERT | Incorrectly formatted certificate is received from the partner. |
| 0x0000019f | 415 | GSK_ERROR_BAD_PEER | An SSL protocol that is not valid is received from the partner. |
| 0x000001a0 | 416 | GSK_ERROR_PERMISSION_DENIED | Report this error to IBM Software Support. |
| 0x000001a1 | 417 | GSK_ERROR_SELF_SIGNED | The self-signed certificate is not valid. |
| 0x000001a2 | 418 | GSK_ERROR_NO_READ_FUNCTION | The read() failed. Report this error to IBM Software Support. |
| 0x000001a3 | 419 | GSK_ERROR_NO_WRITE_FUNCTION | The write() failed. Report this error to IBM Software Support. |
| 0x000001a4 | 420 | GSK_ERROR_SOCKET_CLOSED | The partner closed the socket before the protocol completed. |
| 0x000001a5 | 421 | GSK_ERROR_BAD_V2_CIPHER | The specified V2 cipher is not valid. |
| 0x000001a6 | 422 | GSK_ERROR_BAD_V3_CIPHER | The specified V3 cipher is not valid. |
| 0x000001a7 | 423 | GSK_ERROR_BAD_SEC_TYPE | Report this error to IBM Software Support. |
| 0x000001a8 | 424 | GSK_ERROR_BAD_SEC_TYPE_ COMBINATION | Report this error to IBM Software Support. |
| 0x000001a9 | 425 | GSK_ERROR_HANDLE_CREATION_ FAILED | The handle is not created. Report this error to IBM Software Support. |
| 0x000001aa | 426 | GSK_ERROR_INITIALIZATION_FAILED | Initialization failed. Report this internal error to service. |
| 0x000001ab | 427 | GSK_ERROR_LDAP_NOT_AVAILABLE | Unable to access the specified user registry when a certificate is being validated |
| 0x000001ac | 428 | GSK_ERROR_NO_PRIVATE_KEY | The specified key did not contain a private key. |
| 0x000001ad | 429 | GSK_ERROR_PKCS11_LIBRARY_ NOTLOADED | A failed attempt was made to load the specified PKCS11 shared library. |
| 0x000001ae | 430 | GSK_ERROR_PKCS11_TOKEN_ LABELMISMATH | The PKCS #11 driver failed to find the token that is specified by the caller. |
| 0x000001af | 431 | GSK_ERROR_PKCS11_TOKEN_ NOTPRESENT | A PKCS #11 token is not present in the slot. |
| 0x000001b0 | 432 | GSK_ERROR_PKCS11_TOKEN_ BADPASSWORD | The password/pin to access the PKCS #11 token is incorrect. |
| 0x000001b1 | 433 | GSK_ERROR_INVALID_V2_HEADER | The SSL header received was not a properly formatted SSLv2 header. |
| 0x000001b2 | 434 | GSK_CSP_OPEN_ERROR | Could not open the hardware-based cryptographic service provider (CSP). Either the CSP name is not specified correctly or a failed attempt was made to access the specified CSP certificate store. |
| 0x000001b3 | 435 | GSK_CSP_OPEN_ERROR | Some conflicting attributes for SSL operation were defined. |
| 0x000001b4 | 436 | GSK_CSP_OPEN_ERROR | The Microsoft Crypto API is only supported on Microsoft Windows 2000 with Service Pack 2 applied. |
| 0x000001b5 | 437 | GSK_CSP_OPEN_ERROR | System is running in IPv6 mode without setting a PEERID. |
| 0x000001f5 | 501 | GSK_INVALID_BUFFER_SIZE | The buffer size is negative or zero. |
| 0x000001f6 | 502 | GSK_WOULD_BLOCK | Used with nonblocking I/O. Refer to the nonblocking section for usage. |
| 0x00000259 | 601 | GSK_ERROR_NOT_SSLV3 | SSLv3 is required for reset_cipher(), and the connection uses SSLv2. |
| 0x0000025a | 602 | GSK_MISC_INVALID_ID | An ID that is not valid was specified for the gsk_secure_soc_misc() function call. |
| 0x000002bd | 701 | GSK_ATTRIBUTE_INVALID_ID | The function call has an ID that is not valid. This issue might also be caused by specifying an environment handle when a handle for an SSL connection should be used. |
| 0x000002be | 702 | GSK_ATTRIBUTE_INVALID_LENGTH | The attribute has a negative length, which is not valid. |
| 0x000002bf | 703 | GSK_ATTRIBUTE_INVALID_ ENUMERATION | The enumeration value is not valid for the specified enumeration type. |
| 0x000002c0 | 704 | GSK_ATTRIBUTE_INVALID_SID_CACHE | A parameter list that is not valid for replacing the SID cache routines. |
| 0x000002c1 | 705 | GSK_ATTRIBUTE_INVALID_ NUMERIC_VALUE | When a numeric attribute is set, the specified value is not valid for the specific attribute that is being set. |
| 0x000002c2 | 706 | GSK_CONFLICTING_VALIDATION_ SETTING | Conflicting parameters were set for additional certificate validation. |
| 0x000002c3 | 707 | GSK_AES_UNSUPPORTED | The AES cryptographic algorithm is not supported. |
| 0x000002c4 | 708 | GSK_PEERID_LENGTH_ERROR | The PEERID does not have the correct length. |
| 0x000002c5 | 709 | GSK_CIPHER_INVALID_WHEN_FIPS_MODE_OFF | The particular cipher is not allowed when FIPS mode of operation is off. |
| 0x000002c6 | 710 | GSK_CIPHER_INVALID_WHEN_FIPS_MODE_ON | No approved FIPS ciphers are selected in FIPS mode of operation. |
| 0x00000641 | 1601 | GSK_TRACE_STARTED | The trace started successfully. |
| 0x00000642 | 1602 | GSK_TRACE_STOPPED | The trace stopped successfully. |
| 0x00000643 | 1603 | GSK_TRACE_NOT_STARTED | No trace file was previously started so it cannot be stopped. |
| 0x00000644 | 1604 | GSK_TRACE_ALREADY_STARTED | Trace file is started so it cannot be started again. |
| 0x00000645 | 1605 | GSK_TRACE_OPEN_FAILED | Trace file cannot be opened. The first parameter of gsk_start_trace() must be a valid, full-path file name. |