Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Logging into the vSphere Web Client hangs after VC 6.7 upgrade (54751)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 45300Language:
Chinese (Simplified)JapaneseEnglish

9 like this article

Subscribe to get an email
newsletter with new updates

9 people found this helpful Please provide article feedback:

Symptoms

After upgrading to vCenter Server 6.7, logging into the vSphere Web Client hangs.

In the vsphere_client_virgo.log file, you see entries similar to:

[2018-04-23T15:06:03.415+10:00] [ERROR] http-nio-9090-exec-1 70000020 ###### ###### Endpoint.AMF null java.lang.NullPointerException: null
[2018-04-24T19:59:10.152+03:00] [ERROR] start-signalling-3 org.springframework.flex.core.MessageBrokerFactoryBean Error thrown during MessageBroker initialization org.springframework.aop.framework.AopConfigException: Unexpected AOP exception; nested exception is java.lang.RuntimeException: java.lang.ClassNotFoundException: org.springframework.cglib.proxy.NoOp not found from bundle [com.<Offending Plugin>]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

The vsphere_client_virgo.log file is located at:

vCenter Server on Windows - C:\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\

vCenter Server Appliance - /var/log/vmware/vsphere-client/logs

Purpose

This article provides information on restoring vSphere Web Client (Flash) 6.7 operations after login with installed plug-ins.

Cause

This issue occurs when the new version of the application server responsible for rendering the plug-ins in the vSphere Web Client (Flash) 6.7 is missing the libraries needed by the plug-ins. This disrupts the communication path between the browser and the application server of the vSphere Web Client.

Impact / Risks

Upon logging in with the vSphere Web Client (Flash) where certain incompatible plug-ins had been installed, a user finds that the client hangs. The vSphere client (HTML5) and its plug-ins are not affected by this issue.

Resolution

This issue is resolved in vCenter Server 6.7.0a,  available at VMware Downloads

Workaround

To work around this issue, run the following script on the vCenter Server 6.7.
Scripts (whitelist-plugins.sh & whitelist-plugins.bat) can be downloaded from the KB Attachements.

The script contains commands to:

Whitelist the following verified plug-ins:

VMware Update Manager

VMware Virtual SAN

VMware Site Recovery Manager 8.0

VMware vSphere Replication 8.0

Dell EMC's OpenManage 4.2 Integration for VMware vCenter

Nimble Storage 5.0

Applying the Whitelist script:

The steps on applying the Whitelist script are listed below:

In Windows-based vCenter Server

Download whitelist-plugins.bat from this KB attachments and copy the file to a directory on the vCenter Server.

Open the command prompt (as Administrator) to run the script.

To apply the whitelist script for your vCenter Server, run this command:

<path_to_script>\whitelist-plugins.bat apply

In vCenter Server Appliance

Log into the bash shell as root. For more information, see the Enable and Access the Bash Shell from the Appliance Shell section of the vCenter Server Appliance Configuration Guide.

To upload the files to VCSA run the below command to change the default shell to bash which enables you to copy the files using WinSCP. For more information refer KB article.

chsh -s /bin/bash root

Using WinSCP, Download whitelist-plugins.sh from the KB attachments and copy the attached whitelist-plugins.sh to the /tmp/ directory.

Run this command:

chmod +x /tmp/whitelist-plugins.sh

To apply the whitelist script for your vCenter Server appliance, run this command:

sh /tmp/whitelist-plugins.sh apply

Notes:

Be sure to refresh the browser after applying the script.

After applying the script, you should be able to log in to the vSphere Web Client (Flash). To see the results of the whitelist action after logging in, navigate to the Administration section and click Client Plug-Ins. Installed plug-ins included in the whitelist will display as “Enabled”, while plug-ins not included in the whitelist script will be displayed as “Incompatible.”

Revert the plug-in whitelist configuration:

This option allows you to restore pre-whitelist configuration after upgrading plug-ins to a vSphere 6.7-compatible version.

In Windows-based vCenter Server

Download whitelist-plugins.bat file from the KB attachments and copy the to a directory on the vCenter Server. (If not already done so).

Open the command prompt (as Administrator) to run the script.

To revert the changes, run this command:

<path_to_script>\whitelist-plugins.bat revert

In vCenter Server Appliance

Log into the bash shell as root. For more information, see the Enable and Access the Bash Shell from the Appliance Shell section of the vCenter Server Appliance Configuration Guide.

Using WinSCP, Download whitelist-plugins.sh from the KB attachments and copy the attached whitelist-plugins.sh to the /tmp/ directory. (if not already done so).

Run this command:

chmod +x /tmp/whitelist-plugins.sh

To revert the changes, run this command:

sh /tmp/whitelist-plugins.sh revert

Note: Be sure to refresh the browser after applying the script.

Related Information

VMware is enabling special engagements for partners to update their plug-ins and certify to ensure compatibility with vSphere 6.7. For more information on the list of partner certified plugins, see the VMware Compatibility Guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

whitelist-plugins.sh

whitelist-plugins.bat

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
针对 CVE-2018-3639 的管理程序协助的客户机缓解措施（推测存储绕过） (55111)

KB
•
当 ESXi 主机从待机状态唤醒时，触发“主机连接和电源状态”警报 (2030249)

KB
•
vCenter Server からボリューム サイズを増やすと、ESXi ホストが正しいデータストア容量を報告しない (52985)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant