31201

Unable to process the database query, {0}.

Note: This is a critical error.

Possible Causes:

• Invalid input parameter was specified.
• Error occurred during encryption.
• Database is down.

Solution:

1. Verify that the database information in arcotcommon.ini is correct.

2. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

3. If the issue is not resolved, then you must contact CA Support.

31002

UDS is not initialized.

Note: This is a critical error, and is typically seen when UDS or Administration Console are restarted.

Possible Causes:

• ARCOT_HOME is not correctly set
• Database is down.
• Hardware encryption initialization failed.

Solution:

1. Verify that the database information in arcotcommon.ini is correct.

2. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

3. If the issue is not resolved, then you must contact CA Support.

31003

Fatal error, restart UDS.

This error is expected when UDS application has encountered an unexpected error.

Possible Causes:

• UDS did not correctly start up.
• Database is down.
• Hardware encryption initialization failed.

Solution:

1. Verify that the database information in arcotcommon.ini is correct.

2. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

3. Restart UDS.

31006

Configuration parameter, {0} not found.

This error occurs if the specified UDS configuration was not found in the ARUDSCONFIG table.

Possible Causes:

• Database was manually updated.
• Information in database tables was not correctly populated.

Solution:

1. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

31007

Invalid configuration parameter value, {0} for parameter name, {1}.

This error occurs if the specified UDS configuration contains invalid value(s).

Possible Causes:

• Database was manually updated.
• Information in database tables was not correctly populated.

Solution:

1. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

31008

Unknown error.

This message appears if an unexpected internal error occurred.

Possible Cause:

Unexpected internal error.

Solution:

1. See the arcotadmin.log and arcotuds.log files and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

31009

General error: {0}.

This message appears if an unexpected internal error occurred.

Possible Cause:

Unexpected internal error.

Solution:

1. See the arcotadmin.log and arcotuds.log files and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

35100

Error communicating with data store.

Note: This is a critical error that occurs either when the connectivity with the database server is lost or during processing of a database query.

Possible Causes:

• The database is down.
• There was an error during encryption or decryption of data.

Solution:

1. See the arcotadmin.log and arcotuds.log files and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

35101

Error while loading configuration file, {0}.

Note: This is a critical error and occurs while reading configuration files in the conf directory of ARCOT_HOME.

Possible Cause:

The configuration files are corrupted.

Solution:

1. Ensure that the configuration files contain the required details.

2. Retry reading from the files.

35102

Configuration file, {0} not found.

Possible Causes:

1. ARCOT_HOME is not set.

2. The required configuration files not found in the conf directory of ARCOT_HOME.

Solution:

1. Verify if ARCOT_HOME points to the right location.

2. Verify if the required configuration files exist in the conf directory of ARCOT_HOME.

35103

ARCOT_HOME environment variable is not set.

Possible Cause:

ARCOT_HOME not set.

Solution:

Set the ARCOT_HOME to point to your Arcot installation directory.

35105

Invalid input parameter.

Possible Cause:

The input value provided for the specified parameter is not valid.

Solution:

See User Attributes Validation Checks for more information on valid input parameters.

35106

Missing input parameter, {0}.

Possible Cause:

The specified input parameter is missing in the API request.

Solution:

Provide the required parameter.

35107

Cannot update global chosen encryption set, because the organization already contains users.

Possible Cause:

One or more organizations refer to the global encryption set, but users have already been created in these organizations.

Solution:

Global encryption set cannot be updated when there are users in the referring organizations.

35108

Error while audit logging.

Possible Causes:

1. Database connectivity is lost.

2. Invalid input provided for the audit logs.

Solution:

See the arcotadmin.log and arcotuds.log files and take corrective action.

35109

Field, {0} exceeded maximum length, {1}.

Possible Cause:

The specified field exceeded the allowed length.

Solution:

Provide a value within the expected range. See User Attributes Validation Checks for more information on valid input parameters.

35110

Field, {0} contains invalid characters.

Possible Causes:

The value provided for the specified field contains unsupported characters.

Solution:

Retry with valid inputs. See User Attributes Validation Checks for more information on valid input parameters.

31125

User, {0} not found.

Possible Causes:

1. The user identifier specified in the request is not valid.

2. The user does not exist in the system.

3. The user has been deleted.

Solution:

