0

0

The operation was successful.

NA.

1000

2002

There was an internal error.

Possible Cause:
Unexpected internal error.

1050

0

Value of one of the parameters used in the operation is invalid.

Possible Cause:
The value of the parameter passed to the API is invalid.

For example, the allowed values for user status are 0 and 1. If you set this value as 5, then you will get this error.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

1050

2050

Value of one of the parameters used in the operation is empty.

Possible Cause:
The parameter passed to the API is empty.

Solution:
Provide a non-empty value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

1050

2051

The length of one of the parameters used in the operation has exceeded the maximum allowed value.

Note: Length here refers to length of the parameter, for example password length.

Possible Cause:
The length of the parameter passed to the API has exceeded the maximum value.

Solution:
Provide the parameter such that its length is less than or equal to the maximum allowed value.

See appendix, "Input Data Validations" for the supported parameter values.

2052

The length of one of the parameters used in the operation is less than minimum allowed value.

Possible Cause:
The length of the parameter passed to the API is less than the minimum value.

Solution:
Provide the parameter such that the length of the parameter is greater than or equal to the minimum allowed value. See appendix, "Input Data Validations" for the supported parameter values.

2053

Value of one of the parameters used in the operation exceeded the maximum allowed value.

Note: Value here refers to the value of the parameter.

Possible Cause:
The value of the parameter passed to the API has exceeded the maximum allowed value.

Solution:
Provide the parameter such that the value of the parameter is less than or equal to the maximum allowed value.

See appendix, "Input Data Validations" for the supported parameter values.

1050

2054

Value of one of the parameters used in the operation is less than the minimum allowed value.

Possible Cause:
The value of the parameter passed to the API is less than the minimum allowed value.

Solution:
Provide the parameter such that the value of the parameter is greater than or equal to the minimum allowed value.

See appendix, "Input Data Validations" for the supported parameter values.

2055

Value of one of the parameters used in the operation is invalid.

Possible Cause:
The value of the parameter passed to the API is invalid.

For example, the allowed values for user status are 0 and 1. If you set this value as 5, then you will get this error.

Solution:
Provide valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

2056

Value of one of the parameters used in the operation contains invalid characters.

Possible Cause:
The parameter specified by ParameterKey contains invalid characters.

Solution:
Provide valid characters for the parameter that is specified by ParameterKey.

2057

One of the parameters used in the operation does not meet the formatting requirements.

Possible Cause:
The parameter specified by ParameterKey has an invalid format.

Solution:
Provide a valid format for the parameter that is specified by ParameterKey.

1050

2061

Value of one of the parameters used in the operation is not allowed.

Possible Cause:
The parameter specified by ParameterKey has an invalid format.

Solution:
Provide a valid format for the parameter that is specified by ParameterKey.

8104

The specified Callout URL is not valid.

Possible Cause:
The specified URL is incorrect.

Solution:
Provide the valid URL.

8105

The specified duration is not valid.

Possible Cause:
The Start Date is greater than the End Date.

The specified value for Start Date and/or the End Date is in the past.

Solution:
The Start Date must be greater than the End Date and these should be the current or future dates (as this is the duration for the exception user).

7000

0

The operation was successful.

NA.

8000

7001

0

There was an internal error.

Possible Cause:
Unexpected internal error.

8000

There was an internal error.

Possible Cause:
Unexpected internal error.

8108

There was an internal error.

Possible Cause:
Unexpected internal error.

8122

There was an internal error.

Possible Cause:
Unexpected internal error.

7501

0

The current operation on the database failed.

Possible Cause:
Database is not running.

Solution:
Start the database.

Possible Cause:
Connection between the Server and database is not complete.

Solution:
Establish the connection between the Server and database again.

Possible Cause:
The operation failed because of an internal error.

Solution:
Check the database logs for details and ensure appropriate action is taken based on these logs.

7502

An exception occurred because of an unexpected internal error.

Possible Cause:
Internal error because of unexpected Server behavior.

Solution:
Most likely cause might be Server or database failure. Check the Server transaction and database logs for details and ensure appropriate action is taken based on the Server logs.

7503

The time could not be successfully fetched.

Possible Cause:
The database settings are not set correctly in arcotcommon.ini.

Solution:
Verify and correct the database- related parameters in the file.

7511

8000

The received Device Signature is not valid.

Possible Cause:
The Server cannot parse the Device Signature. Either the packet was corrupted or there was an issue while building the signature.

Solution:
Ensure that the Device Signature is correctly built.

7601

0

Value of one of the parameters used in the operation does not exist.

Possible Cause:
The value of the parameter passed to the API does not exist.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7602

