Error Codes

{0}

Total execution time for {0} {1} Graph API call: {2} ms

Start with validateAndRefershToken(), jobId ={0}, proccessName ={1}, activityId ={2}, threadName ={3}

{0}. Input:\n{1}

End with validateAndRefershToken(), jobId ={0}, proccessName ={1}, activityId ={2}, threadName ={3}

{0}. Output:\n{1}

Before token update call, Shared resource key-values: userName ={0}, appId ={1}, expiryOn ={2}, jobId ={3}, proccessName ={4}, threadName ={5}, refreshToken ={6}, accessToken={7}

Request Data:\n{0}

After token update call, Shared resource key-values: userName ={0}, appId ={1}, expiryOn ={2}, jobId ={3}, proccessName ={4}, threadName ={5}, refreshToken ={6}, accessToken={7}

Response Code: {0} {1}

Token is valid, so no refresh or update required.

Adding new configuration for Shared Resource with name [{0}].

Performing {0} {1} operation.

Deleting Configuration for Shared Resource with name[{0}].

Executing Graph API Call for {0} {1} operation.

Execution of {0} {1} operation completed.

BW Unobfuscation is getting applied on password field.

BW Unobfuscation is failed and return the null value for given password field, so sending password value as it is to server.

ERROR_CATCH_EXCEPTION={0}

An internal error occurred in the LDAP server.

errorCode=500001

Error creating shared resource {0}. Exception:{1}

errorCode=500001

{0}

TA LDAP server could not correctly interpret the request sent by your client because the request does not strictly comply with the LDAP protocol.

{0}

The search operation could not be completed within the maximum time limit.

{0}

The search found more than the maximum number of results.

{0}

Value returned by an LDAP compare operation if the specified attribute and value is not found in the entry.

{0}

Value returned by an LDAP compare operation if the specified attribute and value is not found in the entry.

{0}

The specified authentication method is not supported by the LDAP server that you are connecting to.

{0}

A stronger authentication method (more than LDAP_AUTH_SIMPLE)is required by the LDAP server that you are connecting to.

One or more Mandatory Input fields have blank data.

The LDAP server is referring your client to another LDAP server.

Illegal input data found.

EX_REFERRAL=[LDAP v3] The server does not hold the requested entry. The referral field of the server's response contains a reference to another server (or set of servers), which your client can access through LDAP or other protocols. Typically, these references are LDAP URLs that identify the server that may contain the requested entry.

Shared resource fields does not have valid data.

[LDAP v3] The adminstrative limit on the maximum number of entries to return was exceeded.

No access to input XSD file.

[LDAP v3] The server received an LDAP v3 control that is marked critical and either (1) is not recognized or supported by the server, or (2) is inappropriate for the operation requested.

[LDAP v3] A secure connection is required for this operation.

[LDAP v3] While authenticating your client by using a SASL (Simple Authentication Security Layer) mechanism, the server requires the client to send a new SASL bind request (specifying the same SASL mechanism) to continue the authentication process.

The specified attribute could not be found.

The specified attribute is not defined.

An inappropriate type of matching was used.

An internal error occurred in the LDAP server.

The request contains invalid syntax.

The entry specified in the request does not exist.

A problem occurred with an alias.

The specified distinguished name (DN) uses invalid syntax.

The specified entry is a "leaf" entry (it has no entries beneath it in the directory tree).

An error occurred when dereferencing an alias.

The authentication presented to the server is inappropriate.

The credentials presented to the server for authentication are not valid.

The client is authenticated as a user who does not have the access privileges to perform this operation.

The LDAP server is busy.

The LDAP server is unavailable.

The LDAP server is unable to perform the specified operation.

A loop has been detected.

The "server-side sorting" control was not included with the "virtual list view control in the search request.

An index range error occurred.

A naming violation has occurred.

The requested operation will add or change data so that the data no longer complies with the schema.

The requested operation can only be performed on an entry that has no entries beneath it in the directory tree (in other words, a "leaf" entry).

The specified operation cannot be performed on a relative distinguished name (RDN).

The specified entry already exists.

You cannot modify the specified object class.

[LDAP v3] The client attempted to move an entry from one LDAP server to another by requesting a "modify DN" operation. In general, clients should not be able to arbitrarily move entries and subtrees between servers.

General result code for other types of errors that may occur.

The LDAP server cannot be contacted.

The operation could not be completed within the maximum time limit.

When calling a constructor or method from your client, one or more parameters were incorrectly specified.

Your LDAP client failed to connect to the LDAP server.

The request is not supported by this version of the LDAP protocol.

The requested control is not found.

No results have been returned from the server.

More results are being returned from the server.

Your LDAP client detected a loop in the referral.

The number of sequential referrals (for example, the client may be referred first from LDAP server A to LDAP server B, then from LDAP server B to LDAP server C, and so on) has exceeded the maximum number of referrals (the LDAPv2.REFERRALS_HOP_LIMIT option).

The socket factory of the connection is not capable of initiating a TLS session.

IOException occurred while retrieving XML Output for activity [{0}].

An operation has been canceled using the Cancel extended operation.

The server has no knowledge of the operation requested for cancelation.

It is too late to cancel the outstanding operation.

the identified operation does not support cancelation or the cancel operation could not be performed.

A unknown result code.

Specified file {0} is not found.

Not specify the file name.

Accesslog has not been set up, please set up this entry for OpenLDAP.

Create JNDI Connection failed due to {0}

It is safe to do so when it is unable to perform the operation

Attribute(s) will be monitored is(or are) not recognized, it doesn't(they don't) exist in LDAP Server.