Devices stuck at "configuring google account" pending action

Solved
AH
Andy Halkyard
Co-operative Group Ltd.

Hi, 

We have recently started staging a number of Android devices with Managed Google Play accounts, and today found that all of the devices were getting stuck for quite a long time at the pending action "configuring google account" phase of staging. 

We have staged a handful of devices at a time before with the odd device struggling at that bit, but never have we had the entire lot grind to a halt! 

Is this something people have seen before?

7 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
7 years ago

On top of Wifi congestion suggested by Edgar,  Google's server supplying the required service modules may sometimes be the bottleneck.  It can be due to network loading/maintenance of Google's server serving your region, or due to upgrade/maintenance of the service module(s) themselves.  

Previously, we encountered similar problem.  We could do nothing extra on the devices, but they all eventually got updated when we powered them up again two days later.

Solution
AG
Allen Gulbrand
7 years ago

Ha. Try this. Go to the settings>accounts>Remove the account that is there. Click user action pending and tap the google one a few times. Does it go away?

EG
Edgar Gomez
7 years ago

Hello

I´ve seen that, depending on the device version, it needs to update Google Play Store and Google Play Services, before it configures the Google account for the device. So it may take long if you have a lot of devices connected to the same wifi.

AH
Andy Halkyard
7 years ago (edited 7 years ago)

Thanks to you all for your responses, sadly it looks like a Server side issue and SOTI are looking into it now for us. 

S
Stakvik
7 years ago

Hello Andy

What was needed to be fix in this case?
We are deployig MobiControl v14.1.8 in a closed enviroment and are getting the same issue on Android 6 units.

MobiControl at first we had to set Global Proxy settings so it would reach both Google and Soti Services but units themself are in a closed network.

I belive units needs to connect to Google Services to update whit correct version and such.
Do you have any information you could share about the solution?

LN

Hi,

For the enrollment process you need access to the internet on the devices, if you don't, you can use the master phone with the staging app with cellular sharing, and once you got through to the desktop, switch to the wifi that has access to mobicontrol.

You can then switch back to the cellular network to update google services and after that again on the corporate network to have everything set on the mobicontrol side.

Many steps, but it will eventually get you there.

Android enterprise is meant for devices that can access google services. You can get it to work otherwise, but you will be limited. The use of a corporate play store won't work without the devices accessing google. Instructions are sent from mobicontrol to google, and then google will push to the devices.

Standard provisioning like packages, scripts, messaging and remote control will still work of course.

JW
Johan W
6 years ago

This actually solves the problem very good!

GV

I have 3 Huawei P20 Lite smartphones with Android 8.0 and Mobicontrol Android Enterprise device agent 13.6.0 Build 1567 installed, enrolled, sucribed and connected to a Mobicontrol Deployment Server (14.2.2.1170) in a Wifi Network with dedicated 50MB internet access that have been online for two days now and still stucked in "Configuring Google Account" pending action screen.

I already did all the suggested actions in this post, factory reseting the device, changing to a cellular network, removing the google account, adding manually de google account for Android Enterprie of my company, removing it, etc. and nothing is happening.

I really do not thing this issue should be considered as solved.

Any other suggestions?

SS
Support Staff Account
6 years ago (edited 6 years ago)

Hi Guillermo Vallejo

Thank you for requesting an answer from SOTI Support Staff.

As this has been resolved for the original poster of in this thread, our intention is to close the post to further replies.  If you are having a similar issue that isn't resolved by the solutions provided in this thread feel free to copy your post into a new thread and we can address it separately. 

That way we can get the particulars and differences from your experience and address theses differences as possible symptoms of the issue you are experiencing.

Thank you in advance for your co-operation.

GV

Thanks, I already opened a new thread...

This has not been resolved in our case and I am trying to contact local support to resolve.

I would like to know how solution was implemented for Andy Halkyard who was the one who opened this tread and he never answered how it was solved. Apparently support staff helped him directly