Device activation failed.

Device activation is part of authorization processing.
This code notifies the application that processing did not succeed this time, but may succeed if another authorize call is made. See Authorize.

Enterprise activation failed.

Enterprise activation is part of authorization processing.
This code notifies the application that processing did not succeed this time, but may succeed if another authorize call is made. See Authorize.

This code is set in the scenario that the user keyed and sentcredentials that were rejected, and then cancelled authorization.

Push Connection failed to open but is required to complete authorization.

This code notifies the application that authorization processing did not succeed this time, but may succeed if another authorize call is made.
See Authorize and GDPushConnection.

User not entitled.

Authorization processing has completed, but the user is not entitled to use this application.

This code notifies the application that the BlackBerry Dynamics container has been wiped of all application data and authentication credentials.

If entitlement was withdrawn in error then, after reinstating entitlement, the following steps must be taken. The user must terminate the application on the device using the native task manager, and then restart the application.The application will then open as if being started for the first time.The user will then have to enter a new activation key.

This code is utilized when the end user is not entitled to any version of the application. Compare the GDErrorAppVersionNotEntitled code, below.

User not entitled to this version.

Authorization processing has completed, but the user is not entitled to this version of this application.

This code notifies the application that the BlackBerry Dynamics container has been locked and is not accessible.

If entitlement to the application version is later granted, or reinstated, then the lock is removed. The device must be on-line and able to connect to the BlackBerry Dynamics infrastructure, and the user will have to re-authenticate, in order to complete the removal of the lock.

This code is utilized when the end user is entitled to at least one other version of the application, but not to the current version. Compare the GDErrorAppDenied code, above.

User inactive.

The enterprise's security policies specify a time after which the application is to be locked, and the user has now been inactive for a period that exceeds this time.
In effect, the user's authorization to access the application data has been withdrawn.

This code notifies the application that the BlackBerry Dynamics lock screen is active and therefore the application's own user interface must not be made active.

The locked condition will be cleared when the user enters their password, at which point the application will be notified with a new event.

Policy violation block.

The enterprise's security policies specify a condition under which access is to be blocked, and that condition has occurred.
In effect, the user's authorization to access the application data has been withdrawn.

This code notifies the application that its user interface must not be made active. (Compare GDErrorWiped, below.)

This code may be set when, for example, connection to the BlackBerry Dynamics infrastructure has not been made for a specified interval. If the condition is cleared, the application will be notified with a new event.

Policy violation wipe.

The enterprise's security policies specify a condition under which the secure container is to be wiped, and that condition has occurred. This code notifies the application that the container has been wiped of all application data and authentication credentials. (Compare GDErrorBlocked, above, which also gives an example of a policy condition.)

After a device wipe, the application cannot be run until the following steps have been taken. The user must terminate the application on the device using the native task manager, and then restart the application. The application will then open as if being started for the first time. The user will then have to enter a new activation key.

Remote lock-out.

Either an enterprise administrator has locked the user out of the application, or the security password has been retried too often.
In effect, the user's authorization to access the application data has been withdrawn. This code notifies the application that its user interface must not be made active.

The user's authorization will remain withdrawn until an enterprise administrator removes the lock, and the end user has entered a special unlock code at the device.

Password change required.

The user's security password has expired, or no longer complies with enterprise security policy.
In effect, the user's authorization to access the application data has been withdrawn. This code notifies the application that the BlackBerry Dynamics password change screen is active and therefore the application's own user interface must not be made active.

Internal error: Secure store could not be unlocked.

Programmatic activation connection failed.

It was not possible to establish a data connection for programmatic activation. This code notifies the application that programmatic activation did not succeed this time, but may succeed if another programmatic authotize is made when a data connection can be established from the mobile device. See Authorize.

Programmatic activation credentials failed.

The credential values supplied to the programmatic activation API were rejected during some stage of activation processing. This code notifies the application that programmatic activation did not succeed this time, but could succeed if another programmatic authorize is made with different credential values. See Authorize.

Programmatic activation server communication failed.

A data connection was established but communication with a required server resource subsequently failed. This code notifies the application that programmatic activation did not succeed this time, but could succeed if another programmatic authorize is made later. See Authorize.

It is recommended not to make repeated attempts at programmatic activation with no delay between attempts. Instead, an exponential back-off algorithm should be used to calculate a delay.

Programmatic activation failed.

A general failure occurred during programmatic activation processing. This code notifies the application that programmatic activation did not succeed this time, but could succeed if another programmatic authorize call is made. See Authorize.