Android Enterprise enrollment fails with “work account creation failed” on Honeywell CT37Solved

Participant
Discussion
1 day ago Aug 03, 2026

I’m seeing frequent “work account creation failed” errors while enrolling Honeywell CT37 devices running Android 14.

Enrollment type is Android Enterprise, and the management mode is Device Owner. So far, the only thing that has worked is factory resetting the device and trying the enrollment again, but that is taking a lot of time during staging.

Is there a better way to recover from this error without wiping the device every time?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
1 day ago Aug 03, 2026
Marked SolutionPending Review

Hey @it_christo,

This can happen during Android Enterprise Device Owner enrollment if the work account creation step cannot complete successfully with Google services.

Common causes include:

  • A temporary network drop during Google token exchange.
  • Delayed Google Play Services registration on a freshly booted device.
  • Incorrect date, time, or time zone on the device, which can cause Android 14’s time-sensitive cryptographic handshake with Google servers to fail.

You do not need to factory reset the device every time this happens. If the device is listed in the Hexnode portal and the work account creation status shows as failed, you can retry the process remotely:

  1. Go to Manage > Devices.
  2. Open the affected Android device.
  3. On the device summary page, check the Enrollment details section.
  4. Find Work Account Creation.
  5. If the status is Failed, click Retry.

This re-initiates the work account creation process and prompts the device to contact Google’s API servers again without wiping the device.

For prevention, before scanning the enrollment QR code or entering the enrollment token on a fresh device, manually verify that the date, time, and local time zone are accurate. This is especially useful on Android 14 devices where an incorrect system clock can break the secure enrollment handshake.

Best Regards,
Isabel Lora
Hexnode UEM

Marked SolutionPending Review
Participant
21 hours ago Aug 03, 2026
Marked SolutionPending Review

Thanks @isabel_lora, just to confirm, the retry option is only visible after the device has already appeared in Hexnode, right? In our case, the device reaches the portal but fails at the work account creation stage.

Marked SolutionPending Review
Hexnode Expert
20 hours ago Aug 03, 2026
Marked SolutionPending Review

Yes @it_christo. The Retry option is relevant when the device record exists in the portal and the enrollment details show that work account creation failed.

If the device never reaches the portal at all, the issue would need to be checked from the enrollment method, network, QR/token entry, or device-side setup flow.

Best Regards,
Isabel Lora
Hexnode UEM

Save