Raudi
Expert
Expert

Can't upgrade the Update Manager with the version on the Update2 CD

Hallo,

i successfully updated my Virtual Center, but i can't update my Update Manager. When i now try to install the Update Manager i was asked for the login Informations to Virtual Center. But after this i got the message that the installation was interrupted. But not why.

In a log file in C:\WINDOWS\temp i found the following:

2008-07-27 13:56:40:451 '' 2168 ALERT  logUtil, 246 Product = VMware Update Manager, Version = 1.0.0, Build = 103284(Product Build = 63972)

2008-07-27 13:56:40:451 'lib.vdb.vdb' 2168 ERROR  47 LogonUser failed, err=1326

2008-07-27 13:56:40:451 '' 2168 ERROR  createDbSchema, 340 InitConnection: Windows impersonation failed

2008-07-27 13:56:40:451 '' 2168 ERROR  main, 127 InitConnection: Windows impersonation failed

The Update Manager is currently working normal and Virtual Center too, i have no idea what user i should enter at the installation to get this working.

I didn't want to uninstall the Update Manager and make a clean install because i didn't want to download all the patches again. Or is there a way, how i can uninstall it and use the already downloaded files?

Best regards

Stefan

0 Kudos
12 Replies
testqa
Enthusiast
Enthusiast

Hi there, do you have an SR open with vmware support? if yes, could you share the SR #?

If you haven't done so, please open one so we could track this issue!

Thanks!

0 Kudos
Raudi
Expert
Expert

This is in my unsupported testing enviroment. I want to made a test before i went to the customer. Today afternoon i will went to the customer. When i got the same error, i will open a Issue at the support...

0 Kudos
kjb007
Immortal
Immortal

Which user did you supply? The db user or the vc admin user?

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
Raudi
Expert
Expert

Both users i tryed...

0 Kudos
kjb007
Immortal
Immortal

Here's another thread with the same error that had a fix: http://communities.vmware.com/thread/158750

-KjB

vExpert/VCP/VCAP vmwise.com / @vmwise -KjB
0 Kudos
Raudi
Expert
Expert

The msvcr71.dll is already in the system32 directory and the same Version i found on the CD. This DLL is extracted during installation and will be executed from the temp directory, this i can see with the ProcessMonitor.

Now i found a log file in the temp directory of my profile with this error:

VMware Update Manager-build-103284: 07/29/08 18:55:57 Begin Logging

VMware Update Manager-build-103284: 07/29/08 18:55:57 --- CA exec: VMCheckUMDbSchema

VMware Update Manager-build-103284: 07/29/08 18:55:57 Setting property VUM_DB_UPGRADE =

VMware Update Manager-build-103284: 07/29/08 18:55:57 Getting Property TempFolder = C:\DOKUME1\ADMINI1\LOKALE~1\Temp\

VMware Update Manager-build-103284: 07/29/08 18:55:57 Getting Property VMUM_DIR = D:\Programme\VMware\Infrastructure\Update Manager\

VMware Update Manager-build-103284: 07/29/08 18:55:57 Getting Property VUM_DB_VERSION = 3

VMware Update Manager-build-103284: 07/29/08 18:55:57 Attempting to stream log4cpp.dll from binary table to 'C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\log4cpp.dll'

VMware Update Manager-build-103284: 07/29/08 18:55:57 Successfully wrote 139264 bytes to file C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\log4cpp.dll

VMware Update Manager-build-103284: 07/29/08 18:55:57 Attempting to stream libeay32.dll from binary table to 'C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\libeay32.dll'

VMware Update Manager-build-103284: 07/29/08 18:55:57 Successfully wrote 851968 bytes to file C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\libeay32.dll

VMware Update Manager-build-103284: 07/29/08 18:55:57 Attempting to stream msvcp71.dll from binary table to 'C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\msvcp71.dll'

VMware Update Manager-build-103284: 07/29/08 18:55:57 Successfully wrote 499712 bytes to file C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\msvcp71.dll

VMware Update Manager-build-103284: 07/29/08 18:55:57 Attempting to stream vmacore.dll from binary table to 'C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\vmacore.dll'

VMware Update Manager-build-103284: 07/29/08 18:55:58 Successfully wrote 2056192 bytes to file C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\vmacore.dll

VMware Update Manager-build-103284: 07/29/08 18:55:58 Attempting to stream db_config.exe from binary table to 'C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\db_config.exe'

VMware Update Manager-build-103284: 07/29/08 18:55:58 Successfully wrote 327680 bytes to file C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\db_config.exe

