error when upgrading vcenter from 4.0 to 4.1

[tugi]

Hi,

I have an error when i try to upgrade vcenter from 4.0 to 4.1.

After run Setup, Upgrade databease step is getting this error. "Error occurred while connecting to the Data Source".

vcenter and sql is the same machine.

Sql version is Std. 2005 Sp3

vpxuser is a sysadmin

windows version is 2008 Std64 bit

vminst.log

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 --- CA exec: VMLaunchDbUpgradeWizard

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property SourceDir = C:\sources\VMware-VIMSetup-all-4.1.0-259021\vpx\

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property TempFolder = C:\Users\ADMINI~1\AppData\Local\Temp\1\

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_DSN = VCENTER

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_EXISTING_VERSION = 400

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Getting Property DB_USERNAME = vpxuser

VMware VirtualCenter-build-258902: 07/19/10 10:54:00 Found "C:\sources\VMware-VIMSetup-all-4.1.0-259021\vpx\dbupgrade\bin\VCDatabaseUpgrade.exe"

VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Process returned 6

VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Error occurred while connecting to the Data Source.

VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Getting Property UILevel = 5

VMware VirtualCenter-build-258902: 07/19/10 10:54:01 Getting Property ProductName = VMware vCenter Server

VMware VirtualCenter-build-258902: 07/19/10 10:54:02 End Logging

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Begin Logging

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 --- CA exec: VMCleanupRegistry

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Getting Property TEMPLATE = x64

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Warning: Deleting a key that isn't empty: "HKEY_CURRENT_USER\VMW"

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 Warning: Deleting a key that isn't empty: "\InstRTPaths"

VMware VirtualCenter-build-258902: 07/19/10 10:54:03 End Logging

[RAMESA]

Did you create 32bit as well as 64bit dsn (system dsn)? Both should point to same database and connection should pass.

Please upload log files from %temp%

[tugi]

I have just 64 bit dsn. you can find all log files as attached.

thx.

[RAMESA]

For upgrade you need to have 32bit as well as 64bit dsn. Can you create both and try upgrade?

[tugi]

I tried but doesn't work.

same error.

[RAMESA]

as per log file -

Info: Beginning upgrade process....

Info: VCENTER has been detected as a SQL server.

Error: ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection.

ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection.

Initialize failed, exiting...

Looks like something is wrong with user name using which we are trying to connect db. Can you cross check authentication once again from odbc?

or try -

from command line navigate to installer directory till path "\vpx\dbupgrade\bin"

try command - VCDatabaseUpgrade DSN= QUIET=true

Let me know what is the result

[tugi]

You are right, the user name is blank. The same thing when looking at the database log.

Why the user name is blank?

I ran the command and same error.Log as follows.

Info: Beginning upgrade process....

Info: vcenter has been detected as a SQL server.

Error: ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection.

ERROR [SQL Native Client][SQL Server]Login failed for user ''. The user is not associated with a trusted SQL Server connection.

Initialize failed, exiting...

[RAMESA]

Few places that you need to check -

In the install wizard did you provide username password at dsn info screen?

In the dsn details for 32bit as well as 64bit did you provide right username?

check the value of db username in registry under VMware VirtualCenter.

Also can you provide me exact command that you used?

[admin]

Please refer to the following KB article-

http://kb.vmware.com/kb/10090

[tugi]

In the install wizard username is vpxuser and i enter just password at the dsn screen.

Yes 32 bit and 64bit dsn is set by vpxuser

What is the location of db username at registry?

I ran the command you sent me "VCDatabaseUpgrade.exe DSN=vcenter UID=vpxuser PWD=****** QUIET=true"

[RAMESA]

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB

or

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter\DB

did you check the kb article

[tugi]

under

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware

VirtualCenter\DB

VCENTER

vpxuser

which kb article?

[RAMESA]

Please refer to the following KB article-

http://kb.vmware.com/kb/10090

[tugi]

I've already checked this article.

[ABoeff]

Hi tugi,

it is possible that we both had the same problem...

http://communities.vmware.com/thread/276714

[RAMESA]

