zmccraw
asked on
VirtualCenter 5.1 SSO issues
I keep receiving error 29114 unable to connect to DB when trying to install Vcenter 5.1b. I have tried everything recommended on the VMware site pertaining to the error, but nothing is working.
Has anyone else seen/encountered this error?
Has anyone else seen/encountered this error?
ASKER
I've verified everything in the KB article, and I'm using an account that has domain, enterprise, and schema admin privileges. It's still giving me the same cannot connect to DB error, and it rolls back the installation.
You mentioned that your account is a domain admin, schema admin etc..but when you type in the credentials for the DB server are you using a SQL account which has DB owner rights?
"This issue can occur because Windows authentication was used to connect to the database. To avoid this error, ensure that SQL Authentication is used when connecting to the SQL database. For more information, see Single Sign On Installation fails with error "Error 29115 Cannot authenticate to DB" (2035449)."
"This issue can occur because Windows authentication was used to connect to the database. To avoid this error, ensure that SQL Authentication is used when connecting to the SQL database. For more information, see Single Sign On Installation fails with error "Error 29115 Cannot authenticate to DB" (2035449)."
ASKER
Yes, the pre-installation stuff has you create a user, and that user was created using the SA credentials in VMware. The error I'm receiving seems to occur when the install runs the rsaIMSLiteMSSQLCreateSchem a.sql file. I've tried running it manually, but it doesn't seem to make a difference. I've attached the install log.
VCenter-install.log
VCenter-install.log
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I've read kb.vmware.com/kb/2036318 and changed the index. Still getting the same error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Are you using an account associated with an Active Directory domain?