Database Error Messages

There are a number of reasons why the SecurID server would refuse a pincode:

• The user might not have permission to make up his own pincode.
• The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters.
• The pincode contains any non alphanumeric characters.

Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.

There are a number of reasons why the SecurID server would refuse a pincode:

• The user might not have permission to make up his own pincode.
• The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters.
• The pincode contains any non alphanumeric characters.

Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.

There are a number of reasons why the SecurID server would refuse a pincode:

• The user might not have permission to make up his own pincode.
• The pincode was either too short or too long. Valid pincodes consist of minimal four, but no more than eight characters.
• The pincode contains any non alphanumeric characters.

Reexecute the operation and make sure to use a pincode that satisfies the above requirements. If the problem persists, turn on tracing at the Oracle Server side of the connection and examine the trace file for the exact error.