VMware vCenter Server 5.x Storage Monitoring and Profile Driven Storage Service fails with error: "Unable to retrieve health data from..."
book
Article ID: 328628
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
-
After upgrading to VMware vCenter Server 5.x, the VMware vCenter Storage Monitoring Service fails.
-
You see these errors:
-
Restarting the vCenter Storage Monitoring Service (SMS) does not resolve this issue.
-
The SMS plugin tries to connect to port 80, but fails.
-
The vCenter Server was installed with custom ports.
Cause
This issue occurs if you are using a custom port, such as Port 81, for vCenter Server.
To identify the custom port used by vCenter Server:
- Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter.
- Verify port HttpProxyPort used for vCenter Server.
Resolution
To resolve this issue, you must modify the SMS and the Profile Driven Storage service.
Modifying the SMS:
-
Open the extension.xml file located at C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\ com.vmware.vim.sms using a text editor.
- Locate the entry with http://localhost/sms/health.xml.
-
Edit this entry to include the custom port that is used. For example, if the custom port used is 81, change the entry to:
http://localhost:81/sms/health.xml
-
Save and close the file.
Modifying the Profile Driven Storage service:
Note: Due to changes in vCenter Server 5.5 ports, these steps do not change Profile Driven Storage service port.
- Open the extension.xml file located at C:\Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\ com.vmware.vim.sps using a text editor.
- Locate the entry with http://localhost/sps/health.xml.
- Edit this entry to include the custom port that is used. For example, if the custom port used is 81, change the entry to:
http://localhost:81/sps/health.xml
- Save and close the file.
Restart the VMware vCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).
Feedback
thumb_up
Yes
thumb_down
No