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

vSAN health check in vSphere Web Client fails with "back end property provider" error (65162)

Last Updated: 6/22/2023Categories: TroubleshootingTotal Views: 7354Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

Checking vSAN health using using the vSphere Web Client fails with the error:

The query execution timed out because of a back-end property provider
'com.vmware.vsphere.client.storage.impl.StoragePropertyProvider' which took more than 120 seconds.

In the /var/log/vmware/vsphere-client/logs/vsphere_client_virgo.log file, you see entries similar to:

[ERROR] usage-data-collector-thread com.vmware.ph.upload.service.UploadServiceImpl Failed 3 of 3 attempts to get
manifest from VMware server. The reason for the last failure was (enable 'debug' level logging to see the stack trace for every failed
attempt): org.apache.http.conn.ConnectTimeoutException: Connect to vcsa.vmware.com:443 [vcsa.vmware.com/<IP Address>]
failed: connect timed out. com.vmware.ph.upload.exception.ConnectionException: org.apache.http.conn.ConnectTimeoutException:
Connect to vcsa.vmware.com:443 [vcsa.vmware.com/<IP Address>] failed: connect timed out

In the /var/log/vmware/vsan-health/vmware-vsan-health-service.log, you see entries similar to:

INFO vsan-health[PhoneHomeCollector] [VsanPhoneHomeUtil::isVcPhoneHomeEnabled] VC CEIP Enabled Status : True
...
WARNING vsan-health[EventMonitor] [VsanCloudHealthUtil::checkNetworkConnection] Internet is not connected.

Purpose

This article provides steps to resolve the error back-end property provider when checking vSAN health through the vSphere Web Client.

Cause

The issue occurs if there is no Internet connection while Customer Experience Improvement Program (CEIP) is enabled.

Resolution

To resolve the issue:

Disable CEIP or connect to internet.

Log in to the vCenter Server instance as a member of [email-masked] group by using the vSphere Web Client.

On the vSphere Web Client Home page, under Administration, click Customer Experience Improvement Program.

Click Join to enable the CEIP or Leave to disable the Program.

Or configure Internet connectivity through vSphere Web Client:

vSAN-Cluster > Configure > vSAN > General

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
vSAN のメモリまたは SSD の輻輳がしきい値制限に達した (2071384)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant