4 Replies Latest reply on Jul 24, 2018 8:15 AM by Albinho77

    Unhandled Exception when clicking on network adapter

    Albinho77 Lurker

      Hi,

       

      I'm getting an unhandled exception error everytime I click on some network adapters.

       

      Host is ESXi 6.7 with latest Embedded Host Client from here -> ESXi Embedded Host Client

       

      I tried emptying the cache, incognito mode and also Firefox, same thing happens.

      On firefox the error trace is different but the result is the same.

       

      The "click path" from the WEB UI would be:

       

      Networking -> Physical NICs -> vmnic4 to 7 (on vmnics 0 to 3 this does not happen)

       

      vmnics 4 to 7 are 2 separate PCIe Intel x710 dual 10g cards, while 0 to 3 are onboard 4x1G Broadcom interfaces.

       

      The complete error I get on Chrome is the following:

       

      Unhandled exception (2)

      Cause: TypeError: Cannot read property 'length' of undefined

      Version: 1.29.0

      Build: 8122819

      ESXi: 6.7.0

      Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36

       

       

      Exception stack:

       

       

      TypeError: Cannot read property 'length' of undefined

          at updatePNIC (https://x.x.x.x/ui/scripts/main.js:353:31158)

          at https://x.x.x.x/ui/scripts/main.js:354:5621

          at https://x.x.x.x/ui/scripts/main.js:320:10283

          at n.$eval (https://x.x.x.x/ui/scripts/main.js:320:17497)

          at n.$digest (https://x.x.x.x/ui/scripts/main.js:320:16068)

          at https://x.x.x.x/ui/scripts/main.js:320:17584

          at e (https://x.x.x.x/ui/scripts/main.js:319:5691)

          at https://x.x.x.x/ui/scripts/main.js:319:7797

       

      And here's the error on Firefox:

       

      Unhandled exception (1)

       

       

      Cause: TypeError: pnic.validLinkSpecification is undefined

      Version: 1.29.0

      Build: 8122819

      ESXi: 6.7.0

      Browser: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0

       

       

      Exception stack:

       

       

      updatePNIC@https://x.x.x.x/ui/scripts/main.js:353:31124

      @https://x.x.x.x/ui/scripts/main.js:354:5835

      $digest@https://x.x.x.x/ui/scripts/main.js:320:16343

      $apply@https://x.x.x.x/ui/scripts/main.js:320:17773

      safeApply@https://x.x.x.x/ui/scripts/main.js:462:13760

      updateScopeProperty@https://x.x.x.x/ui/scripts/main.js:462:13900

      onChange@https://x.x.x.x/ui/scripts/main.js:461:23916

      trigger@https://x.x.x.x/ui/scripts/main.js:322:30504

      change@https://x.x.x.x/ui/scripts/main.js:338:1850

      trigger@https://x.x.x.x/ui/scripts/main.js:322:30504

      _notify@https://x.x.x.x/ui/scripts/main.js:334:402

      value@https://x.x.x.x/ui/scripts/main.js:334:11

      _tap@https://x.x.x.x/ui/scripts/main.js:333:30441

      f@https://x.x.x.x/ui/scripts/main.js:316:12963

      trigger@https://x.x.x.x/ui/scripts/main.js:322:30504

      notify@https://x.x.x.x/ui/scripts/main.js:325:5811

      _trigger@https://x.x.x.x/ui/scripts/main.js:325:3988

      end@https://x.x.x.x/ui/scripts/main.js:325:3472

      _eachTouch@https://x.x.x.x/ui/scripts/main.js:325:6993

      _end@https://x.x.x.x/ui/scripts/main.js:325:6816

      @https://x.x.x.x/ui/scripts/main.js:323:31429

      dispatch@https://x.x.x.x/ui/scripts/main.js:317:14412

      add/r.handle@https://x.x.x.x/ui/scripts/main.js:317:11234

       

      Any clues?

      Thanks!

      Luis

        • 1. Re: Unhandled Exception when clicking on network adapter
          golddiggie Virtuoso

          What's the host hardware/server?? Was the 10G card installed in the host during ESXi install? Which ISO did you use to install ESXi?

           

          In case you didn't know, if you have an HP host server, you MUST use the HP customized ESXi install ISO file. In my experience, you don't need to use the customized for Dell hosts, just use the GA ISO.

           

          If you added the 10Gb card after ESXi was installed, you might need to install the actual drivers for the card. While it might appear to be 100%, it might only be 75% (or less). Basically, showing up in the list, but not working properly.

           

          BTW, if this is a standalone host server (with no vCenter Server present, or won't be present) then you can use the web client (HTML5 based) to manage it. No real need to try using something else. In fact, I would attempt to use the built-in web client BEFORE you go doing anything else. If the fling you are using is installed on the host, remove it and see what happens. If it won't remove clean, then do a reinstall of ESXi 6.7 on the host and try using the built-in web client.

          • 2. Re: Unhandled Exception when clicking on network adapter
            daphnissov Guru
            Community WarriorsvExpert

            Your best bet (if you haven't done so already) is to post this in the Flings comment section and see if any of the devs there can offer any support. It sounds like, if you've truly tried those things, to be a bug, but they'd be the ones to tell you.

            • 3. Re: Unhandled Exception when clicking on network adapter
              Albinho77 Lurker

              Hi, thanks for the reply!

               

              Hardware is a Dell Poweredge R430, the x710 nics were installed before ESXi install, I used the regular ISO from vmware site (6.7.0-8169922.x86_64 iso)

               

              Standalone Server, no vCenter present, the error I am getting is from the Web Client, I didn't try to use it from vSphere client cause AFAIK it doesn't work on versions >6.5

               

              For clarification, despite the error I described the NIC is actually working.

              • 4. Re: Unhandled Exception when clicking on network adapter
                Albinho77 Lurker

                Your best bet (if you haven't done so already) is to post this in the Flings comment section and see if any of the devs there can offer any support. It sounds like, if you've truly tried those things, to be a bug, but they'd be the ones to tell you.

                Thanks!

                 

                I'll try posting there as well, it does look like a bug, its not impeding the nic to actually work cause I can add it to vswitches and it works, but the error its quite annoying.