Vcenter 5.1 upgrade error during single sing-on installation

[Anunn]

When we upgrade our vcenter server from 5.0 to 5.1 during single sign-on, the installation failed with error VMExecuteSSOCommand Error 29148.STS configuration error, this error was thown during the configuration process after the database schema check and any subsequent reinstall we tried will generate the exact same error at them exact same time during the install process, we're unable to find a solution anywhere, even google seach return absolutly nothing.

[spravtek]

Is there any more information to be found in the installation logs? Can you post the info here?

[Anunn]

Hi spravtek thank you for the reply, I've attached the sso installation lof file a log file with this post.

[spravtek]

Hi ... Thanks for the log ... I had a look through it.

The first thing I could find is the mention of the error you gave here: Error 29148.STS configuration error.

The STS part could point to database errors, are you using a specific password with some special characters in it? That has proven to sometimes cause troubles during the installation of SSO.

[Anunn]

Hi spravtek the only special character I used in the sql server password is "," single comma others are number + upper & lower case letters, I already chekced the special chareactor in the KB and it's doesn't seem to include comma, could it be something else?

[spravtek]

Of course it could be something else entirely, the error doesn't give us much to go on, it might be permission problems, make sure the install user, db user has the necessary rights ...

For example if you use a SQL Server account with sysadmin rights, make sure this login is also mapped to the databases master, msdb, ...

Are you using a remote DB?

[Anunn]

I'm using the build-in sql server database

[spravtek]

Are you now using the separate installer options when installing 5.1? Or are you using the easy install?

[Anunn]

First I use the simple install and failed with the error describe above, after that I run seperate individual install starting with sso which product the exact same error as the simple install.

[spravtek]

Sorry, was called away ...

Well, this is difficult one ... On the one hand it looks somewhat like this error

Same kind of log entries ...

But maybe you already saw it.

[abhilashhb]

Hi Anunn,

Have u ran the script for creating databases on your database server which creates tables required for single sign-on? You'll find the script in the installation iso. it creates a custom database and then you have to link that to the single-sign-on. 

[Anunn]

I thought the sso install would run thouse script, but the error I got occur during the config phase after the db schema check, it looks as if the db was configured correctly.

[abhilashhb]

When i did the installation recently i was following the admin guide and it said we'll have to manually run the scripts on the DB server. can you post the error's screenshot?

[Anunn]

The error log is attached in my above post, did you run the db script on seperate database or ms build-in database.

[abhilashhb]

Follow this

Prerequisites for the vCenter Single Sign On Database:

• Create a vCenter Single Sign On database, unless you plan to install the bundled database.
• If you are using an existing database with your vCenter Single Sign On installation or upgrade, make sure that the table spaces are named RSA_DATA and RSA_INDEX. Any other table space names will cause the vCenter Single Sign On Installation to fail.
• If you are using an existing database for Single Sign On, to ensure that table space is created for the database, run the script rsaIMSLite<DBName>SetupTablespaces.sql. The script is included in the vCenter Server installer download package, at vCenter Server Installation directory\Single Sign On\DBScripts\SSOServer\Schema\your_existing_database. You can run the script prior to the vCenter Server upgrade, or during the upgrade, when you are prompted by the Single Sign On installer. You can leave the installer to run the script, and resume the installer after you run the script.
• When you use an existing database rather than the database bundled with vCenter Single Sign On, the installation process requires database users with certain permissions. The type of users and their required permissions depend on whether you want the installer to create users for you or if you choose to create the users manually.

[TedH256]

Nice post

one thing I am still wondering - in an upgrade situation, can the vcenter 4.1 db also be the SSO db? Or, do we HAVE to either allow the installer to create an SSO DB, or create our own and run this script against it?

[abhilashhb]

Hi TedH256,

I think you need another database which has tablespaces named RSA_DATA and RSA_INDEX. Any other table space names cause the vCenter Single Sign On installation to fail. So at the end of the day the database you are trying to link to SSO should have these table spaces. And one way of creating the table spaces is to run the script thats provided in the intallation bundle.

[TedH256]

OK thank you - one last question (Just trying to nail down what my process should be when I am confronted with this next week):

For a small system, where vcenter and update manager are running on on server, when I run the SSO install is there an option to let SSO create it's own DB (using sql express)? And then I presume after that, I can run the vcenter upgrade, and still point at the existing db. Correct?

[spravtek]

Sorry for the late reply guys, needed to get to Barcelona

You can install vCenter with an SQL express DB and later do an upgrade to full SQL, migrate the database so to speak.

For small deployments some of my customers choose the appliance, all-in-one, and update manager on a separate server (together with syslog en dump collector, and so on)