- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 11:33 AM
Few of our users are facing `Try setup again later. Some technical issues are preventing setup right now.` error during work profile provisioning. Below are the device logs
11-06 19:49:04.078 19772 25409 I clouddpc_CloudDpsClient: Registering device in unified policy mode. 11-06 19:49:04.079 19772 25409 E clouddpc_CloudDpsClient: Error registering device, no auth token or enrollment token. 11-06 19:49:04.077 3816 3816 D RegisteredNfcFServicesCache: Service unchanged, not updating 11-06 19:49:04.079 19772 25398 I clouddpc_crw: Logging setup event: 3 11-06 19:49:04.080 19772 25398 I clouddpc_crw: SetupStep: STEP_REGISTER 11-06 19:49:04.080 2408 2447 D SecureElementService: getReaders() for com.android.nfc 11-06 19:49:04.083 19772 19772 I clouddpc_SetupActivity: setup ui state changed: # com.google.android.apps.work.clouddpc.base.util.setup.setupstate.proto.SetupState$SetupUiState@8dc35 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: Setup failed: 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: cgg: Setup failed. FAILURE_REASON_SERVER_OTHER. ERROR_SERVER 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: Caused by: cin: Error registering device, no auth token or enrollment token. 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at ciz.r(PG:3) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at ffc.a(PG:9) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at isj.call(PG:23) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at java.util.concurrent.FutureTask.run(FutureTask.java:264) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at jfu.run(PG:2) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at hmb.run(PG:12) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644) 11-06 19:49:04.083 19772 25388 E clouddpc_fhk: at java.lang.Thread.run(Thread.java:1012) 11-06 19:49:04.085 19772 23345 I clouddpc_VanillaNotific: Profile setup failed notification shown
It suggests that no auth token or enrollment token was found, the qr code scanned does have a enrollment token so not very sure why this is happening. Any help would be appreciated. Thank you.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2023 12:48 PM
Wiping the cache/storage for Android Device Policy app from settings before enrolling with EMM solved the issue for us.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 12:23 PM
We are using Android Management API to provision and mange these devices.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 12:25 PM
I’ve been seeing some issues today with amapi enrollment so that might be it. If you’re sure that the QR Code token is valid wait a little bit before trying again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 01:08 PM
Okay thank you, we have received about 10 customer reports about this in the last 3 weeks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 01:11 PM
I've only encountered this issue today, you should create a support ticket in the http://emm.androidenterprise.dev if you've double checked your own code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2023 12:48 PM
Wiping the cache/storage for Android Device Policy app from settings before enrolling with EMM solved the issue for us.
- Android Auto with COPE in Admin discussions
- Android device management - Unable to enroll: DEVICE_MODE_QUARANTINED in Admin discussions
- Smart watch notifications for work profile are being blocked by Android Management Policy in Admin discussions
- Work Profile Environment Only in Admin discussions
- Zero trust not pushing profiles to devices in Admin discussions