1 Reply Latest reply on Apr 20, 2017 8:08 AM by Cryptasianer509

    vSphere Client 5.5.0 crashes  on Windows 8.1 after Windows Updates April/2017

    Cryptasianer509 Lurker

      Hi everybody,

       

      after shuting down my Windows 8.1 Workstation on 13.04.2017 with installing updates, when I startet the PC the next time on 18.04.2017 I wasn't able to login to our vSphere console.

      I have VMware-viclient-all-5.5.0-4032365.exe installed.

      Sorry for the screenshots beeing german, but this is the update history of the relevant days.

      vSphere1.jpg

      The vSphere Client comes up, asks me for the login and after some time (where it establishes the connection, searches for plugins, loads the main form, ...) the windows simply closes. Sometimes with the following messages:

      vSphere2.jpg

      vSphere3.jpg

      vSphere4.jpg

      vSphere5.jpg

      At the moment I am the only one with this problem in my company. On a Windows 10 Notebook I have no Problems connecting to the ESX.

      I attached you the relevant log file. Anyone else with such a Problem?

       

      Greetz Christian

        • 1. Re: vSphere Client 5.5.0 crashes  on Windows 8.1 after Windows Updates April/2017
          Cryptasianer509 Lurker

          Hi again,

           

          In the logs I may found the error which causes the Client to crash. (with no solution yet)

           

          [viclient:SrvMsg  :W:19] 2017-04-20 16:24:08.897  RMI Request Vmomi.Core.PropertyCollector.WaitForUpdates - 35
          <version>4</version>
          [        :QuickInf:P:17] 2017-04-20 16:24:08.913  Loading catalog '/catalog/de/fault.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\vim\fault_263e8cf67fe795111db9c5874a31e0f7.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:08.960  Loading catalog '/catalog/de/vm.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\vim\vm_ed81fd68a22d6f6566779466be55feea.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:08.991  Loading catalog '/catalog/de/event.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\vim\event_a8b18de7255f84634846307bae384bce.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:09.100  Loading catalog '/catalog/extensions/com.vmware.vim.sps/locale/de/extension.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\com.vmware.vim.sps\extension_ddcea64aa76bffa014df02d5d99ed735.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:09.147  Loading catalog '/catalog/de/option.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\vim\option_efa636aa6aa8cfc4e3cedbf9d94d587c.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:09.178  Loading catalog '/catalog/extensions/VirtualCenter/locale/de/task.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\VirtualCenter\task_77e354a9e552f1ccbe0585cdb5ea1a53.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:09.194  Loading catalog '/catalog/extensions/com.vmware.vim.eam/locale/de/task.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\com.vmware.vim.eam\task_f907a4c18c1b40e7d0ae61df46703d63.vmsg
          [        :QuickInf:P:17] 2017-04-20 16:24:09.209  Loading catalog '/catalog/de/locmsg.vmsg' from C:\Users\cstoiber\AppData\Local\VMware\vpx\catalog\VirtualCenter\5.5.0\de\vim\locmsg_886ca73c915650c1d87bc8f3d0547c9a.vmsg
          [        :Error   :M: 6] 2017-04-20 16:24:27.076  System.Runtime.InteropServices.SEHException: Eine externe Komponente hat eine Ausnahme ausgelöst.
             bei VMware.CustomControls.ListViewEx..ctor()
             bei VpxClientCommon.ListViewData..ctor()
             bei SmService.Controls.ReportsList..ctor(EntityType entityType, IDataProvider dataProvider, Banner banner)
             bei SmService.Controls.ReportsView..ctor(EntityType entityType, IDataProvider dataProvider, Banner banner)
             bei SmService.Controls.MainPanel..ctor(VIApp app, IDataProvider dataProvider, Banner banner, String managedObjType)
             bei SmService.Controls.StoragePanel.InitializeComponent()
             bei SmService.Controls.StoragePanel..ctor(VIApp app, IDataProvider dataProvider, String managedObjType)
             bei SmService.Main.AddExtension(String managedObjectType)
             bei SmService.Main.Load(VIApp viApp)
             bei VpxClient.Plugins.PluginManager.LoadPlugin(PVE pve, PluginInformation info, List`1 pluginServices)
          [        :QuickInf:M: 6] 2017-04-20 16:24:27.263  Plugins2.DiscoverPlugins processed directory (C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Plugins\SMS55) 00:00:18.9863296
          [        :QuickInf:M: 6] 2017-04-20 16:24:27.263  Stop : PluginManager.DiscoverPlugins00:00:19.9941909
          [        :Error   :W: 2] 2017-04-20 16:24:43.895  A fatal unhandled error occurred in vSphere Client
          [        :QuickInf:M: 6] 2017-04-20 16:24:44.036  ChromeView created.
          [        :Error   :W: 2] 2017-04-20 16:24:44.083  System.Runtime.InteropServices.SEHException: Eine externe Komponente hat eine Ausnahme ausgelöst.
             bei VMware.CustomControls.ListViewEx.Dispose(Boolean disposing)
             bei VpxClientCommon.ListViewData.Dispose(Boolean disposing)
             bei System.ComponentModel.Component.Finalize()
          [        :Error   :W: 2] 2017-04-20 16:24:44.301  A fatal unhandled error occurred in vi client
          [        :Error   :W: 2] 2017-04-20 16:24:44.317  System.Runtime.InteropServices.SEHException: Eine externe Komponente hat eine Ausnahme ausgelöst.
             bei VMware.CustomControls.ListViewEx.Dispose(Boolean disposing)
             bei VpxClientCommon.ListViewData.Dispose(Boolean disposing)
             bei System.ComponentModel.Component.Finalize()
          [        :ShowExcp:M: 6] 2017-04-20 16:24:59.841  Fehler: Im vSphere-Client trat ein interner Fehler auf.
          Details: Eine externe Komponente hat eine Ausnahme ausgelöst.
          

           

          Looks like there is a problem with the Storage Manager plugin. But I am not aware of any changes there, thats why I suppose it is related to the Windows updates.

           

          Greetz Christian