VMware Update Manager-build-103284: 07/29/08 18:55:58 Found "C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\db_config.exe"

VMware Update Manager-build-103284: 07/29/08 18:55:58 Attempting to launch "C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\db_config.exe --dbSchemaCheck 3"

VMware Update Manager-build-103284: 07/29/08 18:55:58 Process returned 3

VMware Update Manager-build-103284: 07/29/08 18:55:58 db_config.exe::Error - failed to connect to db

0 Kudos
mokotoe21
Enthusiast
Enthusiast

Hi,

Would you mind posting the logs or sending them directly to me via PM so that we can investigate this?

You can go to "Start > Programs > VMware > Generate VirtualCenter Server log bundle" and attach the zipped log file.

Regards,

Michael

0 Kudos
admin
Immortal
Immortal

"C:\DOKUME1\ADMINI1\LOKALE~1\Temp\vum\db_config\db_config.exe --dbSchemaCheck 3"
VMware Update Manager-build-103284: 07/29/08 18:55:58 Process returned 3
VMware Update Manager-build-103284: 07/29/08 18:55:58 db_config.exe::Error - failed to connect to db

That tells me the db connection failed. Was the update manager database up while you were trying to do upgrade? For upgrading, the db must be up for db upgrade.

Your other log shows:

2008-07-27 13:56:40:451 'lib.vdb.vdb' 2168 ERROR 47 LogonUser failed, err=1326
2008-07-27 13:56:40:451 '' 2168 ERROR createDbSchema, 340 InitConnection: Windows impersonation failed
2008-07-27 13:56:40:451 '' 2168 ERROR main, 127 InitConnection: Windows impersonation failed

This is odd. How did you install the earlier update manager, using your own db, or the db came with update manager? Did the db use the local system username/password, or network domain user name and password? It seems your windows authentication failed.

0 Kudos
Raudi
Expert
Expert

The database is up and the current version of the Update Manager can connect to it. The VC and the UM use the same database server, only different databases.

I installed the Virtual Center and Update Manager DB as described in this article:

What i'm wondering is: In the Event-Log/Security i can see a successful authentication but in the SQL Server log i can't see a login try. (Activated the logging of successful and unsuccessful logins)

Google told me to error 1326: Logon failure: unknown user name or bad password

I think the installation uses for login to the DB the Username/Password which is stored in the registry at Update Manager/DB.

Very strage...

0 Kudos
admin
Immortal
Immortal

So you did provide your own database for update manager. This is a good practice.

Please check your DSN for the credential: from the windows control panel, administrative tools, launch Data Source ODBC app. In System DSN tab, click the DSN that you provided to the update manager in your prior installation (it defaults to "VMware Update Manager", if you did not provide one). Then, click the configure... button, a new MS SQL server DSN configureation wizard will pop up, click the next button, what selection do you have on that page, "with integrated windows authentication", or "With SQL server authentication using a login ID and password entered by the user"? In the Login ID field, does the user name have a format of "domain_name/user_name", or just "user_name"?

0 Kudos
Raudi
Expert
Expert

The DSN seems to be correct, in the vim-all-msi.log i can see this:

Property(C): DB_DSN = VirtualCenter

Property(C): DB_SERVER_TYPE = Custom

Property(C): DB_USERNAME = srv10\vclogin

This are the same informations i found in registry under "Update Manager\DB". When i try to create a new DSN with the default name "VMware Update Manager" with SQL Server or SQL Native Client or the same Name "UpdateManager" with SQL Server i have still no success. I havn't proveided a username in the DSN because i havn't enabled the SQL security.

The only thing i noticed in the log:

Property(C): VMUM_DATA_DIR = C:\Dokumente und Einstellungen\All Users\Anwendungsdaten\VMware\VMware Update Manager\Data\

Property(C): VMUM_DIR = C:\Programme\VMware\Infrastructure\Update Manager\

This path is wrong, it must be:

Property(C): VMUM_DATA_DIR = D:\Programme\VMware\Infrastructure\Update Manager\Data\

Property(C): VMUM_DIR = D:\Programme\VMware\Infrastructure\Update Manager\

I think i will made a clean installation, the search for a soloution is to expensive. It is cheaper to make a new installation... It took already too much time.

0 Kudos
Raudi
Expert
Expert

I just uninstalled the complete Virtual Center and made a new clean installation with a new database...

Thanks to all they are trying to help me.

Best regards

Stefan

0 Kudos