VMware Cloud Community
zenomorph
Contributor
Contributor
Jump to solution

Cannot start VC Update Manager after U4

Hi there,

I just upgraded to VC2.5U4 and it seems the VC cannot connect to the Update Mgr dbase " [vcIntegrity,

867] ODBC error: (IM002) - [ODBC Driver Manager] Data source

name not found and no default driver specified"

this is the vmwar-vci-log file:

ODBC error: (IM002) - [ODBC Driver Manager] Data source name not found and no default driver specified

vim.fault.DatabaseError

VcIntegrityPlugin Start

VcIntegrityPlugin WaitStop

Stopping managed process rdevServer.exe

Stopping managed process vum-webServer.exe

Stopping managed process java.exe

Process monitoring stopped

Product = VMware Update Manager, Version = 1.0.0, Build = 145819(Product Build = 63995)

CryptoKey_Import: not in export format

CryptoKey_Import: not in export format

CryptoKey_Import: not in export format

Failed to get the module name for process 4. Ignoring the process

Failed to get the module name for process 5404. Ignoring the process

Starting managed process java.exe

Starting managed process rdevServer.exe

Starting managed process vum-webServer.exe

No running instance of webserver found

Process monitoring started

Internal Scheduled Task Manager created...

Email alert manager created...

Configuration manager created...

Entity locking manager created...

vaCrypto Initializing....

Loaded VALM key C:\Program Files\VMware\Infrastructure\Update Manager\ssl\valm.key

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for all: false

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.BaselineComplianceStatusCollector: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.ComplianceStatusCollector: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.ComplianceStatusManager: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.ContainerComplianceStatusCollector: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.ScheduledTaskManager: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.SessionManager: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.UpdateComplianceStatusCollector: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.VcIntegrity.remediate: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.VcIntegrity.scan: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.VcIntegrity.setConfig: true

2009-05-16 20:51:04:171 'Activation.trace' 6392 DEBUG Trace for integrity.VcIntegrity.setNewUpdateConfig: true

VcIntegrityPlugin Init

Add callback to Ufa Shutdown manager.

ODBC error: (IM002) - [ODBC Driver Manager] Data source name not found and no default driver specified

vim.fault.DatabaseError

VcIntegrityPlugin Start

ODBC error: (IM002) - [ODBC Driver Manager] Data source name not found and no default driver specified

vim.fault.DatabaseError

No started

Leave Validate. Failed

ODBC error: (IM002) - [ODBC Driver Manager] Data source name not found and no default driver specified

vim.fault.DatabaseError

No started

Leave Validate. Failed

ODBC error: (IM002) - [ODBC Driver Manager] Data source name not found and no default driver specified

vim.fault.DatabaseError

No started

Leave Validate. Failed

this is the error message I get when using Virtual Centre

Is it my ODBC name thats wrong, where can I edit that?

Any suggestions please.\

many thanks

0 Kudos
1 Solution

Accepted Solutions
Troy_Clavell
Immortal
Immortal
Jump to solution

0 Kudos
4 Replies
AndreTheGiant
Immortal
Immortal
Jump to solution

It seems that the VUM database does not exist or does not function.

The service is running (for the DB instance)?

From witch version have you done the upgrade?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

Andrew | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
zenomorph
Contributor
Contributor
Jump to solution

Andre,

I pretty much upgraded from the initial version

that came with VC 2.5 because we didn't really use it in the past and

when we upgraded to u4 I already created a new dbase "VMwareUpdateMgr,

if I look into SQL2k5 I can see the db tables for UMgr as well.

I had a look at the ODBC DSN and did a test and it can connect to the dB, so I'm not sure whats wrong.

many thanks

0 Kudos
Troy_Clavell
Immortal
Immortal
Jump to solution

here are a couple KB's that might be helpful

http://kb.vmware.com/kb/1006169

http://kb.vmware.com/kb/1006902

0 Kudos
zenomorph
Contributor
Contributor
Jump to solution

Guys reinstalled and reconfigured and got it working thanks................ Smiley Wink

0 Kudos