cannot connect to profile-driven storage service

[smetter]

Hello,

I want to test the profile-driven storage features,

but I'm stuck in the beginning...

I was able to enable VM storage profiles for my cluster.

Ever since then, when I open the vi client and log on to vcenter,

the following error pops up:

"vSphere Client cannot connect to Profile-driven storage service at https://vcenter:443/sps/sdk"

The "VMware vsphere Profile-Driven Storage Service" windows service seems to be running,
but after a couple of minutes it always seems to stop again.
Whether it is indicated as "running" or "stopped", the vi client keeps giving me the above error message.

The Orchestrator service is not running,
The Web client service is also not running.

In the windows system event log,
I can see the following:
"The VMware vSphere Profile-Driven Storage Service service terminated with service-specific error Incorrect function.."

Any ideas ?

[Virtualinfra]

refer the below KB

http://kb.vmware.com/kb/2001804

[smetter]

Thanks, but this KB can't help me.

I already found it before,

but this is not where my problem lies.

When I manually start or restart the profile driven storage windows service,

after make sure the vcenter windows service is already up and running,

I have the exact same error when connecting with the vi client.

The values for infiniteAttempt, attemptNumber, and sleepInterval listed in this KB are actually the default values in that xml file,

so these values are already there.

What's interesting though is that in this KB, port 31000 seems to be used in the "http://<VC_IP>:31000/sps/sdk" link,

while in the error I am getting,

I am seeing the following link "https://vcenter:443/sps/sdk"

--> port 443

--> and https instead of http.

Maybe an SSL issue ??

hmmmz

still don't know how to fix this though...

[smetter]

solved.

Apperently it was a hostname resolution problem.

The vcenter server was not part of an active directory domain yet,

and the fully qualified domain name taht was entered could

not be resolved.

After adding the vcenter host to the active directory domain everything is working.

[aseto]

I'm having the same problem but my vCenter is in AD. I tried accessing http://vcenter:31000/sps/health.xml and the page comes up but it when I try port 443, it says 503 Service Unavailable

[john23]

make entry in etc/host and connect back the vc... its worked for me...:)

[aseto]

my host files only has:

127.0.0.1 localhost

What am I adding now? This:

192.x.x.x vcenter ?

OR

127.0.0.1 vcenter ?

[john23]

try to add 192 one...check

[aseto]

no dice. Still broken.

[Ric0Zz]

Stop the WebClient service if you have it installed. Worked for me. The Web-Client was starting before vCenter service and took the port of the health service voor the sps.After stopping the VMware Webclient service the health service worked fine. After that it started the Web Client service again and everything worked fine after that.

As a solution i've made a dependenty for the Web-Client with vCenter. So basicly Web Client always start after vCenter.

Is this also a solution for you?

Greetz Rico

[aseto]

no luck

[afterlife]

Edit the extension.xml file for Short Message Service (SMS) and Storage Policy Service (SPS) located in the following directory:

Program Files\VMware\Infrastructure\VirtualCenter Server\extensions\<extension name>, where <extension name> is com.vmware.vim.sms for SMS and com.vmware.vim.sps for SPS.

For SMS:

http://localhost/sms/health.xml to http://localhost:<http_port>/sms/health.xml, where <http port> is the custom port number.For SPS:
http://localhost/sps/health.xmlto http://localhost:<http_port>/sps/health.xml, where <http port> is the custom port number.

change the sps one to http://ipaddress:31000/sps/health.xml that fixed this 503 error for me. Now everything is green

[aseto]

That fixed it, but I had to use the short name, not the IP or FQDN. I changed the SPS URL to http://vcenter:31000/sps/health.xml

[afterlife]

please give points if this solved your issue.

Thanks

[aseto]

how do you do that?

[AndyR8939]

Making the webclient a manual service worked for me in my VCP5 lab.

[Gaurav_Baghla]

Tried everything and finally

1) took a backup of the Database

2)uninstalled Vcentre

3)reinstalled Vcentre

4)Stopped all Services

5)Restored the DB

6)started the Services

worked Fine but took almost 2 hours to do so ...........

[IamTHEvilONE]

If you are the Original Poster, you have the option to award points to a specific post.  Basically, it's two buttons that say "Helpful" and "Correct"

This is why we suggest having separate threads for each person's issue ... and why aseto can't award points.