1. Provide valid user details.

2. Also, search for deleted users to verify whether the user has been deleted.

31126

User, {0} not unique. More than one user found.

Possible Cause:

The specified user is not unique in the system. As a result, more than one user returned for the given UserID.

Solution:

1. Ensure that the UserID is unique.

2. Verify if the UserID mapping attribute exists in the LDAP organization.

3. If the issue is not resolved, then you must contact CA Support.

31118

Search field, {0} not permitted.

Possible Cause:

User search is not permitted on the specified field. For example, searching for an unmapped LDAP attribute is not allowed.

Solution:

1. Search based on other fields.

2. Ensure that the required attributes are correctly mapped.

31127

Operation, {0} not supported. Invalid current state {1} of User, {2}.

Possible Causes:

• The current operation is not supported for the given user status.
• The status of the specified user is either INITIAL or INACTIVE.
  For example, authentication operations are not supported for INACTIVE users.

Solution:

Update the user status to a valid status and then perform the operation. See User Attributes Validation Checks for more information on valid input parameters.

31104

Operation, {0} not supported for repository.

Possible Cause:

The current operation is not supported for the repository. For example, Write operations are not supported for LDAP repository.

Solution:

Unsupported operations must be independently performed on the repository and must not go through CA AuthMinder flows.

For example, users must be created in LDAP through LDAP user interface or APIs.

31128

User, {0} already exists.

Note: The createUser API throws this error.

Possible Cause:

The specified user already exists in the system. Therefore, cannot create another user with the same UserID.

Solution:

UserID must be unique in an organization. Create an user with different UserID.

31119

User identifier, {0} is mandatory.

Possible Cause:

API was called without providing user identifier, which is mandatory for the given API call.

Solution:

Provide a valid user identifier in the API request.

31129

PAM is not set.

This is a C++ error code.

Possible Causes:

1. Specified user was not found.

2. Database connectivity is lost.

Solution:

1. See the arcotadmin.log and arcotuds.log files and take corrective action.

2. If the issue is not resolved, then you must contact CA Support.

31131

Invalid authentication token.

Note: This is observed when the API is enabled for authentication and authorization.

Possible Causes:

1. The authentication token is not provided in the request.

2. The specified authentication token is not valid or has been tampered with.

Solution:

Provide a valid authentication token, if the API is enabled for AnA

31132

Invalid authentication request.

Note: This is observed when the API is enabled for authentication and authorization.

Possible Causes:

1. The authentication token provided in the request has expired.

2. The SOAP request is invalid.

Solution:

1. Provide a valid authentication token in the request.

2. Obtain a new authentication token, if required.

31135

Hashing of authentication token failed.

Note: This is observed when the API is enabled for authentication and authorization.

Possible Causes:

1. The authentication token provided in the request is invalid or has been tampered with.

2. The token could not be processed.

3. The securestore.enc file not found in the conf directory of ARCOT_HOME.

Solution:

1. Provide a valid authentication token.

2. Re-create securestore.enc.

Book: See CA AuthMinder Administration Guide for more information on how to create this file.

3. If the issue is not resolved, then you must contact CA Support.

70611

Authentication failed.

Possible Causes:

1. Incorrect username or password has been specified in the request.

2. The administrator status is not valid.

3. The Account is locked.

4. Account has expired.

Solution:

Retry with valid password or contact the administrator to unlock or activate the account.

70300

Administrator {0} (organization: {1}) does not have the privilege to perform

administration operations for organization, {2}.

Note: This is observed when the API is enabled for authentication and authorization.

Possible Cause:

The administrator performing the operation has a limited scope, and does not have the required permissions to perform the current task.

Solution:

1. Contact an administrator at higher level for the required permissions.

31136

Delete operation for product {0} failed.

Note: This error is seen when the Cascade Delete feature is enabled.

Possible Cause:

A database error occurred during a delete operation.

Solution:

1. Retry the operation.

2. If the error persists, then you must contact CA Support.

31137

Invalid search expression.

Note: This error is thrown by the searchUsers API.

Possible Cause:

The search expression that you provided is not valid.

Solution:

Provide valid search expressions. Refer to the WSDL documentation to know more about valid search expressions.

31138

Invalid start ({0}) or end ({1}) index specified.

Note: This error is thrown by the listUsers API.