Is it possible for you to take a video clip from installer launching to getting error so that we can find out exactly what is the problem?

As per my understanding if this is not related to kb; in the installer wizard if connection is working fine it should work t db upgrade wizard.

[tugi]

i solved the problem. Unfortunately, problem is local regional settings. When i change from Turkish to English, it works well.

Thx for everyting, espacially RAMESA.

[RAMESA]

Good to know that your issue has been resolved. But i am really surprised how come regional setting make any difference (even when you dsn, dbuser, dbpwd everything is in english). Anyway I will try my luck to reproduce this.

[twentygb]

I had this exact same problem and was able to solve it. Turns out to be an invalid character in the VC database password. How rude!

I started by looking in the vminst.log and found ...

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Found "D:\vpx\dbupgrade\bin\VCDatabaseUpgrade.exe"

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Process returned 6

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Error occurred while connecting to the Data Source.

I looked in the VCDatabaseUpgrade.log and found this...

Info: Beginning upgrade process....

Info: VMware VirtualCenter has been detected as a SQL server.

Error: ERROR [http://SQL Server Native Client 10.0|http://SQL Server Native Client 10.0][SQL Server]Login failed for user ''.

ERROR [http://SQL Server Native Client 10.0|http://SQL Server Native Client 10.0][SQL Server]Login failed for user ''.

Initialize failed, exiting...

So I looked in the errorlog on the SQL side and this is what I saw...

2010-10-13 13:21:42.43 Logon Error: 18456, Severity: 14, State: 8.

2010-10-13 13:21:42.43 Logon Login failed for user ']

Conclusion

I looked at the password that I was using for the VC sql database and it had some special characters. I decided to change the password so that it used more "programming language" friendly special characters (i.e., no quotes or periods). and low and behold the error disappeared!!!!

Whatever method the VM installer uses to pass the SQL password must be the root source of this particular problem.

VMware please take note and check for this during install to prevent future users the trouble.

Thank you

-Chris

[mcssoftware]

twentygb wrote:

I had this exact same problem and was able to solve it.  Turns out to be an invalid character in the VC database password.  How rude!

I started by looking in the vminst.log and found ...

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Found "D:\vpx\dbupgrade\bin\VCDatabaseUpgrade.exe"

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Process returned 6

VMware VirtualCenter-build-258902: 10/13/10 13:03:40 Error occurred while connecting to the Data Source.

I looked in the VCDatabaseUpgrade.log and found this...

Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Info: Beginning upgrade process....

Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Info: VMware VirtualCenter has been detected as a SQL server.

Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Error: ERROR Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED[http://SQL Server Native Client 10.0|http://SQL Server Native Client 10.0][SQL Server]Login failed for user ''.

ERROR Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED[http://SQL Server Native Client 10.0|http://SQL Server Native Client 10.0][SQL Server]Login failed for user ''.

Re: error when upgrading vcenter from 4.0 to 4.1 - SOLVED Initialize failed, exiting...

So I looked in the errorlog on the SQL side and this is what I saw...

2010-10-13 13:21:42.43 Logon       Error: 18456, Severity: 14, State: 8.

2010-10-13 13:21:42.43 Logon       Login failed for user ']

Conclusion

I looked at the password that I was using for the VC sql database and it had some special characters.  I decided to change the password so that it used more "programming language" friendly special characters (i.e., no quotes or periods). and low and behold the error disappeared!!!!

Whatever method the VM installer uses to pass the SQL password must be the root source of this particular problem.

VMware please take note and check for this during install to prevent future users the trouble.

Thank you

-Chris

I can confirm this happened to me as well.  I had a 16 char password with symbols and both the 4.1 agent pre-upgrade checker and the 4.1 vcenter installer had issues with this.  I had to change the database user's password to somethng else (only alpha, numeric) and then update the DSN before the install would complete.  This appears to be a problem in the way that the installers are creating the connection string - maybe not escaping the password?? Anyway, seems to be a bug to me.  I was upgrading from 4U2 to 4.1.  This was the second upgrade for this vcenter server - the first being a 4U1 to 4U2 (which worked fine with the "bad" password).