Anyone know how to fix this issue? It started happening seemingly at random. I've tried rebooting the host and clearing my browser cache, along with using a variety of other browsers.
The error reads
Unhandled Exception
Unfortunately, we hit an error that we weren't expecting.
The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.
And the more info button reveals
Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
Version: 1.4.0
Build: 3959074
ESXi: 6.0.0
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.89 Safari/537.36
Exception stack:
Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
at Error (native)
at https://10.0.1.20/ui/scripts/main.js:252:20611
at l (https://10.0.1.20/ui/scripts/main.js:254:12567)
at k.$apply (https://10.0.1.20/ui/scripts/main.js:254:16690)
at updateBodyOverflow (https://10.0.1.20/ui/scripts/main.js:276:181)
at new <anonymous> (https://10.0.1.20/ui/scripts/main.js:276:497)
at e (https://10.0.1.20/ui/scripts/main.js:253:3861)
at Object.instantiate (https://10.0.1.20/ui/scripts/main.js:253:3997)
Hi,
We fixed this issue some time ago, and will be releasing an updated version with the next 6.0 Patch release.
For now, you could install the latest fling release: labs.vmware.com/flings/esxi-embedded-host-client
Hi Goldman60,
Can you tell me if you are connecting to ESXi or vCenter?
Can you check if your web client services run properly?
Can you check if your firewall block web client ports & try to turn of your firewall to test it if you can connect.
Can you provide me a screenshot of error?
Can you connect to the host via the c# client, enable SHS for the host the SSH to the host.
Check services are running and check the logs
Hi,
We fixed this issue some time ago, and will be releasing an updated version with the next 6.0 Patch release.
For now, you could install the latest fling release: labs.vmware.com/flings/esxi-embedded-host-client
This does seem to have stopped the problem, thanks!
The same error is occuring when using ESXi 6.5 and the chromium browser.
Version of chromium:
Chromium | 57.0.2977.0 (Developer Build) (32-bit) |
Revision | ef911f1fd846f9116ec49c42dded7af7a6b6c525-refs/heads/master@{#442226} |
OS | Windows |
JavaScript | V8 5.7.410 |
Error from ESXi:
Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
Version: 1.8.0
Build: 4516221
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2977.0 Safari/537.36
Exception stack:
Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
at https://x.x.x.x/ui/scripts/main.js:263:20611
at l (https://x.x.x.x/ui/scripts/main.js:265:12567)
at k.$apply (https://x.x.x.x/ui/scripts/main.js:265:16690)
at HTMLInputElement.<anonymous> (https://x.x.x.x/ui/scripts/main.js:267:828)
at HTMLInputElement.dispatch (https://x.x.x.x/ui/scripts/main.js:262:14464)
at HTMLInputElement.r.handle (https://x.x.x.x/ui/scripts/main.js:262:11251)
at prop (https://x.x.x.x/ui/scripts/main.js:263:3018)
at n.access (https://x.x.x.x/ui/scripts/main.js:262:6702)
at n.fn.init.prop (https://x.x.x.x/ui/scripts/main.js:263:2642)
at V.$set (https://x.x.x.x/ui/scripts/main.js:264:21408)
Version of ESXi:
6.5.0 (Build 4564106)
The intersting thing:
This error does not occur when using Chrome 55, Firefox 50.1.0 and Internet Explorer 11. This error only occurs when using chromium (official build from: Download Chromium)
SAME ISSUE HERE !!! ESXi 6.5 !
Cause: TypeError: Cannot read property 'productsection' of undefined
Version: 1.8.0
Build: 4516221
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
Exception stack:
TypeError: Cannot read property 'productsection' of undefined
at updateSummaryPortlet (https://192.168.0.200/ui/scripts/main.js:312:31731)
at https://192.168.0.200/ui/scripts/main.js:313:4513
at https://192.168.0.200/ui/scripts/main.js:265:9465
at k.$eval (https://192.168.0.200/ui/scripts/main.js:265:16492)
at k.$digest (https://192.168.0.200/ui/scripts/main.js:265:15047)
at https://192.168.0.200/ui/scripts/main.js:265:16577
at e (https://192.168.0.200/ui/scripts/main.js:264:5646)
at https://192.168.0.200/ui/scripts/main.js:264:7652
This is anoying because this is the only way I know to manage ESXi in this version. In previous version vCenter Client was working great, but looks like it is no longer available for esx6.5
Have you tested the updated esx-ui?
Check here:
My bug is still there, even after updating to the newest component. I also opened a new bug report at:
Two days ago I patched my ESX and it is now with a build: 6.5.0 (Build 4887370)
Still the same issue.
I am also having the same issue with Chrome 57, ESXi 6.5a:
Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
Version: 1.8.0
Build: 4516221
ESXi: 6.5.0
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36
Exception stack:
Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
at https://192.168.1.110/ui/scripts/main.js:263:20611
at l (https://192.168.1.110/ui/scripts/main.js:265:12567)
at k.$apply (https://192.168.1.110/ui/scripts/main.js:265:16690)
at HTMLInputElement.<anonymous> (https://192.168.1.110/ui/scripts/main.js:267:828)
at HTMLInputElement.dispatch (https://192.168.1.110/ui/scripts/main.js:262:14464)
at HTMLInputElement.r.handle (https://192.168.1.110/ui/scripts/main.js:262:11251)
at prop (https://192.168.1.110/ui/scripts/main.js:263:3018)
at n.access (https://192.168.1.110/ui/scripts/main.js:262:6702)
at n.fn.init.prop (https://192.168.1.110/ui/scripts/main.js:263:2642)
at V.$set (https://192.168.1.110/ui/scripts/main.js:264:21408)
I was also having this exact issue with the same version of ESXi and Chrome. What I found to be the issue was due to me pressing the ENTER key on my keyboard during the login process. If I instead clicked the Log In button after entering the username and password, it would load the page just fine.
Give that a shot and see if that helps you (or anyone else)
Hello,
I too have seen this exact problem with ESXi 6.5, with the latest patch (released March 14th 2017) installed. However, I only have it when I hit "enter" after typing in the password. I do not get the error when I click "Log In".
I can completely re-create this error on 2 different ESXi 6.5 systems.
Hit enter after password: "unhandled exception" error.
Click Login: Everything works perfectly.
This issue does exist on Chrome (latest version as of March 20th), but does not exist on Microsoft Edge, the other browser I have installed. So at this moment I am deducting it to be one of two problems: 1) There is a problem with Chrome and ESXi web client that needs to be fixed in Chrome, or 2) There is a problem in the ESXi web client that needs to be fixed.
Since this problem does not exist on any other HTML5 websites in Chrome, I am inclined to think there is a coding error in the ESXi web client that has not yet been found.
I am not impacted as clicking "Log In" works.... but oh man, I do wish VMWare did not abandon the "thick client" idea.....
I agree that sometimes the HTML5 interface is a little difficult getting used to after using the VMware Client, but for those of us who don't use Windows regularly, it's nice not having to open a Windows VM or use a Windows machine just to administer ESXi. Plus, I think in abandoning the VMWare client, they have one less codebase they have to support, and can allocate more resources to making the HTML5 interface more consistent and less buggy. Also, I'm noticing now that I'm finally finding out where the features are on the HTML5 interface as opposed to the VMWare Client, it appears to be laid out a lot more consistently, while simultaneously managing to hide some of the more obscure features while still including them (e.g. the "down arrows" to show more settings after each one of the settings in the VM edit panel). Also, I was having trouble figuring out the network topology in VMware client, but the HTML5 interface makes it much more intuitive. It seems like a big win all the way around.
Just think -- they could have used Java for cross-platform access *shudder* ... things could always be worse!
I have the same issue and clicking the log in button instead of pressing enter has helped in my case, thank you!
Same problem here also.
I just ran into this this morning Mar 23, 2017. Really annoying. Using the login button instead of the enter key worked for me.
I am on 6.5.0 (Build 4564106)
Will this get fixed?
Great workaround !!!
Same here.
Chrome 57 / ESXi 6.5
Same issue here. Pressing Enter after entering Username and Password gives the error. Click Login, works perfectly.
Cause: Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
Version: 1.15.0
Build: 5069532
ESXi: 6.5.0
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36