VMware vSphere Profile-Driven Storage Service missing

[Slingsh0t]

Hey guys,

One vSphere platform I have at the moment is complaining about the SPS service not functioning in the vCenter server health status page.  What I've found is that the "VMware vSphere Profile-Driven Storage Service" does not actually exist in the list of windows services on the vCenter server.  Has anyone else seen this before?

When I run the vSphere client and select VM Storage Profiles I get the following error:

vSphere Client cannot connect to Profile-driven storage server at https://<VC_HOSTNAME>:443/sps/sdk

The vCenter server has been rebooted, all standard vsphere services are running (except for storage profile of course).  If anyone has a fix or information about this please let me know.

[Slingsh0t]

Shameless bump... no-one has seen this before?

[Datto]

Although your situation may be different since you're not seeing the Profile Driven Storage Service, I've had problems happen to me twice where the Profile Driven Storage service wouldn't start although it was visible in the list of services. Both times it was due to problems with the VCenter Inventory Service (VCenter Inventory Service wouldn't start and thus Profile Drive Storage wouldn't start).

Here's the link I used to get the VCenter Inventory Service to become useable in my case:

http://pubs.vmware.com/vsphere-50/index.jsp?topic=/com.vmware.vsphere.install.doc_50/GUID-EBB03FB7-F...

Check to see if your VCenter Inventory Service is starting correctly (assuming you're using the Windows VCenter rather than the VCSA appliance).

Datto

Message was edited by: Datto

[Slingsh0t]

Thanks for the reply, the vCenter Inventory Service is running, has been restarted however the issue goes still unresolved.  I'll try resetting the Inventory DB as per that article a little later.

<removed as I misread the above post!>

[Sonsondei]

Make sure web client server is not running in the same server that runs vCenter server.  That may solve your issue.

[jeremyahagan]

Did you ever resolve this? I have the same issue on a clean install of vCenter 5.0 Update 2.

[jeremyahagan]

I managed to get the missing component to install by rerunning the vCenter installer. It did a repair install and added the missing component. See http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=201714...

[JayhawkEric]

I had the same issue and the repait install via the "change" button within programs and features worked for me as well.  Thanks for the post Jeremy!!