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 the value of this 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.

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 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.

1050

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.

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 the value of this 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.

1050

2057

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

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

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

2061

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

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

Solution:
Provide 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 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

0

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

0

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.

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 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

8199

The Case Queue that you are trying to access does not have any cases.

Possible Cause:
No cases were found in the specified Queue.

Solution:
Try to access the Queue again after some time.

7664

8200

There was an internal error in the Case Management operation.

Possible Cause:
Unexpected internal error.

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

7664

8201

No Queue is assigned to the Case administrator.

Possible Cause:
No Queue assigned to the Case administrator.

Solution:
Ensure that the Case administrator is assigned a Queue before the operation.

7664

8202

There was an internal error in the Case Management operation.

Possible Cause:
The Case was not successfully reassigned.

Solution:
Ensure that the Case is assigned to an administrator.

7664

8203

There was an internal error in the Case Management operation.

Possible Cause:
Unexpected internal error.

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

7664

8204

The specified Queue was not found in the system.

Possible Cause:
The Queue that you are trying t access does not exist.

Solution:
Ensure that you are using the correct Queue name and parameters for the operation.

7664

8205

There was an internal error in the Case Management operation.

Possible Cause:
The Queue Schedule that you are trying to create could not be successfully created.

Solution:
Ensure that you are using the correct Schedule name and parameters for the operation.

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 valid rule for the parameter. See Appendix E, "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 invalid value.

Solution:
Provide 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 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:
Provide valid rule for the parameter. 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 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 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 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 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 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 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 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 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 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 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.