The name specified for the new ruleset already exists.

Possible Cause:
The value of the parameter passed to the API already exists.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7603

No Active ruleset of the specified name was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7604

No Proposed ruleset of the specified name was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7605

0

The name specified for the ruleset (Active or Proposed) does not exist.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7606

8101

The data sharing type refers to another ruleset. Therefore, the addition operation is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data cannot be added to the other ruleset.

7607

0

The data sharing type refers to another ruleset. Therefore, the operation to set the value(s) is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data cannot be set to another ruleset.

7608

The data sharing type refers to another ruleset. Therefore, the delete operation is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data cannot be deleted from the other ruleset.

7609

The data sharing type refers to another ruleset. Therefore, the update operation is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data cannot be updated.

7610

The data sharing type refers to another ruleset. Therefore, the value rotation is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data values cannot be rotated.

7611

The parameter sharing type refers to another ruleset. Therefore, the operation to set the value(s) is not allowed.

Possible Cause:
The rule or the ruleset refers to another ruleset. Therefore, the data cannot be set to another ruleset.

7612

0

No Active or Proposed data was found for the specified Negative Country.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFNEGATIVECOUNTRYLIST table.

Solution:
Provide a valid value for the parameter.

See appendix, "Input Data Validations" for the supported parameter values.

7613

No Active or Proposed data was found for the specified Negative IP address.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFUNTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7614

No Active or Proposed data was found for the specified Trusted IP address.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7615

0

No Active or Proposed parameters were found for the specified rule.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

Possible Cause:
The parameter specified by ParameterKey contains invalid characters.

Solution:
Provide a valid characters for the parameter that is specified by ParameterKey.

7616

No Proposed data was found for the specified Trusted IP address.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7617

No Proposed data was found for the specified Negative IP address.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFUNTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7618

No Active or Proposed data was found for the specified Scoring configuration.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7619

0

No Active or Proposed data was found for the specified Execution configuration.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7620

The value of the configuration state parameter used in the operation is invalid.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7621

The ruleset cannot be created because the specified parameters and their values for the rule do not match.

Possible Cause:
The parameters and their corresponding values passed to the API are invalid.

Solution:
Provide a valid value for the parameter. See appendix,"Input Data Validations" for the supported parameter values.

7622

No Active ruleset parameters found for the specified otherOrgName and otherConfigName.

Possible Cause:
The value of the otherOrgName and otherConfigName parameters passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix,"Input Data Validations" for the supported parameter values.

7623

No Active ruleset found for the specified data for otherOrgName and otherConfigName parameters.

Possible Cause:
The value of the otherOrgName and otherConfigName parameters passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7624

0

The update is not allowed because it will create a cyclic dependency.

Possible Cause:
The rule or the ruleset refers to another ruleset.

Solution:
Change the ruleset(s) that have not yet been migrated, so that the cyclic dependency is eliminated.

7625

No Active ruleset found for the specified otherOrgName and otherConfigName parameters. Therefore, the update operation is not allowed.

Possible Cause:
The value of the otherOrgName and otherConfigName parameters passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7626

No Active ruleset found for the specified data for otherOrgName and otherConfigName parameters. Therefore, the update operation is not allowed.

Possible Cause:
The value of the otherOrgName and otherConfigName parameters passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7627

8102

The specified country cannot be deleted because no corresponding Proposed data was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7628

The specified IP range cannot be deleted because no corresponding Proposed data was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7629

0

The specified IP range cannot be deleted from the Trusted Aggregator list because no corresponding Proposed data was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7630

The specified IP or range cannot be deleted for the Trusted Aggregator because no corresponding Proposed data was found.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7631

The specified IP range does not exist in the Negative IP Address list.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7632

No Active or Proposed data for Trusted Aggregator was found for the specified Trusted IP address.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7633

No Proposed data for the specified Trusted Aggregator was found.

Possible Cause:
The value of the parameter passed to the API was not found in the ARRFTRUSTEDIPLIST table.

Solution:
Provide a valid value for the parameter. See appendix,"Input Data Validations" for the supported parameter values.

7634

0

The specified Trusted Aggregator does not exist in the Trusted Aggregators list.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7635

The specified Trusted Aggregator cannot be added, because it already exists in the Trusted Aggregators list.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7636

The specified Aggregator ID could not be generated because of an internal Server error.

Possible Cause:
Aggregator ID generation failed due to an internal error in the Server.

Solution:
Most likely cause might be because of database failure. Check the Server transaction logs for details and ensure appropriate action is taken based on the Server logs.

7637

The specified encryption key was not found in the database.

Possible Cause:
The encryption key does not exist.