Possible Causes:

1.The start or end index that you provided is not vv lid (probably a a negative integer).

2. End index is less than the start index.

Solution:

Provide valid positive integers for the start and end indexes.

31139

Page size, {0} exceeded the configured default search count, {1}.

Note: This error is thrown by the listUsers API.

Possible Cause:

Number of users that you are trying to retrieve exceeds the configured search count.

Solution:

Limit the number of users within the search count. Or increase the search count.

31151

Start lock time and End lock time are not allowed for ACTIVE user status.

Possible Cause:

You have provided Start lock time and End lock time as inputs along with the user status, ACTIVE.

Note: User status cannot be updated to ACTIVE if Start lock time and End lock time are also specified in the request.

Solution:

Do not provide Start and End lock dates for ACTIVE user status. These inputs are valid only if the user status is INACTIVE.

31152

Invalid lock period. Start lock time must be before End lock time.

Possible Cause:

Start lock time is greater than the End lock time.

Solution:

Ensure that the Start lock time is always less than the End lock time.

31153

Invalid lock Period. Start lock time cannot be before current time.

Possible Cause:

Start lock time is less than the current time.

Solution:

Ensure that the Start lock time is always greater than the current time.

36100

Invalid input parameter: name, {0} value, {1}.

Possible Cause:

The input value provided for the given parameter name is not valid. For example, specified email contains multi-byte characters.

Solution:

Provide valid input values. See User Attributes Validation Checks for more information on valid input parameters.

36101

Unsupported encoding exception: {0}.

Possible Cause:

Error while encoding or decoding user or organization custom attributes. Invalid custom attributes.

Solution:

Retry with valid inputs.

36102

Parser exception: {0}.

Possible Cause:

Error occurred while parsing user details from datastore.

For example, the error occurred while retrieving information from the LDAP Date field.

Solution:

1. Retry the operation.

2. If the error persists, then you must contact CA Support.

36103

{0}.

Possible Causes:

Error occurred while encrypting or decrypting user data, because:

1. HSM is not reachable

2. Invalid Key Label is provided in the input.

3. Server Cache has not been updated.

Solution:

1. Retry after cache refresh.

2. Verify if the specified Key Label exists in the HSM.

3. Ensure that the HSM connectivity is not lost.

36106

User {0} not updated.

Possible Causes:

1. Specified user not found.

2. Database connectivity is lost.

Solution:

1. Retry the operation.

2. See if there are any database-related errors in arcotadmin.log and arcotuds.log and take corrective action.

3. If the issue is not resolved, then you must contact CA Support.

36107

Provided image size, {0} KB, exceeds the maximum supported size, {1} KB.

Possible Cause:

The user image has exceeded the supported size.

Solution:

Ensure that the image size is within the supported range. See User Attributes Validation Checks for more information on valid input parameters.

36108

Invalid image format, {0}. Supported image formats are JPEG, GIF, BMP, and PNG only.

Possible Cause:

The format of the user image provided in the request is not valid.

Solution:

Ensure that the image format you are using is supported by UDS. See User Attributes Validation Checks for more information on valid input parameters.

31134

Invalid input parameter. {0} is not an enterprise LDAP organization.

Possible Cause:

You passed non-LDAP organization details to the LDAP-only API, such as API=performQnaVerification

Solution:

Ensure that you use the correct non-LDAP APIs.

31108

Invalid input parameter: name, {0} and value, {1}.

Possible Cause:

The value provided for the specified parameter is not valid.

Solution:

Provide valid inputs. See User Attributes Validation Checks for more information on valid input parameters.

31109

Organization with name {0} already exists.

Possible Cause:

Organization with the specified name already exists. As a result, another organization with the same name cannot be created.

Solution:

Provide a unique organization name.

31110

Organization with the display name {0} already exists.

Possible Cause:

Organization with the specified display name already exists. As a result, another organization with the same display name cannot be created.

Solution:

Provide a unique display name for the organization.

31114

Operation, {0} is not supported for organization {1} with status {2}.

Possible Cause:

The specified operation is not supported for the specified status of an organization. For example, setting an INACTIVE organization as default is not allowed.

Solution:

Update the organization status and then perform the operation.

31115

Organization, {0} with status, {1} does not exist.

Possible Cause:

