chrome app player on ASUS chromebox hangs "waiting for application window"

  • 3
  • Problem
  • Updated 3 years ago
  • Solved
  • (Edited)
EDIT MARCH 21, 2018: Please note that all conversations related to Chrome OS in this Community should be considered obsolete and out of date. As announced in our new Community, Rise Vision is adding support for Chrome OS with a new version of Rise Player for Chrome OS.

To receive updates, make sure to subscribe to the Rise Vision Blog, or join the new Community and post questions.
=====================================================================================================================================================

Have an ASUS M004U Chromebox that had been successfully running the chrome app player (and some pretty demanding content) for over a month. The device was wiped, provisioned through the management console and Rise was deployed from the management console. Everything installed cleanly back in May, with no issues.

In August, the chromebox spent about 15-20 days off the network doing nothing. After hooking it all back up, things are different. 

Now when it is launched, the boot sequence completes, chrome comes up in kiosk mode and we halt here:


I have NOT deprovision / re-provision or taken any other remedial steps yet.
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb

Posted 4 years ago

  • 3
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Hi Dave,

I've not seen it sit on that window.  If you press CTRL+ALT+S, can you confirm the version of Chrome that is installed?  Also, can you confirm the date on the system to ensure that is accurate (I know with the native players, if the date resets - to something like 2011, then the Player doesn't start).

Thanks.
Photo of Digi Sign

Digi Sign

  • 232 Points 100 badge 2x thumb
Hi Neal,

This is the exact thing that happened to my asus chromeboxe after unplugging the ac. It loops forever.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Based on the answer Dave provided below, he was able to correct the problem by wiping out the Chromebox (one of the steps with reprovisioning).  His were enrolled, where I believe you said yours is just using Kiosk mode.

Can you try wiping out your Chromebox and reinstall the Chrome App Player to see if that corrects it for you?

Thanks
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Time and Date are accurate.

Chrome OS Version is 36.0.1985.143
Platform 5841.99.0 (Official Build) Stable

Thanks!
 
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Just as I was writing the last reply, the OS started updating.

Now on: 37.0.2062.119
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Dave,

I can nearly replicate what you're seeing if I unplug the network cable from my chromebox.  For me, it says its waiting for a network connection.  Is it possible that a firewall, or proxy is preventing the chromebox from getting out to the internet?  You can review what's needed here.

Thanks.
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
When I drop to the desktop, the network is there and ready. It is on WiFi and it spends about 3 seconds "looking" for the network and them moves on to the "waiting for application window".

It might be possible that it is having trouble with the WiFi that I just cant see. I will check that out.

Also I have noticed that is reporting in to the management services as recently as one minute ago, while the "wait" message was up. I think that rules out a one-off interface issue with firewalls and such? 
(Edited)
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Added ethernet to the allowed networks in chrome management and plugged up directly to the switch. Rebooted. Still getting "waiting on application window". Device desktop can still get everywhere. Device is reporting status to Chrome Management.

I think I am going to blow it away (or just de-provision), reload it and see what happens.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
It could be that something is corrupted and preventing it from starting up normally.  When you do get it back up and running, would you let us know what finally took care of it?

Thanks
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
Re-provisioned the device, re-entered the DisplayID and it started rock'n again. All Good! Thanks for the help.
Photo of Neal

Neal

  • 61,252 Points 50k badge 2x thumb
Excellent.  Good to hear it is back up and running.
Photo of Ed Juline

Ed Juline

  • 60 Points
How do you re-provision the device?
Photo of Dave

Dave

  • 886 Points 500 badge 2x thumb
Assuming the device was managed/enrolled in the chrome management console, instructions are here: https://support.google.com/chromeboxf...
Photo of b1alpha

b1alpha

  • 60 Points
I recently enrolled 4 managed asus chromboxes, and 3/4 of them ended up corrupted in that state of "waiting for application" I would love to hear more about a solution to prevent this corrupted state from occurring in the first place. How can I make google aware this is happening so often?
(Edited)
Photo of Dave

Dave

  • 2,836 Points 2k badge 2x thumb
I see this condition myself. Still no idea why some provision right out of the box and others do not. I am using only HP chromebooks and Asus Chrome Boxes in the management console. Nothing else.

What makes things slightly easier is putting the device into "reprovisioning required" mode in the console. This alleviates some steps in the deprovisioning/reprovisioning process. It does not prevent the "waiting for application window" issue from happening.

The only thing I have found that fixes this is deprovisioning and reprovisioning the device. In most cases, the Risevision Display ID must be reapplied.

