VMware Cloud Community
andrewpeplinski
Contributor
Contributor

ESXi Host Client Unhandled Exception

Having an odd issue when connecting to the Host Client on ESXi 6.7 U3.  When I log in I get an Unhandled Exception error (listed below).  I only get it on UCS blade hosts in our production cluster, but don't get it on the same build on a stand-alone Cisco host.  I only get the error on initial login, when it tries to display the host summary page - if I hit ESC I can browse to other areas, just can't see the summary pane at all.

 

Cause: Possibly unhandled rejection: {}
Version: 1.43.10
Build: 20199807
ESXi: 6.7.0
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

Exception stack:

TypeError: Cannot mix BigInt and other types, use explicit conversions
    at https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:392:8392
    at Array.forEach (<anonymous>)
    at https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:392:8300
    at https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:320:26610
    at m.$digest (https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:321:307)
    at https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:321:2024
    at Yg.completeTask (https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:321:8113)
    at https://cmk-prdesxi04.noram-dc.local/ui/scripts/main.js:319:13245

 

0 Kudos
2 Replies
andrewpeplinski
Contributor
Contributor

Further, when we try to edit a VM's settings in the host client we get the same error message.  Not sure if it's correlative, but definitely consistent.

0 Kudos
MagigMage
Contributor
Contributor

I had a customer with this issue, and It was a vvol that was 8,000 (or appeared to be) TB.

If we clicked on datastores it was the only datastore that threw this error.

I believe it can also happen when you have too many decimal points on a hard disk size, but internally searching our queue came up with one other customer that had this issue with vvols/datastores and being over 60TB.

 

Hit escape on the error instead of reload, open the datastores, sort by size and see which one throws the error may help.

0 Kudos