Hi All,
I have installed VC 5.5.0b in Linked mode on a Windows Server 2008. The Installation went fine and all looks good but when I check the vCenter Service Status it shows that two services have an alert
The Services are
I checked the log file vws.log and found below error message
ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.vim.sms from http://localhost/sms/health.xml
ERROR com.vmware.vim.health.impl.ComponentSpec] Unable to retrieve health for com.vmware.vim.sms from any of its health URLs
ERROR com.vmware.vim.health.impl.XmlUtil] Error retrieving health from url: http://localhost/sps/health.xml
java.io.FileNotFoundException: http://localhost/sps/health.xml
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
I have tried below steps
My Virtual Database is using a custom port instead of 1433.
Please suggest what I can try next
Thanks in advance
This service is supposed to be there, anyway you can try repair the installation. This KB article talks about re-install the VMware vSphere Profile Driven Storage service: Upgrading to vCenter Server 5.0 Update 1, 5.1, or 5.5 fails and the installation wizard is interrupt...
Check if the service VMware vSphere Profile-Driven Storage Service are using the same credentials of VMware VirtualCenter Server service and the VMware VirtualCenter Management Webservices, the default is Local System.
Hi Richard,
VMware vSphere Profile-Driven Storage Service is missing from services.msc console
VMware VirtualCenter Management Web services is running under a service account same as VC Service.
Thanks
Could you please upload the logs vim-sps-msi.log and vpxd.log ? You can find vim-sps-msi.log at temp(%temp%) directory and The vpxd.log (located at C:\ProgramData\VMware\VMware VirtualCenter\Logs)
This service is supposed to be there, anyway you can try repair the installation. This KB article talks about re-install the VMware vSphere Profile Driven Storage service: Upgrading to vCenter Server 5.0 Update 1, 5.1, or 5.5 fails and the installation wizard is interrupt...
Thanks a ton Richard !!!
FYI, I ran into the vmware vsphere profile driven storage missing during a vcenter upgrade from 5.5 U2 to 5.5 U3
I did not have access to the U2 ISO to repair, so vmware support had me UNINSTALL vcenter and do a clean U3 install
We had some trouble recreating the SQL DSN (uninstall deletes it!)
But everything was there in the DB once we had a working DSN
First time out of 20+ vcenter upgrades I had seen this!