The specified organization with the given status does not exist.

Solution:

Verify if the organization exists and check if its status has changed.

31116

Organization {0} is already deleted.

Possible Cause:

The organization that you are trying to delete cannot be deleted, because it has already been deleted.

Solution:

Ensure that you specify the correct organization details.

31117

Unable to connect to the repository, {0}.

Possible Causes:

• Repository is down.
• Specified Repository connection details are not correct.

Solution:

Check the repository connection details and retry.

31121

Invalid organization status, {0}.

Possible Cause:

The organization status is not valid for the given operation. For example, the organization cannot be created with status INACTIVE.

Solution:

Update the organization status to a valid one.

31122

Operation, {0} not supported for default organization {1}.

Possible Cause:

The specified operation is not supported on Default organization. For example, Default organization cannot be deleted.

31124

Organization, {0} does not exist.

Possible Causes:

• The organization name provided as input is not valid.
• The Server cache has not been updated.
• The organization with the specified name does not exist.

Solution:

Retry the operation after cache refresh.

31140

Attribute encryption failed.

Possible Causes:

• The organization display name provided as input is not valid.
• The Server cache has not been updated.
• The organization with the specified display name does not exist.

Solution:

Retry the operation after cache refresh.

31142

Invalid key label. No key with alias, {0} exists.

Note: This error is thrown if the system is configured for hardware encryption.

Possible Causes:

• The Key Label specified in the operation does not exist in the HSM.
• The HSM connection failed.

Solution:

1. Check the HSM connectivity.

2. Verify if the Key Label is present in the HSM.

31143

Organization {0} exist with the same LDAP configuration.

Note: The createOrg APIs throw this error.

Possible Cause:

An LDAP organization with the same configuration already exists.

Solution:

LDAP organizations must have unique configurations. Update the existing organization or create a new organization with different details.

31146

Error saving custom attributes for user {0}.

Note: This error is thrown while updating users’ custom attributes.

Possible Causes:

• The specified user was not found.
• The database connection failed.

Solution:

1. Retry the operation.

2. If the issue is not resolved, then you must contact CA Support.

38100

Resource, {0} of type, {1} does not exist.

Note: This error is thrown when the processing of an account type fails.

Possible Causes:

• The specified account type does not exist.
• The Server cache has not been updated.

Solution:

Refresh the cache and retry.

38101

Unknown or unexpected error.

Possible Cause:

A critical internal error occurred.

Solution:

Contact CA Support.

39100

User account, {0} not found for account type, {1}.

Possible Causes:

The specified user account was not found for the given account type, because:

• The specified user does not have an account.
• The account has been deleted.

Solution:

Verify if the input Account ID is valid.

39101

The custom attribute, {0} is invalid for account type, {1}.

Possible Cause:

• The specified account custom attribute does not exist for the account type.
• The Server cache has not been refreshed.

Solution:

1. Ensure that you provide a valid input.

2. Refresh the cache and retry.

39102

User identifier, {0} not found for organization, {1}.

Possible Cause:

The user identifier was not found for the organization during deep search. In other words, the specified identifier did not match any of the userid, accountid, and accountid attributes.

Solution:

Provide valid user identifier.

39103

Account(s) creation failed for user identifier, {0} belonging to the organization, {1}.

Note: This is a C++ error code.

Possible Causes:

• The connection to the database failed.
• An unexpected error occurred while creating account(s).

Solution:

1. See if there are any related errors in arcotadmin.log and arcotuds.log and take corrective action.

2. Retry the operation.

39104

The specified user account already exists for user {0}.

Possible Cause:

The specified user account already exists.

Solution:

Ensure that you specify a unique account name.

39105

Account types do not exist for organization, {0}.

Possible Causes:

• The specified account type is not available for the organization.
• The Server cache has not been refreshed.

Solution:

1. Ensure that you specify the correct account type name.

2. Add the organization to the account type scope.

3. Retry after cache refresh.

39106

Account type already exists.

Note: The APIs for creating and updating account types throw this error.

Possible Cause:

The specified account type exists in the system. As a result, another accounttype with the same name or display name cannot be created.

Solution:

Create an accounttype with a unique name or display name.

39107

Account ID, {0} already created for the account type, {1}.

Possible Cause:

The specified user account has already been created for the given account type.

