VMware Cloud Community
CRIHB
Contributor
Contributor

vCenter Single Sign On 5.1 Installation issues...

Hello!

I was trying to upgrade our vCenter 5.01b installation to vCenter 5.1.  The first part is to install the SSO component and when I attempt to attach to any DB servers (local or remote) I cannot get connected.  I have read on a blog that the SSO has been hard coded so that the DB cannot have any periods, hyphens, or spaces.  We use hyphens in our server naming convention so I was wondering if this could this be the issue that is causing the SSO installation to fail to make the SQL connection no matter what DB instance or server I point it to?  I have tried to even do a "new" DB local install option with no luck.  Am I going to have to rename the server to get this to work?

Firewall's are turned off.  SA is available and the password is correct in addition to the install/service account having sysadmin access to the DB server.

0 Kudos
9 Replies
TonyNguyen
Enthusiast
Enthusiast

Hi CRIHB,

I struggled mightily with SSO. Took me like two days to get it to work. Smiley Happy

Derek Seaman's Blog is very helpful with some pointers on how to get it going.

http://derek858.blogspot.com/2012/09/vmware-vcenter-51-installation-part-1.html

I am pretty sure that the the periods.. hyphens, spaces apply to the DB name and not the server itself. All of my servers have dashes in them.

How did you create the SSO DB's?

What database type, and hostname / IP are you entering?

Hope this helps.

Sreec
VMware Employee
VMware Employee

Hi ,

     Have a look at the KB:http://kb.vmware.com/kb/2033137

Regard's

Sreejith.C

Cheers,
Sree | VCIX-5X| VCAP-5X| VExpert 7x|Cisco Certified Specialist
Please KUDO helpful posts and mark the thread as solved if answered
0 Kudos
CRIHB
Contributor
Contributor

Hello!  That is the exact blog I pulled the information from....  I have built a brand new server that doesn't use any hyphens in the name and still couldn't get the SSO module installed properly with a existing local SQL install.  The install looks to be broken since it is inconsistent at providing the line to provide SA password, and when attempting to manually connect there is a connection failure....

Thanks!

James

0 Kudos
MATTBR
Contributor
Contributor

Were you able to try these steps?

http://communities.vmware.com/thread/417915?tstart=30

Be sure to use mixed authentication mode on SQL and let the SSO installer created your local SQL users for you vs. the .sql script.

0 Kudos
jshelly
Enthusiast
Enthusiast

Has anyone been able to complete a fresh/clean install of 5.1?

I'm having no luck at all. I'm experiencing multiple errors...

[2012-09-18 14:07:06,360] WARN   530[main] - com.vmware.vim.installer.core.logging.CoreLoggerImpl.warn(?:?) - com.microsoft.sqlserver.jdbc.SQLServerException: Cannot drop the login 'RSA_DBA', because it does not exist or you do not have permission.
[2012-09-18 14:07:06,423] INFO   593[main] - com.vmware.vim.installer.core.logging.CoreLoggerImpl.info(?:?) - Users RSA_DBA and RSA_USER has been created successfully.

0 Kudos
CRIHB
Contributor
Contributor

Hello Everyone!

Basically the installation is broken.  IF trying to install to a previously installed local SQL MSDE the installer fails to locate the installation and never prompts for the SA password so that it can install the DB.  THE ONLY WAY I have been able to make it work is to install a NEW instance and move forward from there.

GOOD LUCK EVERYONE!!!:smileycool:

0 Kudos
escapem2
Enthusiast
Enthusiast

yeah installing my first VC 5.1 this has some changes 😮 and this SSO kinda difficult to get it to work.....wasted 3 hours already today and I am not going forward...looks like I am not the only one

0 Kudos
escapem2
Enthusiast
Enthusiast

not really happy managing vCenter using the Web client slow pretty slow and an error enabling HA after it was disabled

really don't like this

http://screencast.com/t/dbCEXj1E

0 Kudos
NelsonSFernande
Contributor
Contributor

Found a work around as apposed to a fresh install. For the install I removed the SA password and left it blank. The install finished without issue. Thanks for your post, it got me headed in the right direction. 

0 Kudos