Solution:
Ensure that the key that you are using is correct.

7638

0

The supported port types could not be tokenized.

Possible Cause:
Server host, port, or both might not be configured correctly.

Solution:
Provide the correct host and port number.

Possible Cause:
Server might not be running.

Solution:
Start the Server.

Possible Cause:
If SSL is configured, then certificates might not be configured correctly.

Solution:
Configure the TLS certificates correctly.

7639

The specified SSL Trust Store does not exist.

Possible Cause:
The value of the parameter passed to the API was not found.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

Possible Cause:
The specified Trust Store name is not valid.

Solution:
You must provide a valid Trust Store name.

Possible Cause:
The specified organization name is not valid.

Solution:
You must provide a valid organization name.

7640

0

The specified score ranges were not found.

Possible Cause:
No Score ranges or Advice were found in the ARRFADVICECONFIG and ARRFADVICECODE tables. The RiskMinder database scripts were not run properly.

Solution:
Contact CA Support to resolve this issue.

7641

The Scoring Callout does not have the highest execution priority.

Possible Cause:
The priority set in the Web service call is higher than the existing highest execution priority in the RiskMinder database.

Solution:
Set the priority in the Web service call correctly.

7642

The Score does not have the highest execution priority.

Possible Cause:
The priority set in the Web service call is higher than the existing highest execution priority in the RiskMinder database.

Solution:
Set the priority in the Web service call correctly.

7643

8103

The required custom rule details were not specified. Therefore, the rule was not added.

Possible Cause:
The custom rule details were not specified correctly in the Web service call.

Solution:
Set the Web service call input parameters correctly.

7644

0

The specified rule type does not exist or is not valid.

Possible Cause:
The specified rule type is either not present in the ARRFADDONRULETYPE table or is an invalid rule type.

Solution:
You must provide a valid rule type.

7645

0

The custom rule was not added because it will create a cyclic dependency of data.

Possible Cause:
The creation of the custom rule referring to another rule creates a cyclic dependency for the data that you added. Therefore, this is not allowed.

Solution:
Change the required rule such that the cyclic dependency is eliminated.

7646

The custom rule was not added because it will create a cyclic dependency of parameters.

Possible Cause:
The creation of the custom rule referring to another rule creates a cyclic dependency for the parameters that you added. Therefore, this is not allowed.

Solution:
Change the required rule such that the cyclic dependency is eliminated.

7647

The rule that you specified is not available in the ruleset.

Possible Cause:
The value of the rule passed to the API was not found in the specified ruleset.

Solution:
Provide a valid rule for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7648

Error occurred while fetching the parameters.

Possible Cause:
The parameter specified by ParameterKey contains invalid characters.

Solution:
Provide valid characters for the parameter that is specified by ParameterKey.

7649

Other rules are dependant on this rule. Therefore, this rule cannot be deleted.

Possible Cause:
Rules in another ruleset are currently referring to this rule. Therefore, you cannot delete this rule.

Solution:
If required, delete the depending rulesets before you delete this rule.

7650

0

The TypeName input is not specified in the call.

Possible Cause:
The TypeName has not been specified in the Web service call.

Solution:
Specify the correct input value for TypeName in the input.

7651

Specified TypeName already exists.

Possible Cause:
The TypeName in the input is already present in the system.

Solution:
Specify a different TypeName in the input.

7652

A cyclic redundancy is created with this update. Therefore, the update is not allowed. Also, because of this action only some rulesets were migrated.

Possible Cause:
A cyclic dependency will be created after the migration of all the required rulesets. As a result, only a few rulesets have been migrated.

Solution:
Change the ruleset(s) that have not yet been migrated, so that the cyclic dependency is eliminated.

7653

A cyclic redundancy is created with this update. Hence this update is not allowed. No rulesets have been migrated.

Possible Cause:
A cyclic dependency will be created after the migration of all the required rulesets.

Solution:
Change the required ruleset(s) such that the cyclic dependency is eliminated.

7654

0

The database operation failed while migrating to production. Some rulesets were migrated

Possible Cause:
A cyclic dependency was found during migration of a ruleset. Therefore, only a few rulesets have been migrated. Some ruleset(s), including the failed ruleset, have not been migrated.

• Solution:
  Check the RiskMinder logs for details and ensure that appropriate action is taken based on these logs.
• Remove the cyclic dependency of the failed ruleset and migrate it.
• Migrate the remaining rulesets that were not migrated because of the failed ruleset.

7655

The value could not be converted to uppercase.

Possible Cause:
The input given cannot be converted to uppercase.

Solution:
Check the input.

7656

The User Profile information could not be retrieved.

