Unhandled exception(1) shows up when using chrome browser to login to vSphere Web Client 6.5

Hi Anderson,

Can you confirm which version of the Host Client you are using?

You can press Escape to close the error dialog.

I suspect you might be hitting a known bug with Chrome. If you are not using version 1.17.0, then you could upgrade to the latest Fling release to resolve that known bug.

You should update to version 1.17.0. It fixes the issue.

I'm getting this same issue only after updating to 1.17.0. It was working fine before on 1.16.0. I'm on a Mac running OS X 10.11.6 and Chrome browser Version 56.0.2924.87 (64-bit). The error I get is "Unhandled Exception (1)" in a popup window and then forced to re-login. This happens any time I try to go any lower than just the top pages for navigation including edit settings, etc.

Hi Anthony,

Can you please post the backtrace when you click on the Details button?

I got same error. Here's the backtrace:

Unhandled execption (1)

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.110 Safari/537.36

Exception stack:

Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
at https://192.168.0.224/ui/scripts/main.js:263:20611
at l (https://192.168.0.224/ui/scripts/main.js:265:12567)
at k.$apply (https://192.168.0.224/ui/scripts/main.js:265:16690)
at HTMLInputElement.<anonymous> (https://192.168.0.224/ui/scripts/main.js:267:828)
at HTMLInputElement.dispatch (https://192.168.0.224/ui/scripts/main.js:262:14464)
at HTMLInputElement.r.handle (https://192.168.0.224/ui/scripts/main.js:262:11251)
at prop (https://192.168.0.224/ui/scripts/main.js:263:3018)
at n.access (https://192.168.0.224/ui/scripts/main.js:262:6702)
at n.fn.init.prop (https://192.168.0.224/ui/scripts/main.js:263:2642)
at V.$set (https://192.168.0.224/ui/scripts/main.js:264:21408)

I am receiving the same error. The backtrace is also identical to the one posted above.

Hi Marnin,

Yes, unfortunately a Google Chrome update has exposed this error in existing versions of Host Client.

You can update to version 1.16.0 from this website which will resolve the issue.

We are working on getting an official release ready to ship.

I got this error after replacing the self-signed certificate on ESXi 6.5. Prior to that, it was working fine using the same Chrome build.

No such issue using Firefox. Edge doesn't even load the landing page!

---

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 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Exception stack:

Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
at https://192.168.207.130/ui/scripts/main.js:263:20611
at l (https://192.168.207.130/ui/scripts/main.js:265:12567)
at k.$apply (https://192.168.207.130/ui/scripts/main.js:265:16690)
at HTMLInputElement.<anonymous> (https://192.168.207.130/ui/scripts/main.js:267:828)
at HTMLInputElement.dispatch (https://192.168.207.130/ui/scripts/main.js:262:14464)
at HTMLInputElement.r.handle (https://192.168.207.130/ui/scripts/main.js:262:11251)
at prop (https://192.168.207.130/ui/scripts/main.js:263:3018)
at n.access (https://192.168.207.130/ui/scripts/main.js:262:6702)
at n.fn.init.prop (https://192.168.207.130/ui/scripts/main.js:263:2642)
at V.$set (https://192.168.207.130/ui/scripts/main.js:264:21408)

Hi Jason,

Unfortunately this error is caused by Chrome 57. Chances are you restarted Chrome and it got updated.

The latest release of Host Client here on the Flings site addresses this issue. We will be making an official release very shortly via the normal ESXi patch process.

So you are saying i have to shutdown all my virtual machines and upgrade ESXI to fix this issue? Not a good answer finding downtime is like finding a needle in a haystack.

Hi Brendan, no you can update the Host Client without a reboot.

esxcli software vib update -v /absolute/path/to/vib

I found if you click on the log on button and not use the enter key on the keyboard you can log in normally and all works normally...

Andy A. was correct this worked for us.

Andy's work around does work, but would like to see a proper fix.

I experienced the same error.

When it shows up, press Ctrl+R to reload, and the page will reload without the error box showing up, hope it helps for now.

Also would be nice to have an official update to fix this issue. Only happening in 6.5U1, my 6.0U3 has no problem.

Hi Carl,

This issue was fixed some time ago - you can upgrade to the Fling version of the Host Client from this site or you can download the 6.5 Update 1 release of ESXi.

yah, no, it's not fixed. using a freshly loaded 6.5U1 ESXi, and chrome 61.0.3163.100 (Official Build) (64-bit), and it's happening.

the CTRL+R trick works nicely though.

Same thing here. Running ESXI 6.5.0 (Build 5146846) and Chrome 61

I think ESXi 6.5 U1 does not come with the newest host client. I had to update to the latest 1.23 client from here, and then Chrome 61 worked.

I open it through IE builtin one and didn't press enter key just after credentials click by mouse on the log in button it will solve the problem

Hi Sayed, can you let me know which version of Host Client you're using?

Getting the unhandled exception error when attempting to deploy an OVA.
ESXi 6.5 U1 (Cisco OEM custom) and Host Client 1.29. Happens when using Chrome or Firefox on Mac and when using Chrome or IE on Windows Server 2012. Same problem on both a fresh 6.5 build and an upgrade from 6.0.
------------------
Cause: Error: [$parse:syntax] http://errors.angularjs.org/1.3.20/$parse/syntax?p0=.1.&p1=is%20an%20unexpected%20token&p2=67&p3=wizardOptions.data.propDropdowns.com.cisco.nm.cpcm.applicationMode.1.selectedValue&p4=.1.selectedValue
Version: 1.29.0
Build: 8122819
ESXi: 6.5.0
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:59.0) Gecko/20100101 Firefox/59.0

Exception stack:

S/<@https://10.214.5.32/ui/scripts/main.js:318:20612
throwError@https://10.214.5.32/ui/scripts/main.js:321:18900
parse@https://10.214.5.32/ui/scripts/main.js:321:18184
Oe/this.$get</<@https://10.214.5.32/ui/scripts/main.js:320:9440
$watch@https://10.214.5.32/ui/scripts/main.js:320:14476
getPropertyFields/</<@https://10.214.5.32/ui/scripts/main.js:368:27658
r@https://10.214.5.32/ui/scripts/main.js:318:21018
getPropertyFields/<@https://10.214.5.32/ui/scripts/main.js:368:25525
r@https://10.214.5.32/ui/scripts/main.js:318:21124
getPropertyFields@https://10.214.5.32/ui/scripts/main.js:368:25282
@https://10.214.5.32/ui/scripts/main.js:368:28856
e@https://10.214.5.32/ui/scripts/main.js:319:3872
Fe/this.$get</</<@https://10.214.5.32/ui/scripts/main.js:319:23883
I/<@https://10.214.5.32/ui/scripts/main.js:319:15273
r@https://10.214.5.32/ui/scripts/main.js:318:21124
I@https://10.214.5.32/ui/scripts/main.js:319:15257
g@https://10.214.5.32/ui/scripts/main.js:319:11540
G/<@https://10.214.5.32/ui/scripts/main.js:319:11155
Q/<@https://10.214.5.32/ui/scripts/main.js:319:12029
h@https://10.214.5.32/ui/scripts/main.js:319:14061
link/<@https://10.214.5.32/ui/scripts/main.js:321:31965
$digest@https://10.214.5.32/ui/scripts/main.js:320:16343
$apply@https://10.214.5.32/ui/scripts/main.js:320:17773
l@https://10.214.5.32/ui/scripts/main.js:319:26637
F@https://10.214.5.32/ui/scripts/main.js:319:28783
wf/</C.onload@https://10.214.5.32/ui/scripts/main.js:319:29325

Ctrl-R worked for me
Windows 7 Ultimate
ESXI 6.5.0
Build 4887370
Chrome 71.0.3578.98 (Official Build) (64-bit)