Update Manager fails to scan a host with an unknown error

Products

• VMware

Issue/Introduction

Symptoms:

• vCenter Update Manager fails to scan an ESX host
• You may see these errors:
  • Scan Entity <name of host> VMware vCenter Update Manager had an unknown failure. Check Tasks and Events tab and logs for more details.
  • Unknown Error
     
• You see this error in vmware-vum-server-log4cpp.log (located in C:\Documents and Settings\All Users\Application Data\VMware\Update Manager or C:\Users\All Users\VMware\VMware Update Manager\Logs):

[2009-11-26 18:11:27:691 'BaselineMgr' 3784 WARN] [vciUtilities, 2777] Could not recompute baseline compliance for entity host-29: "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot find either column "dbo" or the user-defined function or aggregate "dbo.vci_CheckBaselineConflict", or the name is ambiguous." is returned when executing SQL statement "{CALL vci_compBaselineComplianceLeaf(?,?,?,?)}"

 

[2011-09-16 13:17:55:715 'SingleHostScanTask.SingleHostScanTask{99}' 3332 ERROR] [singleHostScanTask, 399] SingleHostScan caught exception: Database error (vdb) "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot find either column "dbo" or the user-defined function or aggregate "dbo.vci_CheckBaselineConflict", or the name is ambiguous." is returned when executing SQL statement "{CALL vci_compBaselineComplianceLeaf(?,?,?,?)}" with code: -1
[2011-09-16 13:17:55:728 'SingleHostScanTask.SingleHostScanTask{99}' 3332 ERROR] [vciTaskBase, 564] Task execution has failed: Database error (vdb) "ODBC error: (42000) - [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot find either column "dbo" or the user-defined function or aggregate "dbo.vci_CheckBaselineConflict", or the name is ambiguous." is returned when executing SQL statement "{CALL vci_compBaselineComplianceLeaf(?,?,?,?)}"

Resolution

This issue is resolved in VMware vSphere Update Manager 5.0 Update 1. You can download this version from the vSphere Download Center.

Prior to Update Manager 5.0 Update 1, this issue occurs when the vCenter Update Manager database is installed in a schema other than DBO.

 

To verify that the database tables are part of another schema on SQL:

1. Log in to the SQL instance using SQL Management Studio.
2. Select the Update Manager database.
3. Expand the tables and check the prefix. The tables should be named dbo.vci_xxx. If the tables start with any other prefix then it is not part of DBO schema.

To resolve this issue, change the database schema to DBO:

1. Connect to the SQL Server via SQL Server Management Studio. If you are unsure of how to do this, consult Microsoft's website on downloading or obtaining this utility.
2. When SQL Server Management Studio is open, navigate to Security > Logins.
3. Right-click the user specified in your ODBC for the vCenter Update Manager database and click Properties.
4. Select User Mappings on the left.
5. Select the vCenter Update Manager database name.
6. Change the Default Schema to dbo.
7. When the user mapping has been corrected, uninstall and reinstall vCenter Update Manager.

Alternatively, you can create a new Update Manager Database, ensuring that it is part of the DBO schema. For more information on how the database should be created, see Configure a Microsoft SQL Server Database in the VMware vCenter Update Manager Administration Guide.

 

Note: A Database Administrator is required to implement both resolutions.

Additional Information

Update Manager 未能扫描主机并出现未知错误 

Update Manager が不明なエラーでホストのスキャンに失敗する