Possible Cause:
UDS is not up and running.

Solution:
Check if UDS is deployed properly and is up and running.

Book: See the CA RiskMinder Installation and Deployment Guide for more information to do so.

Possible Cause:
The user does not exist in the RiskMinder system.

Solution:
Add the user to the RiskMinder system.

7656

8116

The User Profile information could not be retrieved because the user status is currently disabled.

Possible Cause:
The user account is disabled.

Solution:
Activate the user.

7656

8117

The User Profile information could not be retrieved because the user account has been deleted.

Possible Cause:
The user does not exist in the RiskMinder system.

Solution:
Add the user to the RiskMinder system.

7656

8118

The User Profile information could not be retrieved because the user does not exist.

Possible Cause:
The user does not exist in the RiskMinder system.

Solution:
Add the user to the RiskMinder system.

7657

0

The Location and Connection information was not found in the database.

Possible Cause:
The Quova data has not been uploaded in the RiskMinder database.

Solution:
Upload the Quova data into the RiskMinder database by using the arrfupload.exe tool.

Book: See the CA RiskMinder Administration Guide for more information on this.

7658

0

The Exception User does not exist in the system.

Possible Cause:
The user does not exist in the RiskMinder system.

Solution:
Add the user to the RiskMinder system.

Possible Cause:
The specified user is not an Exception User.

Solution:
Ensure that you have provided the correct details for the user, or add the user to the Exception User List before proceeding.

7659

The custom rule will create cyclic dependency. Therefore, the rule cannot be added.

Possible Cause:
A cyclic dependency will be created when you create the custom rule.

Solution:
Change the rule such that the cyclic dependency is eliminated.

7660

Other rules have cyclic dependency on the custom rule. Therefore, the rule cannot be deleted.

Possible Cause:
Other rules have cyclic dependency on the custom rule you are trying to delete.

Solution:
Change the rule such that the cyclic dependency is eliminated.

7661

8000

The XML input is invalid.

Possible Cause:
Value of one or more of the parameters used in the operation is invalid.

Solution:
Provide a valid input for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7662

0

The specified version of the parameter used in the operation is not Active.

Possible Cause:
The version of the parameter passed to the API was not found.

Solution:
Provide a valid input for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7663

The operation to refresh the specified configuration failed.

Possible Cause:
The specified configuration does not exist.

Solution:
Ensure that the configuration exists or that you have specified the correct details.

7664

8000

There was an internal error in the operation.

Possible Cause:
Unexpected internal error.

Solution:
Most likely cause might be Server or database failure. Check the Server transaction and database logs for details and ensure that appropriate action is taken based on the Server logs.

7664

8122

The Device ID could not be generated.

Possible Cause:
This could be because of a possible internal error at the server end or because of corrupted data.

7664

8207

There was an internal error because the Server is shutting down.

Possible Cause:
The Server shutdown is in progress.

Solution:
Wait for sometime for the Server to come up again and then try performing the operation.

7666

8000

The length of one of the parameters used in the operation has exceeded the maximum allowed value.

Possible Cause:
The length of the specified parameter has exceeded the maximum value.

Solution:
Provide a valid input for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7666

8113

No Association Name parameter was not found in the request.

Possible Cause:
The Association Name parameter is missing from the request.

Solution:
Ensure that the request contains a valid Tag Name.

7666

8114

The value of one of the parameters used in the operation is not valid.

Possible Cause:
The parameter specified by ParameterKey has an invalid value.

Solution:
Provide a valid format and value for the parameter that is specified by ParameterKey.

7666

8135

The Device ID used in the operation is not valid.

Possible Cause:
The specified Device ID is not valid.

Solution:
Ensure that you provide a valid value for the Device ID.

7667

8000

The length of one of the parameters used in the operation has exceeded the maximum allowed value.

Possible Cause:
The length of the parameter passed to the API has exceeded the maximum value.

Solution:
Provide a valid value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7667

8140

The length of the User Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the User Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7667

8144

The length of the Association Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the Association Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix,"Input Data Validations" for the supported parameter values.

7667

8146

The length of the Transaction Type Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the Transaction Type Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix,"Input Data Validations" for the supported parameter values.

7667

8148

The length of the First Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the First Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7667

8150

The length of the Last Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the Last Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7667

8152

The length of the PAM parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the PAM parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7667

8154

The length of the Email ID parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the Email ID parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7667

8156

The length of the Organization Name parameter has exceeded the maximum allowed value.

Possible Cause:
The length of the Organization Name parameter has exceeded the maximum value.

Solution:
Ensure that the parameter is of valid length. See appendix, "Input Data Validations" for the supported parameter values.

