Symptoms or Error
There are two use cases which spill out different error message depending on the enrollment state. One being a new enrollment while the other is for an already enrolled device.

Solution
Here are the observation when using an iOS device.

As part of a new enrollment you will experience that the MDM portion go through such

  1.  A successful authentication
  2. Successful acceptance of the “Terms and Conditions”
  3. Successful installation of the profiles.

Once the profiles have been installed Secure Hub triggers the MAM portion. This does not go through, throwing up the following error “An error occurred. The enrollment will stop.

What could be the possible cause. (Please refer to the Problem Cause section below)

User-added image

The second scenario is of an already enrolled device.

When the user taps on the Store the error displayed in the popup window reads ” You may need to contact you administrator to verify your sign-on credentials.

What could be the possible cause. (Please refer to the Problem Cause section below)

User-added image

and if the user is already in the Store and taps on an app the error display is “Failed to get application details, please try again later.

What could be the possible cause. (Please refer to the Problem Cause section below)

User-added image
Here are the observation when using an Android device.

​As part of a new enrollment you will experience that the enrollment is successful however, Secure Hub is enrolled only in the MDM mode and not the MAM.

For example if PIN auth is configured on XenMobile, the user is not prompted to enter the PIN and Secure Hub brings up the following message.

User-added image

Secure Hub however lets you proceed further to the following screen as below.

User-added image

The only option we see is Home within Secure Hub. The options such My Apps and Store do not show up.

User-added image

If the Android device is already enrolled following are the error messages observed.

User-added image
User-added image

Problem Cause
Though there may probably multiple reasons, usually the above errors show up when the TLS v1.2 is not enabled on the NetScaler Gateway VIP. Please make sure you have the TLS v1.2 enabled and try again.