Status codes and messages

VIP uses a variety of status codes and messages based on certain causes and conditions.
VIP status messages and codes appear in the result.status field of the VIP Real-time Transaction Reporting Service JSON record returned from VIP User Services.
VIP status codes and messages lists the status codes and messages that VIP User Services returns.
VIP status codes and messages
Status Code
Message
Cause and Solution
0000
Success.
The operation completed successfully. No action required.
6001
Invalid account.
  • The account does not exist or is not in an ACTIVE state. Create the account or make the account active. (createUser, deleteUser, removeCredential only)
  • The jurisdiction hash provided does not match a known account. Provide the correct jurisdiction hash or perform the operation on a different account (addCredential only).
6002
User already exists.
The user ID already exists. Select another user or perform another operation.
6003
User doesn't exist.
The given user ID does not exist. Create the user or perform a different operation.
6004
Credential ID is not valid.
The credential ID cannot be found. Either add the user or perform the operation on a different user.
6005
Internal error.
An internal error occurred. Retry the operation. If this condition continues, contact Symantec Support.
6006
Invalid credential type.
The credential type that has been specified is not valid. Provide the correct credential type, bind a new credential to the user, or perform the operation on a different user.
6007
No binding exists between user and credential.
The credential that is specified in the operation is not assigned to the user that has been specified. Assign the credential to the user or select another credential.
6008
User does not have an enabled credential for the given credential type.
No credentials of the type specified are enabled. Enable a credential of the type specified.
6009
Authentication failed.
The security code that was provided is invalid. Retry the operation with a valid security code.
600A
Credential type not supported.
The operation does not support the credential type specified. Select another credential type.
600B
Schema validation failed.
The XML schema in the request is invalid. Review the WSDL version and XSD version, and verify that the XML is well-formed and that all mandatory elements are populated.
600C
Bad credential state.
The credential state value in the system is invalid. Contact Symantec Support.
600D
Operation not allowed in current state of credential.
The credential state does not support the specified operation. Change the credential state or select another credential and retry the operation.
Push credentials only: If a user is locked out for too many failed push authentication attempts, additional information is included in the
detailMessage
attribute of the
authenticateCredential
response and in the event log for the transaction:
All push-enabled credentials are throttled
600E
Client certificate is revoked.
The VIP Manager certificate has been revoked. Obtain and install a valid certificate and retry the operation.
600F
Credential is revoked.
The credential that has been specified has been revoked. Select another credential and retry the operation.
6010
The account is not authorized to perform this operation.
The requester account is not a super administrator account or the parent of an
OnBehalfOf
account. Modify the permissions and retry the operation, or retry the operation with the correct permissions.
6011
Maximum enabled bindings limit reached. Please unbind or disable a binding before retrying.
The maximum number of enabled credentials has been assigned to the user. Disable or remove one or more credentials from the user before you can assign another enabled credential.
6012
Maximum allowed bindings limit reached. Please unbind an existing binding before retrying.
The maximum number of credentials (disabled or enabled) has been assigned to the user. Remove one or more credentials from the user before you can assign another.
6013
Credential has expired.
The credential that has been specified expired. Renew this credential or select another credential and retry the operation.
6014
Operation is not supported.
The operation that you requested is not supported for the credential type. Select another credential and retry the operation.
6015
Invalid input.
One of more of the values that were provided are invalid. Review your entries and retry the operation.
6016
Token has not been previously registered for this account.
The credential that you specified has not been registered to this VIP account. Register the credential and retry the operation.
6017
Temporary password is not set.
You attempted to perform an action for a temporary password, such as clear a password. However, no temporary password has been set for this user. Set a temporary password or choose another action.
6018
Unable to send SMS to given number through gateway.
The SMS text message was not delivered because:
  • The phone number that you provided in the request is not a mobile device
  • The phone does not allow SMS text messages
Retry the operation with a valid phone number.
6019
Unable to send message to voice gateway for the given number.
The voice message cannot be delivered because:
  • The phone number that is provided in the request is not a mobile device
  • The user did not answer
