BL Messages
CSIBL0051E The system can't start the configuration database.
Explanation
An error might have occurred during the configuration database connection.
Action
Ensure that the mount point is correct. If it is correct, restart the docker container and try the procedure again. If the problem persists, contact IBM Support team for assistance.
CSIBL0052E The system can't find the id configuration in configuration database.
Explanation
Either the configuration was specified incorrectly or the resource does not exist in configuration database.
Action
If the configuration was specified correctly, add the configuration in configuration database.
CSIBL0053E The system can't delete the id configuration from configuration database.
Explanation
The error might be caused by unsupported encoding in the data.
Action
Use UTF-8 encoded data and resubmit the request.
CSIBL0054E The system can't enable replication because the bind request is not approved.
Explanation
Replication can't be enabled until the bind request is approved.
Action
Approve the bind request in IBM Security Verify.
CSIBL0055E The system can't update the id configuration in configuration database.
Explanation
Action
Check that the configuration database is running and verify that its connection parameters in the config.json file are valid.
CSIBL0056E The input data contains invalid characters.
Explanation
For the name parameter, only the following characters are allowed: alphanumeric, hyphen, underscore, At symbol, and white spaces. For the description parameter, only the following characters are allowed: alphanumeric, hyphen, underscore, comma, At symbol, white space, and period.
Action
Remove invalid characters from the user input.
CSIBL0057E The system can't connect to the configuration database.
Explanation
Action
Check that the configuration database is running and verify that its connection parameters in the config.json file are valid.
CSIBL0058E Error occurred while fetching id configuration from the configuration database.
Explanation
Action
Check the configuration database is running and verify that its connection parameters in config.json file are valid.
CSIBL0059E The system can't process the request because one or more required input parameters are missing.
Explanation
All required input parameters must be specified.
Action
To connect to IBM Cloud, the mandatory input parameters are name, description' and bind request file. To update the IGI database connection the mandatory input parameters are details, hostname, port, dbName, username, password, and enableSSL.
CSIBL0060E The system can't store the id configuration in the configuration database.
Explanation
Action
Check that configuration database is running and verify that its connection parameters in config.json are valid.
CSIBL0061E The system can't parse the bind request response from id.
Explanation
An unknown response was received from IBM Security Verify.
Action
Check the connectivity to IBM Security Verify and that the response from IBM Security Verify is valid.
CSIBL0062E The system can't send the bind request to id.
Explanation
This error might be caused by a system error or a connectivity issue.
Action
Check the connectivity to IBM Security Verify.
CSIBL0063E The system can't process the request because of invalid data input.
Explanation
The error might be caused by invalid data types or descriptions in the input data.
Action
Check that the input data like name and description are valid strings and that enabledReplication is boolean.
CSIBL0064E The system can't read the id configuration from the configuration database.
Explanation
The error might be caused by unsupported encoding in the data.
Action
Use UTF-8 encoded data and resubmit the request.
CSIBL0065E The system can't process the request because one or more required input parameters are missing.
Explanation
All required input parameters must be specified.
Action
Ensure that the required parameters hostname and authToken are in the input request.
CSIBL0066E The system can't process the request because the host name is invalid.
Explanation
The error might be caused by invalid characters in the host name. Only following characters are allowed: alphanumeric characters, hyphen, underscore, and period.
Action
Provide correct host name.
CSIBL0067E The system can't process the request because an invalid IBM QRadar authentication token was specified.
Explanation
Either the authentication token has invalid characters or is expired.
Action
Provide a valid authentication token.
CSIBL0068E The system can't process the request because one or more required input parameters are missing.
Explanation
all required input parameters must be specified.
Action
Input request must contain valid XForce API key and password details. The key and password parameters are required in the input request.
CSIBL0069E The system can't process the request because invalid IBM XForce API key and password parameters were specified.
Explanation
The error might be caused by invalid characters in the input request or the IBM XForce API key and password parameters are not valid.
Action
Provide a valid IBM XForce API key and password.
CSIBL0070E The system can't process the request because one or more required input parameters are missing.
Explanation
All required input parameters must be specified.
Action
The input request must contain all mandatory attributes. The decayFactor parameter is required in the input request.
CSIBL0071E The system can't process the request because invalid data types were found in the input parameters.
Explanation
All input parameters must have valid data types.
Action
Input request must contain all the mandatory attributes with valid data types. The decayFactor parameter value must be of the type long data.
CSIBL0072E The system can't process the request because an invalid value was specified for decayFactor parameter in the input request.
Explanation
A valid decayFactor parameter value must be between 0.01 to 1.
Action
Ensure that the decayFactor parameter value in the input request is between 0.01 to 1.
CSIBL0073E The system can't process the request because invalid path parameters were specified. Valid path parameters are id
Explanation
All parameters must have valid paths.
Action
Correct any invalid paths and resubmit the request.
CSIBL0074E The system can't process the request because of an internal server error.
Explanation
Action
Contact IBM Support.
CSIBL0075E The system can't process the request because updating QRadar hostname is not allowed.
Explanation
The application is running on the QRadar console. By default, it uses the QRadar console host name.
Action
CSIBL0076E The system can't process the request because the QRadar input data was invalid.
Explanation
The QRadar host name or authToken might be invalid, or the authToken might be expired.
Action
Resubmit the request with a valid QRadar host name and authToken.
CSIBL0077E The system can't process the request because of too many characters in the input parameters.
Explanation
One or more input parameters might exceed the number of characters limit. For name attribute the limit is 64 and for the description attribute the limit is 265.
Action
Shorten the strings and resubmit the request.
CSIBL0078E The system can't process the request because the input file was invalid.
Explanation
The input file might be corrupted or the input file was reused after the bind request was approved in IBM Security Verify.
Action
Regenerate the file from IBM Security Verify.
CSIBL0079E The system can't process the request because the input file was invalid.
Explanation
The bind request was rejected in IBM Security Verify.
Action
Regenerate the file from IBM Security Verify.
CSIBL0080E The system can't process the request because the input file was invalid.
Explanation
The bind request was already approved in IBM Security Verify. The file can't be reused after approval.
Action
Regenerate the file from IBM Security Verify.
CSIBL0081E The system can't process the request because an invalid database type was specified in the query parameter.
Explanation
Supported database types for IGI are DB2 and Postgres. Supported database types for ISIM is DB2.
Action
Provide valid database type and resubmit the request.
CSIBL0082E The system can't process the request because invalid database connection parameters were specified.
Explanation
One or more JDBC connection parameters might have invalid characters, or a network connectivity might problem exist. For host name, valid characters are alphanumeric characters and period (dot) character. For user name, valid characters are alphanumeric characters. The port number must be between 0-65535
Action
Provide valid database connection parameters and resubmit the request.
CSIBL0083E The system can't process the request because the database name was invalid.
Explanation
The database name might have been mistyped or might contain invalid characters.
Action
Correct the database name or provide a valid database name.
CSIBL0084E The system can't process the request because the usernameMapSettings parameter was invalid.
Explanation
The usernameMapSettings parameter might contain invalid characters. Only following characters are allowed: hyphen, underscore, space, at sign, round brackets, and a period.
Action
Correct usernameMapSettings parameter and resubmit the request.
CSIBL0085E The system can't update the user name map settings because a valid QRadar authentication token was missing.
Explanation
A valid QRadar authentication token is needed before the settings can be updated.
Action
Provide the correct usernameMapSettings parameter values along with a valid QRadar authentication token.
CSIBL0086E The system can't process the request because a support collector run is already in progress.
Explanation
A support collector run can't be started while one is currently running.
Action
Wait until the support collector run is finished, then resubmit the request.
CSIBL0088E The system can't process the request because the support collector run failed.
Explanation
Support collector run is failed.
Action
Support collector run is failed to run.
CSIBL0089E The system can't configure the policy because the required field 'id' was missing.
Explanation
All required fields must be specified in the request.
Action
Specify a valid value for the missing field and resubmit the request.
CSIBL0090E The system can't configure the policy because an incorrect value was specified for the field 'id' .
Explanation
Failed to configure policy.
Action
Failed to configure policy.
CSIBL0091E The system can't configure the policy because an invalid threshold value was specified.
Explanation
The threshold value must be a positive integer.
Action
Specify the threshold value as a positive integer and resubmit the request.
CSIBL0092E The system can't process the request because the proxy server connection parameters were invalid.
Explanation
Check the logs for more details about why the proxy server connection parameters were invalid.
Action
Verify the proxy server connection parameters and retry the operation.
CSIBL0094E The system couldn't delete the custom policy.
Explanation
An error occurred during the deletion operation. The problem might be a temporary system or network issue. Try the request again later. If the problem persists, contact your system administrator.
Action
Check the logs for the error.
CSIBL0095E The system couldn't delete the custom policy because it is not valid custom policy category.
Explanation
Ensure that a valid custom policy ID is specified.
Action
Specify the correct custom policy ID for the policy that is being deleted.
CSIBL0096E The system can't create the specified connection document.
Explanation
This error might be caused by a failure in a database update.
Action
Check that the analytics database is running and verify that its connection parameters in the config.json file are valid.
CSIBL0097E The system doesn't support correlation attribute updates for relationships.
Explanation
Unsupported arguments were included in the request.
Action
Verify that the correlation attribute definitions in the request are valid and retry the operation.
CSIBL0098E The system can't process the request because of invalid ldap configurations.
Explanation
Some of the LDAP configuration details in the input data might be invalid.
Action
Check that the input data like ldap shortorgname, binddn, basedn, host, port or credentials are correct. Correct them and retry the operation
CSIBL0099E The system can't process the request because of invalid input database configurations.
Explanation
Some of the database configuration details in the input data might be invalid.
Action
Check that the input data like database name, host, port, dbtype or credentials are correct. Correct them and retry the operation
CSIBL0100E The system cannot process the request because of an invalid or incorrect policy payload.
Explanation
The error might be caused by invalid or incorrect details in the input payload data.
Action
Check that the input payload contains all of the required attributes, correct any errors, and retry the operation.
CSIBL0101E The system cannot process the request because of an invalid or incorrect policy payload.
Explanation
The error might be caused by invalid or incorrect details in the input payload data.
Action
Check that the input payload contains all of the required attributes, correct any errors, and retry the operation.
CSIBL0102E The system cannot process the request because of an invalid policyId that was specified in request.
Explanation
The error might be caused by an invalid payload or payload with wrong custom policyId in input data.
Action
Check that the input payload contains the correct custom policyId, correct any errors, and retry the operation.
CSIBL0103E The system cannot process the request.
Explanation
The error might be caused by a database connectivity issue.
Action
Check that all the policies are loaded in the database and that the database connection exists. Correct any errors and retry the operation.
CSIBL0104E The system cannot process the request because the activation key was invalid.
Explanation
The activation key might be corrupted or the activation key is expired.
Action
Obtain a valid activation key from IBM Support.
CSIBL0105E The system cannot process the request because the password attribute was not set.
Explanation
A valid password must be set. The length of the password must be greater than 7 characters and the allowed characters are: all alphanumeric characters and special characters like -,_,@,!,*,#,%,~,$,comma, and dot.
Action
Check that the input payload contains all of the required attributes, correct any errors, and retry the operation.
CSIBL0106E The system cannot process the request because the new password is the same as the old password.
Explanation
A valid new password must be set. The length of the password must be greater than 7 characters and the allowed characters are: all alphanumeric characters and special characters like -,_,@,!,*,#,%,~,$,comma, and dot.
Action
Set a different password and retry the operation.
CSIBL0107E The system cannot process the request because the password does not match the password in the system.
Explanation
The password might be incorrectly typed.
Action
Ensure that the the password is entered correctly and retry the operation. If the problem persists, reset the password.
CSIBL0108E The system cannot process the request because the user with username 'id' cannot be found on the system.
Explanation
Either the username was incorrectly entered or it does not exist on the system.
Action
Check that the input payload contains the correct username, correct any errors and retry the operation.
CSIBL0109E The system cannot process the request because length of the password is less than 'id' characters.
Explanation
A valid password must be set. The length of the password must be greater than 7 characters and the allowed characters are: all alphanumeric characters and special characters like -,_,@,!,*,#,%,~,$,comma, and dot.
Action
Ensure that the password meets the requirements and retry the operation.
CSIBL0110E The system cannot process the request because the password contains invalid characters.
Explanation
A valid password must be set. The length of the password must be greater than 7 characters and the allowed characters are: all alphanumeric characters and special characters like -,_,@,!,*,#,%,~,$,comma, and dot.
Action
Remove the invalid characters from the password, ensure that the password meets the requirements, and retry the operation.
CSIBL0112E The system cannot process the request because a value for one or more of the required input parameters is not specified.
Explanation
A value must be specified for all of the required input parameters. A value for the currentPassword and newPassword parameters must be specified in the input payload.
Action
Check that the input payload contains all the required attributes, correct any errors, and retry the operation.
CSIBL0113E The system cannot process the request because one or more of the required input parameters are missing.
Explanation
All required input parameters must be specified. The currentPassword and newPassword parameters are required in the input payload.
Action
Check that the input payload contains all of the required attributes, correct any errors, and retry the operation.
CSIBL0114E The system cannot process the request because a JsonSyntaxException occurred while parsing the request payload for password change.
Explanation
The JSON syntax must be correctly formatted.
Action
Correct the JSON format and retry the operation.
CSIBL0115E The system can't process the request because the previously installed key has longer validity.
Explanation
The activation key might be of smaller validity compared to the already installed key.
Action
Obtain the valid activation key from IBM Support.
CSIBL0116E The system can't process the request because of invalid data input. Datasource definition already exists.
Explanation
The error might be caused due to duplicate datasource definition in the input data.
Action
Check that the datasource input field 'name' is a valid and unique string.
CSIBL0117E The system can't process the request because connection field value is invalid. Allowed values are 'id' and 'id'
Explanation
The error is caused due to invalid connection field value in the input data.
Action
Ensure that the JSON is correctly formatted and retry the operation.
CSIBL0118E The system can't process the request because connectionId field value is invalid.
Explanation
The error is caused due to invalid connectionId field value in the input data.
Action
Correct the connectionId field value and retry the operation after correction
CSIBL0119E The system can't create the specified datasource document.
Explanation
This error might be caused by a failure in a database update.
Action
Check that the request body is a valid json and conforms to the expected structure required for datasource definition.
CSIBL0120E The system can't update the specified datasource document due to invalid configuration values.
Explanation
This error might be caused due to conflicting or invalid configuration values in the request body
Action
Correct the configuration values in the request json body and retry the operation after correction
CSIBL0121E The system can't process the request because one or more required input parameters are missing.
Explanation
All required input parameters must be specified.
Action
To configure a datasource the mandatory input parameters are name, sourceType, connection and active.
CSIBL0122E The system can't update the specified sourcetype document due to invalid configuration values.
Explanation
This error might be caused due to conflicting or invalid configuration values in the request body
Action
Correct the configuration values in the request json body and retry the operation after correction
CSIBL0123E The system can't process the request because of invalid data input. SourceType definition already exists.
Explanation
The error might be caused due to duplicate sourcetype definition in the input data.
Action
Check that the sourcetype input field 'name' is a valid and unique string.
CSIBL0124E The system can't process the request because of invalid data input. Tenant value specified is invalid.
Explanation
The error might be caused due to invalid tenant details in the input data.
Action
Check that the request input header 'X-Forwarded-Host' is a valid and unique tenant string.
CSIBL0125E Some of the specified input attributes are not allowed. Valid attributes are id.
Explanation
The error is caused due to invalid input attributes.
Action
Check the attribute key names and provide correct names.
CSIBL0126E Some of the specified input attribute values are not correct.
Explanation
The error might be caused due to invalid input attribute values.
Action
Check the attribute values and provide correct values.
CSIAR0500E The system couldn't process the request because an internal error occurred during the fetch of the entity schema.
Explanation
This error might be because of a temporary network or system problem.
Action
Check the logs for additional information.
CSIAR0501E The system couldn't process the request because the entity was not found.
Explanation
Either the entity was misentered or it does not exist.
Action
Verify that the entry exists and that it is spelled correctly. If it is correct, check the logs for additional information.
CSIAR0502E The system couldn't process the request because it is missing the Entity parameter.
Explanation
Entity is a required query parameter.
Action
Add the Entity parameter to the request.
CSIAR0503E The system couldn't process the request because an internal error occurred. Check the logs for more details.
Explanation
This error might be because of a temporary network or system problem.
Action
Please check the logs for additional information.
CSIAR0504E The system couldn't process the request because the "sourceName" and "sourceType" were missing in the request.
Explanation
The sourceName and sourceType fields are required fields in the request.
Action
Ensure that all the mandatory fields are present in the request.
CSIAR0505E The system couldn't process the request because the values for "sourceName" and "sourceType" in the request are invalid.
Explanation
The request must have valid values in the sourceName and sourceType files.
Action
Ensure that the values in all fields in the request are valid.
CSIAR0506E The system couldn't process the request because the data length is not within the specified limits.
Explanation
Data length must be between 1 - 1000 for the sourceName and sourceType files.
Action
Ensure that the data length is within the specified range in the sourceName and sourceType files.
CSIAR0507E The system couldn't process the request because the request contains no data.
Explanation
A request must have some data that needs to be processed.
Action
Add some data for processing to the request.
CSIAR0508E The system couldn't process the request because the entity name is missing in the request data.
Explanation
The entity name is a required field in the request body.
Action
Add the entity name to the request body.
CSIAR0509E The system couldn't process the request because the entity data is missing in the request.
Explanation
The entity data is a required field in the request body.
Action
Add the entity data to the request body.
CSIAR0510E The system couldn't process the request because the json body of the request could not be parsed.
Explanation
The JSON body of the request must be well formed.
Action
Correct the JSON format and resubmit the request.
CSIAR0511E The system cannot delete the attribute:attribute because it is a default attribute.
Explanation
Default attributes cannot be deleted.
Action
Remove the default attribute from JSON data and resubmit the request.
CSIAR0512E The system cannot modify the default attribute: attribute because it is a default attribute.
Explanation
Default attributes cannot be modified.
Action
Remove the default attributes from JSON data and resubmit the request.
CSIAR0513E The system cannot process the request for the attribute: attribute, because the attributeName does not start with "usr_".
Explanation
Attribute names must start with the prefix "usr_".
Action
Add the "usr_" prefix to the attribute name.
CSIAR0514E The system cannot process the request because the attribute attribute contains special characters.
Explanation
Attribute names cannot contain special characters.
Action
Remove any special characters from the attribute.
CSIAR0515E The system cannot process the request for attribute attribute because the type field cannot be updated.
Explanation
Request JSON cannot contain the type attribute for existing attribute that is being updated.
Action
Remove type field from the JSON for the attribute that is being updated.
CSIAR0516E The system couldn't process the request because the json body of the request contains internal attributes.
Explanation
The JSON body of the request must not contain internal attributes.
Action
Remove the internal attributes and resubmit the request.