Skip to main content
O
oliviermsc
Participant
April 30, 2018
Question

29.0.0.140 - can't access vmWare vSphere 6.0 anymore

  • April 30, 2018
  • 1 reply
  • 13572 views

Since the update 29.0.0.140 installed on my macOS and on my Windows 10, I cannot access anymore the web interface of vmWare vSphere.  This is a major regression for tech people using these enterprise vmWare products. On macOS, upon login the browser generally end up unresponsive and declares the Flash plugin has failed to answer or did crash. On Windows 10, the login screen to vSphere does not even appear, but I get a top header saying "To view this page ensure that Adobe Flash Player version 11.5.0 or greater is installed." Which is kind of funny since 29.0.0.140 is installed.

Don't know if the culprit is Adobe Flash or vmWare vSphere, but these two should really talk to each other quickly...

Tested both with up-to-date Chrome and Firefox, both on macOS and Windows 10.

Does someone share this same experience and would have a quick work-around? Like access to some previous versions of the plugin?

This topic has been closed for replies.

1 reply

jeromiec83223024
jeromiec83223024
Inspiring
April 30, 2018

If it's actually crashing, a crash dump would be useful:

Report a Flash Player crash or error

For the situation where Flash isn't detected, you may need to enable it in your browser:

https://helpx.adobe.com/flash-player/kb/install-flash-player-windows.html

https://helpx.adobe.com/flash-player/kb/flash-player-issues-windows-10-ie.html

https://helpx.adobe.com/flash-player/kb/flash-player-issues-windows-10-edge.html

https://support.mozilla.org/en-US/kb/why-do-i-have-click-activate-plugins

https://helpx.adobe.com/flash-player/kb/enabling-flash-player-safari.html

https://support.google.com/chrome/answer/6258784

https://helpx.adobe.com/flash-player/kb/enabling-flash-player-opera.html

To give you any additional useful advice, specifics on the browser would be useful:

https://forums.adobe.com/thread/1195540

O
oliviermscAuthor
Participant
April 30, 2018

Thanks.  This is not simply an enabling matter (triple checked). On macOS, already did uninstall completely (using the uninstaller), tested re-installing the latest beta (dated April 21 but which appear to behave exactly in the same way as the release from April 10). Uninstalled again, re-installed the latest release. Same thing.

Upon login to vmWare vSphere, using Chrome (Version 65.0.3325.181 (Build officiel) (64 bits)) on macOS 10.13.4 (17E202), the flash component (chrome://components) is reported being version 29.0.0.140, first the clock appears as it always does for 1 second or two, but since this update it lasts about one minute after which Chrome warns the plug-in doesn't answer anymore and a popup confirms this, while offering to kill the plug-in or wait for it to react (to no avail).

On macOS, the crash I saw once on tens of attempts does not seem to be easy to reproduce, but the hang is 100% reproducible.

On Windows 10, or trying Firefox on macOS, the behaviour is slightly different with warning from the page that the flash version is probably not right. The Chrome version on Windows 10 is 66.0.3359.139 (Build officiel) (64 bits) (cohort: 66_139_win). Again with PepperFlash\29.0.0.140\pepflashplayer.dll.

jeromiec83223024
jeromiec83223024
Inspiring
May 4, 2018

I was able to chase down a VMWare vSphere 6.0 instance here, but we're unable to reproduce the hang that you're describing.  It did take a while to load, but it didn't hang.

Depending on how VMWare wrote their ActionScript, it's possible that the client gets in a pathological state when a particular response is slow or something.  I'm guessing it just continues to poll aggressively for a network response that the developers assumed was always going to come back quickly.

My recommendation would be to reach out to VMWare.  They're really in the best position to debug this.  If they need to escalate an issue to Adobe as a result, we have direct engineering channels with them.

I did observe that newer versions of vCenter 6 no longer rely on Flash Player for the client UI.  Given that the browsers are making it harder and harder to run Flash Player anyway, it might be a good impetus for making the upgrade (I know... easier said that done).

You might take a look at the network tab in the browser's developer tools, and/or with a web debugging proxy (Charles, etc.) to see if maybe you can identify requests that are taking a really long time to respond.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices