Troubleshooting vCenter Server 5.5 Configuration: malfunctioning identity source

I am currently configuring a VDI configuration with vCenter Server 5.5.0a and keep running in to the error:

"The authentication server returned an unexpected error: ns0:RequestFailed: 'Server Hash' value should not be empty. The error may be caused by a malfunctioning identity source."

After installing and configuring the vCenter Server and Connection server I am able to deploy a pool of virtual machines and log in to them without any issues.

However, the next day I come in and try to log in to the vCenter Web Client with any account (SSO Admin or other domain accounts I've privileged) I get the above error. I've looked through many of the logs and cannot tell exactly what to fix to make this error go away.

The only way I have been able to resolve this issue of logging in is to re-install this 5.5.0a software suite with the same databases, but I need a permanent fix. We started out at version 5.5.0, but VMware Tech Support recommended that I upgrade to 5.5.0a. I upgraded this software suite and it did not fix the issue. I've looked through many of the kb articles and nothing really seems to point me in a good direction.

*Note: After this error occurs I CANNOT log in to the Web Client with any account.

This error seems to be consistent with occurring the next day when I come in, but throughout the day that I have set it up it seems to work without any issues.

After I reboot the server, I get the following error message:

"Failed to connect to VMware Lookup Service - https://Ourservername.com:7444/lookupservice/sdk"

After I reboot the server, the vCenter Server service and the Identity service fail to start up properly. I've looked up how to troubleshoot that error message and the kb's on VMware's site don't lead me to fixing this issue. I try to re-register the SSO with vCenter Server (through the scripts in the VMware folder) and it fails to connect.

Any ideas on what I could try to resolve this?
CommCatzAsked:
Who is Participating?
 
IanThConnect With a Mentor Commented:
vcenter virtual appliance doesnt exist anymore its the web client now in 5.5
0
 
IanThCommented:
see

http://www.riccardoriva.com/blog/?p=1301

suggest ssl certificate error he has a workaround
0
 
CommCatzAuthor Commented:
Thank you for the suggestion, but I'm not currently using the vCenter Virtual Appliance in our environment I'm using the "regular" vCenter Server.
0
All Courses

From novice to tech pro — start learning today.