Explanation | Parameter passed into the method was null." |
Action | Rerun the command using a valid parameter. |
Explanation | The specified object does not exist within the management scope. |
Action | Rerun the command with a valid object name. |
Explanation | The specified object already exist. Unable to create another one. |
Action | Create the object with a unique name. |
Explanation | Either a provider/algorithm or a keyManagerClass should be specified not both. |
Action | Rerun the command specifying either a provider/algorithm or a keyManagerClass. |
Explanation | The supplied management scope is not in the correct format or contains information that is not valid. |
Action | Rerun the command with a valid management scope name. |
Explanation | The key store provided is not within the same scope as the key set. |
Action | Rerun the command with a key store that is within the key set's management scope. |
Explanation | The supplied key set object name does not exist. |
Action | Rerun the command with a valid key set object. |
Explanation | The supplied management scope type is not valid. |
Action | Rerun the command with a valid management scope type. Valid types include cell, nodegroup, node, cluster, server, and endpoint. |
Explanation | The supplied management scope does not match the management scope type that was specified. |
Action | Rerun the command with correct management scope type that matches the supplied management scope. |
Explanation | The management scope name supplied already exists in the security configuration. |
Action | Rerun the command with a unique management scope name that does not already exist. |
Explanation | Supplied SSL type is not valid. |
Action | Rerun the command with a valid SSL type - SSSL or JSSE. |
Explanation | Supplied SSL security level is not valid. |
Action | Rerun the command with one of the following valid SSL security levels: HIGH, MEDIUM, LOW, or CUSTOM. |
Explanation | Supplied SSL protocol is not valid. |
Action | Rerun the command with one of the following valid SSL protocols: SSL_TLS, SSL, SSLv2, SSLv3, TLS, or TLSv1. |
Explanation | The supplied trust manager object name is not valid. |
Action | Rerun the command with a valid trust manager object name. |
Explanation | The supplied SSL configuration direction is not valid. |
Action | Rerun the command with a valid SSL configuration direction, inbound or outbound. |
Explanation | The SSL configuration group already exists. |
Action | Rerun the command with a unique SSL configuration group name. |
Explanation | The specified SSL Configuration needs to be in the same management scope as the SSL configuration group being created. |
Action | Rerun the command with an SSL configuration that is in the same management scope as the SSL configuration group being created. |
Explanation | The specified certificate alias is not found in the SSL configuration. |
Action | Rerun the command with a certificate alias that can be found in the configuration. |
Explanation | The specified key alias already exists in the key set. |
Action | Rerun the command with a key alias that does not already exist in the key set. |
Explanation | The password and verify password supplied do not match. |
Action | Rurun the command again a password that matches the verify password. |
Explanation | The specified key store file already exists |
Action | Rerun the command specifying a key store file that does not already exist. |
Explanation | The specified object already exists, it cannot be created again. |
Action | Rerun the command with a unique name that does not already exist. |
Explanation | The specified schedule frequency is not a positive integer. |
Action | Rerun the command using positive integer for the schedule frequency. |
Explanation | The supplied minute value did not fall within the minute range. |
Action | Rerun the command with a minute value between 0 and 59. |
Explanation | The supplied day of week value is out of range. |
Action | Rerun the command with a day of week value between 1 and 7. |
Explanation | The hour value is out of range. |
Action | Rerun the command with a hour value between 0 and 23. |
Explanation | The next start date is set to a date in the past. It needs to be set to a date in the future. |
Action | Rerun the command with a next start date set to a date in the future. |
Explanation | Unable to create a wsCertExpMonitor entry because one already exists. Only one is allowed in the security.xml file at a time. |
Action | Delete the existing wsCertExpMonitor entry and create a new one if a different wsCertExpMonitor is desired. |
Explanation | Valid days parameter is out of range. It should be between 1 and 7300 days. |
Action | Rerun the command with a valid days value between 1 and 7300. |
Explanation | Unable to delete the trust manager because it is still referenced by other objects. |
Action | Make sure the trust manager is not referenced by other objects before deleting it. |
Explanation | Unable to add the certificate to the key store because the key store already contains a certificate with the given alias. |
Action | Rerun the command using a unique alias name for the certificate. |
Explanation | The object is not in the management scope. |
Action | Rerun the command using the correct management scope. |
Explanation | Unable to delete the key set because it is still referenced by other objects. |
Action | Make sure the key set is not referenced by other objects before deleting it. |
Explanation | Unable to generate keys since there is no key generator class configured. |
Action | Configure a key generator class for the key set so that keys can be generated. |
Explanation | One of the objects supplied as input is not a valid key set object. |
Action | Rerun the command making sure the key set object name supplied is valid. |
Explanation | Unable to delete the management scope because it is still referenced by other objects. |
Action | Make sure the management scope is not referenced by other objects before deleting it. |
Explanation | Unable to modify the descriptive property without the correct object parent information. |
Action | Rerun the command with a valid parent data type value. |
Explanation | Unable to modify the descriptive property without the correct class name. |
Action | Rerun the command with a valid class name value. |
Explanation | Unable to modify the descriptive property without the correct descriptive property name. |
Action | Rerun the command with a correct descriptive property name value. |
Explanation | Unable to modify the correct descriptive property without the correct descriptive property type. |
Action | Rerun the command with a correct descriptive property type value. |
Explanation | Information about when the certificate will expire. |
Action | none. |
Explanation | Information about when the certificate will expire. |
Action | none. |
Explanation | Information that the certificate is replaced. |
Action | none. |
Explanation | Information that the certificate is replaced. |
Action | none. |
Explanation | Information that the certificate is deleted. |
Action | none. |
Explanation | Information that the certificate is deleted. |
Action | none. |
Explanation | Information about certificate expiration. |
Action | none. |
Explanation | Information about action taken during certificate expiration monitoring. |
Action | none. |
Explanation | Unable to perform operation on the specified alias because it does not exist in the key store. |
Action | Rerun the command using a certificate alias that exists for the key store. |
Explanation | Unable to perform operation on the specified alias because it is not a certificate request. |
Action | Rerun the command using a certificate request. |
Explanation | Unable to perform operation because the certificate file does not exist. |
Action | Rerun the command using a valid certificate file. |
Explanation | Unable to perform operation because a key for the alias specified does not exist. |
Action | Rerun the command using a valid certificate alias the contains a key. |
Explanation | Unable to receive the certificate from the certificate authority because public keys do not match. |
Action | Rerun the command using a certificate retrieved from a certificate authority that was generated with the certificate request coming form this specified alias in this key store. |
Explanation | Unable to receive the certificate from the certificate authority because public keys do not match. |
Action | Rerun the command using a certificate retrieved from a certificate authority that was generated with the certificate request coming form this specified alias in this key store. |
Explanation | The key store file did not verify. The file may not exist or the key file type or password is not correct. |
Action | Rerun the command with a key store that exists and check that the key file type and password are valid. |
Explanation | The SSL Configuration must be within the Dynamic SSL Configuration Selection management scope. |
Action | Rerun the command with a SSL Configuration that is within the same management scope of the Dynamic SSL Configuration Selection management scope. |
Explanation | The key store being created is a hardware key store and a hardware crypto key store type must be specified. |
Action | Rerun the command with a valid hardware crypto key store type. |
Explanation | Only a positive integer can be used for a hardware slot number. |
Action | Rerun the command using a positive integer for a hardware slot number. |
Explanation | Only a positive number can be used for next start date. |
Action | Rerun the command using a positive number for next state date. |
Explanation | The signer certificate was not retrieved, verify the hostname and port are correct. |
Action | Rerun the command after verifying the hostname is valid and the port is a secure port. |
Explanation | In order to receive a certificate in a key store the public key of the certificate must match the public key of a certificate in the key store. |
Action | Rerun the command with a certificate that has a public key that matches the public key of a certificate in the key store. |
Explanation | When creating a key store object with an existing key store file the file or keyring must exist and a valid password and key store type must be supplied. |
Action | Make sure the key store file or keyring exists with a valid password and key store type. Then rerun the command. |
Explanation | When creating a key store used for hardware acceleration the configuration file must exist. |
Action | Make sure the key store acceleration configuration file exists and rerun the command. |
Explanation | When creating a key store that is not file based the file path specified must exist. |
Action | Make sure the file specified exists and rerun the command. |
Explanation | The certificate specified is not a personal certificate. |
Action | Rerun the command with a personal certificate alias name. |
Explanation | There is already a property by the specified name in the SSL Configuration. |
Action | Rerun the command with a property that does not already exist in the SSL Configuration. |
Explanation | The value is not the type specified. |
Action | Rerun the command making sure the value matches the type supplied. |
Explanation | Remotely managed key stores can only be done on a deployment manager. |
Action | Only locally manage key stores can be managed on a base application server. |
Explanation | Key stores that are read only or key stores that are not file based cannot be changed. |
Action | Unable to perform password change operation on read only key store or key store that is not file based. |
Explanation | The key store file did not verify. The file may not exist or the key file type or password is not correct. |
Action | Rerun the command with a key store that exists and check the key file type and password. |
Explanation | The alias is either not in the key store or it is not a personal certificate in the key store. |
Action | Rerun the command with a personal certificate that is located in the key store. |
Explanation | When creating a hardware key store object the file in the path specified should already exist. |
Action | Rerun the command with a specifying a file that already exists. |
Explanation | The two alias values supplied are the same. The alias values must be different. |
Action | Rerun the command by specifying different alias values. |
Explanation | The value is not a valid configuration object name. |
Action | Rerun the command with a valid configuration object name. |
Explanation | The task is missing a parameter required to run. |
Action | Rerun the command with the correct parameters and values. |
Explanation | The task is missing parameters required to run. |
Action | Rerun the command with the correct parameters and values. |
Explanation | Unable to perform operation on the specified alias because it does not exist in the key store. |
Action | Rerun the command using a certificate alias that exists in the key store. |
Explanation | Information about when the certificate expired. |
Action | none. |
Explanation | Information about when the certificate expired. |
Action | none. |
Explanation | Information parameter is not formatted correctly. It should be in the 'protocol,host,port' format. |
Action | Rerun the command with correct format for the Dynamic SSL configuration selection information parameter. |
Explanation | The specified alias does not exist. |
Action | Rerun the command with a valid alias name. |
Explanation | The time out value range should be between 1 and 86400. |
Action | Rerun the command with a valid time out range between 1 and 86400. |
Explanation | When the sendEmail option value is true, a list of e-mail addresses must be provided. |
Action | Specify a list of e-mail addresses if sendEmail option is set to true and then re-run the command. |
Explanation | When you specify the "emailFormat" option the valid values include "html" or "text". |
Action | Specify "html" or "text" for the e-mail format and re-run the command.. |
Explanation | When you request a new certificate, the minimum Distinguished Name (DN) information is required. |
Action | Specify a value with the certificateCommonName parameter and re-run the command.. |
Explanation | The Certificate Authority client is still referenced by one or more certificates. |
Action | First, remove all of the certificates that reference the Certificate Authority (CA) client. Then, remove the CA client. |
Explanation | To revoke a certificate, the certificate must have a reference object in the security configuration. |
Action | Only revoke certificates that are CA certificates and have a reference object in the security configuration. |
Explanation | The certificate must exist for it to be revoked. |
Action | Run the revoke certificate task on an existing Certificate Authority (CA) certificate. |
Explanation | The certificate request must exist to request a certificate from a Certificate Authority (CA). |
Action | Run the certificate request task with a predefined certificate request or have the command create a request. |
Explanation | A certificate request already exists and information was provided to create a new request. |
Action | Rerun the command using the existing certificate request or use a new unique alias with DN information. |
Explanation | The certificate status needs to be in the PENDING state to make a request to the Certificate Authority (CA) to complete the certificate. |
Action | Run the command on certificates in the PENDING state. |
Explanation | The keystore file does not exist, but it must exist. |
Action | The command needs to run with an existing keystore file. |
Explanation | A valid key storetype must be provided to load the keystore. The specified key storetype is not valid for this configuration. |
Action | Run the command with a valid keystore type for this configuration. |
Explanation | An error occurred when the Application Server attempted to load the keystore. Verify the password and make sure the correct keystore type is provided for the keystore. |
Action | Run the command with all the correct information needed to load the key store. |
Explanation | The specified alias name either does not exist in the key store or it is not a personal certificate. |
Action | Run the command using a personal certificate alias that exists in the keystore. |
Explanation | The parameter value is not a positive integer. |
Action | Run the command using a positive integer. |
Explanation | To modify the keystore reference in the key store object, provide a location, type and password. |
Action | Run the command with the keyStoreLocation, keyStoreType, and keyStorePassword parameters. |
Explanation | The keystore is marked as read-only access. The Application Server cannot perform any operation that will write to the keystore file. |
Action | "Only run the command on a keystore that is not marked read-only. |
Explanation | The specified port value is not valid. |
Action | Run the command using a valid port number. |
Explanation | A certificate can be used to sign other certificates only if the basic constraint flag on the certificate is set to true. |
Action | Ensure that the specified certificate is a certificate authority (CA) certificate, it exists, and it was created in the default root keystore. Only self-signed certificates that are created in the default root keystore have the basic contraint flag set to true. |
Explanation | CA certificates must be deleted and re-requested manually using the administrative tasks. |
Action | To obtain a new CA certificate, manually delete the old certificate and manually request a new certificiate from the certificate authority. |
Explanation | Certificates that are not issued by the product cannot be renewed. The certificate must be renewed manually. |
Action | To obtain a new certificate that was not issued by a node in the product, the old certificate must be manually deleted. A new certificate must be manually requested from the external source from which it first originated. |
Explanation | This message is for informational purposes only. |
Action | none. |
Explanation | The root certificate, which was originally used to sign the certificate, does not exist. The certificate might have been deleted from the keystore. |
Action | Check the deleted keystore to ensure that the certificate was not accidentally deleted. If the certificate is in the deleted keystore, you can restore it using an import or export command. |
Explanation | The task should either work with another keystore object or work with an unmanaged keystore. However, the task cannot work both approaches. |
Action | Specify either a keystore object name or a key file path name and run the command. |
Explanation | he specified keystore must contain at least one personal certificate.. |
Action | The last personal certificate cannot be removed from the keystore. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The specified usage value is not valid. |
Action | Run the command with a valid usage value. |
Explanation | This message is for informational purposes only. |
Action | No action is required.. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The SAF keyring location is not valid. Specify the location in the following form: safkeyring://USERID/KeyringName or safkeyring:///KeyringName. |
Action | Modify the keystore location parameter to point to a valid location. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The task is missing a required parameter. |
Action | Specify the correct parameter and value and rerun the command. |
Explanation | The administrative agent and the job manager have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure the enablement status for the two profiles match. |
Explanation | The administrative agent and the job manager have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure that the enablement status for the two profiles match. |
Explanation | The administrative agent and base profile have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure that the enablement status for the two profiles match. |
Explanation | The administraive agent and base profile have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure that the enablement status for the two profiles match. |
Explanation | The keystore must be marked read-only access. The Application Server cannot perform any operation that will write to the keystore location. |
Action | Run the command on a keystore with a keyring location qualified with a valid RACF user. |
Explanation | The keystore specified is already enabled as a writable keyring. |
Action | Ensure the keystore is not already enabled as a writable keyring before running the command. |
Explanation | A valid replacement option needs to be specified. |
Action | Specify a valid replacement option value and rerun the command. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | An error occurred when the Application Server attempted to create the keystore. |
Action | Verify that the type, password, and file or key ring location are correct. Rerun the command with the correct parameters and values. |
Explanation | To import or export certificates from an audit keystore, the user must have the required auditor role authority. |
Action | Ensure that the acting user has the proper role authority. |
Explanation | The deployment manager and the job manager have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure that the enablement status for the two profiles match. |
Explanation | The deployment manager and the job manager have separate security configurations. The security enablement status must match before federation continues and security is properly applied. |
Action | Ensure that the enablement status for the two profiles match. |
Explanation | There is a failure to connect with the job manager. Make sure the job manager is running. This could be due to security being enabled on the job manager but not on the server registering with it or due to a incorrect username, password, port number, or hostname. |
Action | Ensure the job manager is running, the enablement status for the two profiles match, and that the user, password, port number, and hostname information is correct. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |