google.com, pub-4920175566720914, DIRECT, f08c47fec0942fa0 Skip to main content

Shockwave Flash crashes on vSphere web application




Recently there were an issue where vSphere Web client stopped working with Google crome and Firefox. After login to vSphere webclient or any other web based VMware application getting error where its states “ Shockwave Flash has crashed”

After investigating it’s been found that the google recently published a newer version of Flash( 27.0.0.170) with its latest update of crome ( 61.0.3163.100). However, the newer version of Flash was not available for download or listed in Adobe site.

Same issue identified on the Firefox where the latest Flash were causing the same issue.


Workaround identified

1) One-way to disable the auto-update feature of Chrome, you can do so by changing the following HKLM\SOFTWARE\Policies\Google\Update\AutoUpdateCheckPeriodMinutes to 0


2) It looks like you can also simply replace the new pepperflash DLL with an older version and placing it within the 27.0.0.170 folder (in case Chrome tries to update it). If you are looking for a working Windows DLL, it looks like one has been posted on one of the Chrome Issues thread here. Please be aware that the latest version of Flash (27.0.0.170)  does resolve a major 0-day security vulnerability which is outlined here and reverting its affects can put you and your organizations at risk.


Resolution



VMware has come up with the resolution to fix the issue by installing the latest version of flashplayer (27.0.0.183 or later) from https://get.adobe.com/flashplayer/.

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x
You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out.
Now the option left is from the command line of VCSA appliance.
Below steps will make it possible to change the FQDN of the VCSA from the command line.
Access the VCSA from console or from Putty session.Login with root permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot the VCSA appliance.After reboot you will be successfully manage to change the FQDN of the VCSA .

Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client.

If you are using self-signed certificate, you can regenerate the certificate with the help of below KB 2112283 article.



Happy Sharin…

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …