- 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a month ago
17:34:14.370 I [RemoteLoggerImpl.kt:onSuccess:482] SetupStep: STEP_SETUP_FCM, status: SUCCESS
17:34:14.371 I [CloudDpsClientImpl.java:registerDevice:436] Registering device in unified policy mode.
17:34:14.374 I [OverrideLayer.java:loadFromFile:98] No override for gservices
17:34:14.376 I [RemoteLoggerImpl.kt:onSuccess:462] Logging setup event: 3
17:34:14.376 I [RemoteLoggerImpl.kt:onSuccess:475] SetupStep: STEP_REGISTER
17:34:14.384 I [OverrideLayer.java:loadFromFile:98] No override for gservices
17:34:14.384 I [CloudDpsClientImpl.java:logMessage:1991] Request #1109332922392914000 will be sent to server side
17:34:14.457 I [26257] vop.f(259): ItemStore: Not cached: com.google.android.apps.work.clouddpc
17:34:14.575 I [26257] vop.f(259): ItemStore: Not cached: com.oplus.ocloud
17:34:14.881 E [26127] bml.a: Unexpected response code 420 for https://m.google.com/clouddps/registerDevice?devicetype=Android&agent=TP1A.220905.001
17:34:14.883 W [RetryingFuture.java:terminalExceptionCaught:165] RetryingFuture caught terminal exception
bmh
at bml.a(PG:1014)
at bml.run(PG:6)
Caused by: ebx
at clf.v(PG:137)
at gch.a(PG:130)
at ifw.call(PG:484)
17:34:14.883 I [CloudDpsClientImpl.java:logMessage:1991] Request #1109332922392914000 failed due to execution exception
17:34:14.886 E [SetupInteractorImpl.kt:onSetupFailed:96] Setup failed:
cim: Setup failed. FAILURE_REASON_SERVER_OTHER. UNKNOWN_SETUP_STEP. ERROR_SERVER
Caused by: cks: Request failed
at clf.y(PG:802)
at clf.v(PG:137)
at gch.a(PG:130)
at ifw.call(PG:484)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at kpr.run(PG:11)
at gpm.run(PG:126)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
at java.lang.Thread.run(Thread.java:1012)
Caused by: ebx
at clf.v(PG:137)
at gch.a(PG:130)
at ifw.call(PG:484)
17:34:14.887 I [EventLogManagerImpl.kt:logMessage:1641] Event logged: SetupStepFinished details: [setupStep=register, setupStepStatus=false, failureMessage=cks: Request failed
ebx] metadata: [isNetworkConnected=true]
17:34:14.890 I [VanillaNotificationHelperImpl.java:showProfileSetupFailedNotification:138] Profile setup failed notification shown
17:34:14.891 I [RestoreUtilImpl.kt:getRestoreIntent:66] Getting restore intent
17:34:14.892 W [RestoreUtilImpl.kt:canUseMigrationApp:170] com.google.android.apps.pixelmigrate is not installed as a system app.
17:34:14.892 W [RestoreUtilImpl.kt:canUseMigrationApp:170] com.google.android.apps.pixelmigrate is not installed as a system app.
17:34:14.893 I [RestoreUtilImpl.kt:getRestoreIntent:66] Getting restore intent
17:34:14.893 W [RestoreUtilImpl.kt:canUseMigrationApp:170] com.google.android.apps.pixelmigrate is not installed as a system app.
17:34:14.893 W [RestoreUtilImpl.kt:canUseMigrationApp:170] com.google.android.apps.pixelmigrate is not installed as a system app.
17:34:14.899 E [SetupV2LoggerImpl.kt:logSetupStepException:91] [CONTEXT cel_metadata="# logs.proto.wireless.performance.mobile.ExtensionMetric$MetricExtension@e5e4581b\n[7] {\n}" ]
cim: Setup failed. FAILURE_REASON_SERVER_OTHER. UNKNOWN_SETUP_STEP. ERROR_SERVER
Caused by: cks: Request failed
at clf.y(PG:802)
at clf.v(PG:137)
at gch.a(PG:130)
at ifw.call(PG:484)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
i am trying to provision work profile, not working from last 2 days , showing `Try setup again later. Some technical issues are preventing setup right now.`i have done everything but nothing works like recreated enrollment token etc.
- restrict android personal profile in Admin discussions
- Unlinking Zero-Touch from MDM provider in Admin discussions
- Few customers not able to install applications in personal profile after work profile is setup. in Admin discussions
- Basic WiFi-profiles (configuration profiles) do not deploy into Device in Admin discussions
- Managed Google Play Android enrollment by intune.microsoft.com in Admin discussions