7668

8000

One of the parameters specified for the operation contains prohibited characters.

Possible Cause:
A specified parameter contains prohibited characters.

Solution:
Provide a valid format and value for the parameter that is specified. See appendix,"Input Data Validations" for the supported parameter values.

7668

8141

The User Name parameter contains prohibited characters.

Possible Cause:
The User Name parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8145

The Association Name parameter contains prohibited characters.

Possible Cause:
The Association Name parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8147

The Transaction Type parameter contains prohibited characters.

Possible Cause:
The Transaction Type parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8149

The First Name parameter contains prohibited characters.

Possible Cause:
The First Name parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8151

The Last Name parameter contains prohibited characters.

Possible Cause:
The Last Name parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8153

The PAM (Personal Assurance Message) parameter contains prohibited characters.

Possible Cause:
The PAM parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7668

8155

The EMAIL ID parameter contains prohibited characters.

Possible Cause:
The EMAIL ID parameter has prohibited characters.

Solution:
Provide a valid format and value for the parameter. See appendix, "Input Data Validations" for the supported parameter values.

7669

8158

The EMAIL ID parameter used in the operation does not meet the formatting requirements.

Possible Cause:
The EMAIL ID parameter specified by ParameterKey has invalid format.

Solution:
Provide a valid format for the parameter.

7670

8000

The value of one of the configurations used in the operation does not exist.

Possible Cause:
The specified configuration for the organization is not correct.

Solution:
Ensure that the specified organization configuration is correct.

Possible Cause:
There is no configured ruleset for the specified transaction.

Solution:
Ensure that the specified ruleset exists or that you specify the correct ruleset information.

7670

8120

The value of ruleset configuration used in the operation does not exist for the specified Channel.

Possible Cause:
The specified configuration for the organization and/or channel is not correct.

Solution:
Ensure that the configuration information that you specify is correct.

Possible Cause:
There is no ruleset configured for the specified channel of the organization.

Solution:
Ensure that the specified ruleset exists or that you specify correct ruleset information.

7670

8121

The value of ruleset configuration used in the operation does not exist.

Possible Cause:
The specified configuration for the organization is not correct.

Solution:
Ensure that the specified organization configuration is correct.

Possible Cause:
There is no configured ruleset for the specified transaction.

Solution:
Ensure that the specified ruleset exists or that you specify correct ruleset information.

7671

8000

There was a failure in creating the association.

Possible Cause:
The specified information is not valid.

Solution:
Ensure that the inputs you specify are correct.

7671

8109

There was a failure in deleting the association.

Possible Cause:
The specified association does not exist.

Solution:
Ensure that the specified association exists.

7672

8115

The details for the Organization Name that you specified for the operation is not active.

Possible Cause:
The specified organization has been deactivated.

Solution:
Ensure that the organization is valid and active.

7672

8139

The details for the Organization Name that you specified for the operation were not found.

Possible Cause:
The specified organization is unknown and was not found in the system.

Solution:
Ensure that the organization is valid and active.

7673

8000

The specified input is not valid.

Possible Cause:
The specified input is not valid.

Solution:
You must provide a valid input in the required format.

7673

8184

The specified input is not valid.

Possible Cause:
The user information is not provided.

Solution:
Ensure that you provide the required information for a valid and active user.

7678

8000

The Organization Name that you specified for the operation was not found.

Possible Cause:
The specified organization does not exist.

Solution:
You must provide a valid organization name.

7679

8000

The Organization Name that you specified for the operation is not valid.

Possible Cause:
The specified input is not valid.

Solution:
You must provide a valid input in the required format.

7681

8000

The User Name that you specified for the operation was not found.

Possible Cause:
The specified user does not exist.

Solution:
You must provide a valid user name.

7683

8000

The User Name that you specified for the operation already exists.

Possible Cause:
The specified user already exists in the system.

Solution:
You must provide a distinct user name.

7684

8000

The user account for the corresponding User Name that you specified for the operation has been disabled.

Possible Cause:
The specified user account has been deactivated.

Solution:
Ensure that the user is active.

7690

8000

The user account for the User Name that you specified for the operation already exists.

Possible Cause:
The specified user account already exists in the system.

Solution:
You must provide a distinct user account name.

7691

8000

Web Service authentication or authorization failed.

Possible Cause:
Sent to the client if one of the following Web Services is enabled for Authentication and Authorization (AnA), and the supplied credential is not valid:

• getUserProfile
• addUserToExceptionList
• deleteUserFromExceptionList
• getLocationAndConnectionInfo

Solution:
Ensure that you send the correct credential or authorization token while making the Web Service call.