Retry the operation with a valid phone number. Ensure that the user expects a message.
601A
Expiration date must be later than the current time, and cannot exceed the validity period.
The temporary security code expiration date is invalid. Select an expiration date that occurs in the future. However, the expiration date cannot occur later than the validity period that was set for the account.
601B
Operation not allowed in current user status.
You attempted to perform an action on a token that is not in the correct state, such as setting a temporary security code for a disabled user.
Check the user status and retry the operation.
601C
Client certificate required to perform the requested operation.
Install a client certificate before you can perform this operation.
601D
The user has too many SMS or Voice Credentials.
You attempted to register a credential for a user who has reached the maximum number of credentials that are allowed. Remove or have the user remove one or more credentials and try the operation again.
601E
Order for the credential type already fulfilled or expired.
The credential order cannot be fulfilled because all credentials of this type have been issued or the credential order has expired. Contact Symantec Support for additional credentials or assistance with this order.
601F
Invalid user PIN.
The user PIN entered does not match the PIN that the user created.
6020
User PIN value does not meet policy settings for this account.
The user PIN does not match one or both of these settings in the End User PIN Policy because of:
  • Minimum character length
  • Character restrictions
6021
User PIN is not enabled for this account.
Enable the PIN in the End User PIN Policy.
6022
IA policy must be enabled for this account.
The Intelligent Authentication policy has not been enabled in VIP Manager.
6023
Event for the ID passed in feedback is not found.
EventID
that was provided by
confirmRisk
or
denyRisk
was not found.
6024
Event for the ID passed in feedback is not considered risky.
EventID
that was provided by
confirmRisk
or
denyRisk
. However, the
evaluateRisk
assessment does not consider the event suspicious.
6025
Multi-user credentials are disabled for this account. The given credential is already bound and enabled under a different user.
You cannot register the credential to more than one user in the organization at any one time.
6026
Credential is already registered for this account.
The credential being registered is already registered to this account.
6027
VIP Trusted Device is not enabled for this account.
Enable Trusted Device in the Remembered Devices policy in VIP Manager.
6028
The transaction parameters must be set in VIP Manager for this account.
Set any transaction risk parameters, such as a daily transaction amount and a maximum transaction amount, for the account in VIP Manager before you call this API.
6029
IA service is currently not available.
Symantec IA service is currently not available. Contact Symantec Support for further assistance.
602A
IA transaction monitoring policy must be enabled for this account.
The Intelligent Authentication transaction monitoring policy has not been enabled in VIP Manager.
602B
The encrypted client key in IAAuthData cannot be decrypted.
It failed to decrypt the encrypted client key in
IAAuthData
for the VIP Mobile SDK. Re-encrypt the client key with the latest version of the public key.
602D
Invalid friendly name. Friendly name cannot include $ # ! " / ? \ or *.
The friendly name includes special characters that are not supported.
602E
Mobile push is not enabled for this account.
The administrator has not enabled VIP Access Push on the user’s account.
6040
Mobile push request sent.
A push notification was sent to the user’s registered mobile devices.
6041
Unable to find mobile push enabled credentials.
None of the user’s registered mobile devices have a version of VIP Access that supports the VIP Access Push Feature.
6042
Error sending mobile push request.
An error occurred when sending the push notification to the user’s registered mobile devices.
6043
Credential does not support mobile push.
The user’s installed version of VIP Access does not support the VIP Access Push feature.
604C
Denied by Mobile Token Validation Policy.
The administrator has disabled security code validation for the account or for the group to which the user is a member.
604D
Blocked by Non-US SMS or Voice policy.
The administrator has blocked SMS messages and Voice calls to non-US phone numbers.
604F
Credential does not support number challenge.
The user's credential does not support the number challenge feature.
6603
Mobile token validation is not allowed per policy.
The administrator has disabled security code validation for the account or for the group to which the user is a member.
7000
Mobile push request approved by user.
The user approved the push notification on the mobile device.
7001
Mobile push request in progress.
A push notification has been sent, but the user has not approved or denied the request.
7002
Mobile push request denied by user.
The user denied the push notification on the mobile device.
7003
Mobile push request changed.
The user issued a subsequent push notification.
7004
Mobile push request expired.
The user did not respond to the push notification before it timed out, or the user responded to a subsequent push notification.
7005
Mobile push request not found.
The push notification was not found.
7006
Mobile push request not completed.
The push notification cannot be initiated or the response was not received.
7008
Could not authenticate user based on requested parameters (requestParameters).
The authentication requirements set in the
requestParameters
flag could not be met (for example, local authentication failed). Additional information is available in the response Detail Codes.
See also Detail Codes.