This usually happens when my Display Devices are moved from one network or Wifi AP to another or when significant time has passed since the chromebox has been on the network (like in a powered down state).
Photo of Sanjay Kaler

Sanjay Kaler

  • 1,472 Points 1k badge 2x thumb
I believe this problem occurs if Chromebox doesn't have clean shutdown - unplugging power cable, pressing power button once etc.

From configuring the Chromeboxes to deploying them, if you need to disconnect Chromeboxes, make sure that you press the power button twice (Asus box or follow the manufacture's guide).

The solution to this problem in most situations is wiping out the device data (restoring to factory default) and running the Rise Player in kiosk mode again.

Regards,
Sanjay
Photo of Chris

Chris

  • 70 Points

Is there any update on this?

I am having the same problem, every time my chromebox doesn't shutdown properly I have to wipe the device to fix the player.  

Photo of Matthew Fisher

Matthew Fisher

  • 1,420 Points 1k badge 2x thumb
Chris,

I haven't been able to replicate this problem by simulating an unclean shutdown (pulling the plug).  If the accepted, albeit inconvenient workaround is to wipe and reconfigure the device--that may be the only choice.  However, if it seems to happen because of an unclean shutdown, does pressing ctrl-alt-s to exit out of kiosk mode and then do a clean shutdown help?

Thanks,

Matthew
Photo of Chris

Chris

  • 70 Points
Hi Matthew,

Thank you for the reply. I have tried that with no luck. i believe that this issue is isolated to only one of my chromeboxes.

I just tried to replicate the issue and could not on a new chromebox(specs below). 

HP Chromebox PC
HP Version 43.0.2357.134 (64-bit)

Platform 6946.86.0 (Official Build) stable-channel zako

Firmware Google_Zako.5219.30.0

Photo of Justin

Justin, Employee

  • 2,526 Points 2k badge 2x thumb
Chris,

Thanks for the info. We have many Chromeboxes running in the office here, including a HP Chromebox like yours, running the same versions, and we have not been able to replicate this issue.

Any other users seeing this problem?

Justin
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
So, we are getting this too now. After risevision update our devices turned off. After starting manually non-managed device on wifi, it gave us 'that' screen. I prepared replacement - another device, managed this time. It was working properly. But it gave us the same screen on site and is not connecting. Tried 2 different wifi access points. Same thing. What the hell is going on :) Looks like wifi problem at the same specific location because at work on wifi too it was all good.

So here is what we have. Two devices, managed and non-managed, were able to connect to wifi. However, RiseVision app was stuck on the "waiting..." screen in kiosk mode. Yet, if the app was launched from Chrome manually, everything was working fine (only RiseVision app on managed device requested player ID #). App was not able to start properly in kiosk mode. Both devices were working fine untill today's RiseVision update on Chrome 44.*
(Edited)
Photo of Matthew Schornstein

Matthew Schornstein

  • 224 Points 100 badge 2x thumb
We also had this occur on two managed devices this week. I do not know what caused the device to get into this state.
Luckily, we were able to work around it by 'reinstalling' the kiosk app. (Since managed, move to a sub-org that does not have Rise Vision kiosk app installed, wait a bit, reboot, then add back to the sub-org that has Rise Vision assigned). It is only a work around as you then have to re-add the Display ID to the app, but then all seemed to work correctly.
Photo of Darius - PRODO.us

Darius - PRODO.us, Champion

  • 26,850 Points 20k badge 2x thumb
Thanks Matthew. What bothers me the most is that this happened to both managed and non-managed devices at the same location. Non-managed went to this state right after shut down caused by update. We brought a fully working, tested managed device and it did the same. Funny, but on both of them Rise Vision works fine if started from Chrome OS manually. So, we left the old device working and took managed home for testing on different network. It was not working properly there too, so I simply wiped it out.
Photo of Wendi Borden

Wendi Borden, Champion

  • 6,028 Points 5k badge 2x thumb
Running into a similar problem now. We got a brand new Chromebit, released last week. I've tried a powerwash so far with the same result, hangs on "Waiting for application window.."

Managed, Chrome 46.0.2490.71
(I realize at this time RV recommends 44.x, but it's brand new, no way to roll back I'm aware of)

Believe I'll give it a shot with another app first, then try this de-provision / re-provision step.

I started a new thread since it is different hardware:

https://community.risevision.com/rise_vision_inc/topics/new-chromebit-hung-on-waiting-for-applicatio...