Solution:

The Account ID must be unique for a given account type for an organization. Provide a different Account ID and retry.

39201

SOAP action is null.

Possible Cause:

The incoming SOAP request is not valid.

Solution:

1. Provide a valid SOAP request.

2. If problem persists, then contact CA Support.

55000

Invalid input parameter, {0}.

Possible Cause:

The input value provided for the given parameter is not valid.

Solution:

See User Attributes Validation Checks for more information on valid input parameters.

55001

Missing input parameter, {0}.

Possible Cause:

The required parameter is missing from the API request.

Solution:

Provide the required parameter.

55002

Insufficient input parameters.

Note: This is a C++ error code.

Possible Cause:

The API inputs are incomplete.

Solution:

Provide all the required inputs.

55003

Resource bundles not found.

Note: This is a C++ error code.

Possible Causes:

• ARCOT_HOME is not set.
• The required properties files are missing from the resourcebundles subdirectory in the conf directory.

Solution:

Ensure that the ARCOT_HOME environment variable is correctly set.

55004

Database error.

Note: This is a C++ error code.

Possible Causes:

• The connection to the database failed.
• An unexpected error occurred while writing to or reading from the database.

Solution:

1. Refer to arcotadmin.log and arcotuds.log for more information.

2. Retry the connection.

55010

Error while encrypting the data.

Note: This is a C++ error code.

Possible Causes:

• The connection to the HSM failed.
• An unexpected error occurred.
• The Server cache has not been refreshed.

Solution:

1. Refer to arcotadmin.log and arcotuds.log for more information.

2. Check HSM connection details.

3. Refresh the Server cache.

55011

Error while decrypting the data.

Note: This is a C++ error code.

Possible Causes:

• The connection to the HSM failed.
• An unexpected error occurred.
• The Server cache has not been refreshed.

Solution:

1. Refer to arcotadmin.log and arcotuds.log for more information.

2. Check HSM connection details.

3. Refresh the Server cache.

55012

Internal error occurred.

Note: This is a C++ error code.

Possible Cause:

An unexpected error occurred.

Solution:

Refer to arcotadmin.log and arcotuds.log for more information.

55100

Error while retrieving organization configuration data.

Note: This is a C++ error code.

Possible Causes:

• The specified organization was not found in the system.
• The connection to the database failed.
• The Server cache has not been refreshed.

Solution:

1. Refer to arcotadmin.log and arcotuds.log for more information.

2. Check the database connection details.

3. Refresh the Server cache.

50030

Search size limit exceeded the maximum value.

Note: This is a C++ error code.

Possible Cause:

Search returned more than the maximum configured limit.

Solution:

Refine your search criteria.

50031

Search base node context needs to be bound.

Possible Causes:

• The connection to LDAP organization failed.
• The specified LDAP connection details are not valid.

Solution:

Ensure that the LDAP connection details are correct and then retry.

50032

Search is not expected to return more than set limit values.

Note: This error is thrown by the retrieveUser API in context of LDAP organizations.

Possible Causes:

1. The user you specified is not unique in the system (LDAP). As a result, more than one user details were returned for the given UserID.

2. The UserID attribute is not mapped to the correct LDAP attribute.

Solution:

Ensure that the UserID is unique. Also verify the UserID attribute mappings.

50033

Search criteria is not valid.

Note: This is a C++ error code.

Possible Cause:

The search input that you provided is not valid.

Solution:

Provide valid search inputs.

50034

Unable to get supporting data access class.

Possible Cause:

• The connection to LDAP organization failed.
• The specified LDAP connection details are not valid.

Solution:

Ensure that the LDAP connection details are correct and then retry.

50035

LDAP node has to be created before referencing.

Possible Cause:

• The connection to LDAP organization failed.
• The specified LDAP connection details are not valid.

Solution:

Ensure that the LDAP connection details are correct and then retry.

50036

LDAP repository has to be initialized.

Possible Cause:

• The connection to LDAP organization failed.
• The specified LDAP connection details are not valid.

Solution:

Ensure that the LDAP connection details are correct and then retry.

50037

Context is not bound or cannot be created.

Possible Cause:

• The connection to LDAP organization failed.
• The specified LDAP connection details are not valid.

Solution:

Ensure that the LDAP connection details are correct and then retry.