Hi..
I finished the vSphere Web Client SDK Setup ,after starting my virgo server i get the following error when i open the link https://localhost:9443/vsphere-client/.
A server error occured.
[500]SSO error:null
Check the vsphere webclient server logs for details.
Can you please help me,i am stuck here.
Regards
srini
> Check the vsphere webclient server logs for details.
What error(s) do you see in the logs?
(see docs/FAQ.html for the location of the logs)
These are the Errors that i see in the log generated in the path vsphere-client-sdk-6\server\serviceability\logs of the development machine.
[ERROR] system-artifacts org.apache.catalina.mbeans.GlobalResourcesLifecycleListener No global naming context defined for server
[ERROR] cm-catalog-manager-pool-5 com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be verified
[ERROR] cm-catalog-manager-pool-5 com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] http-bio-9443-exec-1 70000001 100001 ###### com.vmware.vsphere.client.security.websso.MetadataGeneratorImpl Error when registering ngc metadata.
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vim.sso.client.impl.SoapBindingImpl The SSL certificate of STS service cannot be verified
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.security.sso.impl.NgcSolutionUser Login as solution user failed.
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth Search failed for Health Status
[ERROR] ing.timer.TimerFactoryBean#0 com.vmware.vise.vim.cm.healthstatus.InventoryServiceHealth Could not find Health Status EndPoint for Inventory Service
Regards
Srini
hi Srini,
Can you describe your setup in details? thanks.
I have followed all the steps that was mentioned in the setup document in the docs folder.
Using eclipse as IDE and vcenter is in windows 2012 server which i have installed as a vm .
The only problem that i faced in the setup doc was ,there is a bat file which when run will generate 2 other files, in my case it wasn't generating Web client properties file,i got that file from a friend and used it.
when i open in the browser i get this error.
Regards
Srini
Hi Lauren. .
Any clue as to where i am going wrong? I am stuck at this point and there is not many clues in Internet as to how to go ahead.
Regards
Srini
> The only problem that i faced in the setup doc was ,there is a bat file which when run will generate 2 other files, in my case it wasn't generating Web client properties file,i got that file from a friend and used it.
Using someone else's webclient.properties is a big NO NO 🙂
It contains cm.url which must point to your own vCenter setup. Using another value there would explain your error.
Change cm.url to https://YOUR_VCENTER_DNS_NAME/cm/sdk/ and give it a try.
hi lauren,
i was also facing a similar kind of problem, but in my case i was actually getting the webclient.properties file, but with no DNS name in cm.url. since i don't have any DNS server, I tried to use the IP address of the server in the cm.url which didn't worked.
Then i tried giving it a random DNS name and resolved that DNS name locally using "%drivers%>etc>host file" at both the places(my development pc as well as windows server 2012 on which VCS is running). I was successfully able to ping both the systems from each other. But still it didn't work. Do you have any idea where i am going wrong.
thanks
Try running this command on your VCSA host:
keytool -printcert -sslserver localhost
There should be a DNS name somewhere in the output. That's what the dev-setup.sh script tries to extract.
Hi lauren,
I used other webclient.properties file but i made changes in that file.
I replaced the cm.url with my windows server 2012 ip on which i have setup the vcenter.I am using vcenter 6.0 on a windows server and not a vapp,so that cmd is not of much help.
Regards
Srini
As I explained you cannot use an IP address for cm.url in webclient.properties, it must be a DNS name.
(btw, my name is "Laurent", not "Lauren" 🙂
Hi Laurent ..sorry for misspelling your name.Can i resolve this by creating a dns server locally?
I don't know much about local dns servers, sorry!
By local DNS server i meant that , we will map the DNS name to IP address locally in file %drivers%/etc/host where we can specify dns to ip address mapping. (which fulfills the necessity of DNS server).
my question is if we are able to resolve the DNS name , do we still need a dns server for any other reason.
There is no way around the fact that cm.url must be use a FQDN (fully qualified domain name) to point to your VCSA or vCenter for Windows setup.
As I said earlier in this thread, try to run this command on the remote setup to find a FQDN that works:
keytool -printcert -sslserver localhost
Set the time for the entire domain and ensure that ESXi and vCenter are synchronised. It was my problem with the same message.