Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

ODBC and DSN errors installing vCenter Server (1003928)

Last Updated: 9/16/2019Categories: TroubleshootingTotal Views: 219953Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Installing vCenter Server fails

You see the error:

Re-configure your DSN to use one of the supported drivers

The VirtualCenter Server service does not start.

In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file, you see entries similar to:

ODBC error: (IM014) - [Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application.

In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file, you see entries similar to:

In Oracle:

ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-01017: invalid username/password; logon denied

or:

ODBC error: (HY000) - [Oracle][ODBC][Ora]ORA-12541: TNS:no listener

In SQL:

ODBC error: (08001) - [Microsoft][ODBC SQL Server Driver][DBMSLPCN]SQL Server does not exist or access denied

Purpose

During the initial installation of vCenter Server, if you are using a dedicated database server, you should create an ODBC Data Source that vCenter Server uses to connect to the database. If there are changes made to the physical environment, vCenter Server may fail and not start until the information in the Data Source is corrected.

This article provides steps to:

Check which Data Source vCenter Server is using

View and modify the Data Source used for vCenter Server (for both Microsoft SQL and Oracle)

Modify the username and password vCenter Server uses to connect to the database server

Resolution

Note: Some of the procedures in this article involve modifying the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393 .

Note: The preceding link was correct as of September 16, 2019. If you find the link is broken, provide feedback and a VMware employee will update the link.

Select the following troubleshooting steps are available as listed below:

Upgrading vCenter Server fails with the error: DSN is pointing to an unsupported ODBC driver or unsupported database driver (1015804)

Checking which Data Source is being used by vCenter Server

Viewing and modifying the database server and/or database used by vCenter Server (Microsoft SQL)

Viewing and modifying the database server and/or database tablespace used by vCenter Server (Oracle)

Modifying the username and password vCenter Server uses to connect to the database server (valid only for vCenter Server 2.5.x and below)

Change the password from command line

Checking which Data Source is being used by vCenter Server

vCenter Server 5.5:

To check which Data Source is currently being used:

Log in to the vCenter Server as an administrator.

Click Start > Run, type regedit, and press Enter. The Registry Editor window opens.

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

The name of the Data Source that is currently being used is in the 1 registry key. Make a note of this name for use in subsequent steps of this article.

Click File > Exit without making any changes.

vCenter Server 6.0:

To check which Data Source is currently being used:

Log in to the vCenter Server as an administrator.

Navigate to C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx.

Open vpxd.cfg within a text editor.

Search for <dsn> and make a note of the Data Source name.
<odbc>
<dbtype>embedded</dbtype>
<dsn>VMware VirtualCenter</dsn>
</odbc>

Open the tnsnames.ora file using a text editor.

Note: This file is generally located at C:\Oracle\Oraxx\NETWORK\ADMIN (where xx is either 9I or 10g). Look for an entry similar to the example below, where SERVICE_NAME is the TNS Service name to be changed in step 7:

VPX =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS=(PROTOCOL=TCP)(HOST=server)(PORT=1521))
)
(CONNECT_DATA =
(SERVICE_NAME = ServerTableSpace)
)
)
HOST =

In this example, HOST=server is the database host to which the client needs to connect, and SERVICE_NAME = ServerTableSpace is the TNS Service name that is being used from the Oracle server.

To change the host that is being connected to, modify server, to the name of the new server that the Data Source connects to.

To change the tablespace that is being used, modify ServerTableSpace to the name of the tablespace being used on the Oracle server.

When this is complete, save and close the file.

To confirm that the changes are successful:

Navigate to Start > Control Panel > Administrative Tools > Data Sources (ODBC).

For vCenter Server 4.0 running on a 64-bit host:

Click Start > Run, type %systemdrive%\Windows\SysWoW64\Odbcad32.exe, and press Enter.

Click the System DSN tab.

Select the Data Source that vCenter Server is using.

Click Configure.

Click Test Connection.

Enter the username and password, and click OK.

Review the message that is presented. If the change was successful, click OK and exit out of the driver configuration wizard. If the test fails, review and correct the changes to the configuration and try the test again.

Modifying the username and password vCenter Server uses to connect to the database server (valid only for vCenter Server 2.5.x and below)

A common misconception is that the username and password used for vCenter Server is stored within the Data Source. The username and password for vCenter Server are stored in the registry. Instructions on resetting the password from the installer and resetting the password manually are described below.

Note: Ensure that you are using SQL authentication if you are using a Microsoft SQL server because Windows NT authentication is not supported.

To reset the username and password from the Installer:

Log in to the vCenter Server as an administrator.

Click Start > Control Panel > Add or Remove Programs.

Click VMware VirtualCenter Server or VMware vCenter Server from the list of currently installed programs.

Click Change.

Click Next.

Select Repair.

Click Next.

Ensure that Use an existing database server is highlighted.

Note: If you are using an MSDE or SQL Express installation of vCenter Server, it is set up to use Windows Authentication by default and uses the account the service is set to start with. VMware does not recommended changing this configuration.

Click Next.

Enter the new username and password. Ensure that the Data Source name is correct, then enter the new username and password.

Click Next.

Click No when you are prompted with this message:

The DSN points to an existing VMware VirtualCenter repository. Do you want to reinitialize the database and start over with a blank configuration?

Warning: If you click Yes, your existing configuration is overwritten with a blank new one.

Click Next through the remainder of the installation, leaving the default options selected.

On the Ready to Repair the program screen, click Install.

When the repair is complete, exit the installer by clicking Finish.

To reset the username and password manually, without running the installer (valid for all versions of vCenter Server)

vCenter Server 5.5 and earlier:

Log in to the vCenter Server as an administrator.

Click Start > Run, type regedit, and click OK. The Registry Editor window opens.

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

The user that is configured for database connectivity is in the 2 registry key.

Right-click on the 2 key, and click Modify.

Change the Value data to the name of the new user account.

Click OK.

Click File > Exit without making any changes.

vCenter Server 6.0:

Stop the vCenter Server service. For more information, see Stopping, starting, or restarting VMware vCenter Server 6.0 services (2109881).

Navigate to C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx.

Take a backup copy of vpxd.cfg file.

Open vpxd.cfg file in a text editor.

Locate the <DB> element and modify the value for <key_2> to reflect the new database user ID.

...
<DB>
C:\Program Files\VMware\Infrastructure\vCenter Server\vpxd\

Run the command:

vpxd.exe -p

When prompted, enter the new password and press Enter.

Retype the password and press Enter again to complete the password change.

Note: If your issue still persists, contact VMware Support. For more information, see How to Submit a Support Request.

Related Information

Alternatively, if you can log into the vCenter Server using the VI Client (or vSphere Client), reset the password there:

Updating the VirtualCenter 2.5 database user password:

Note: These steps apply to VirtualCenter 2.5 only:

Log in to the vCenter Server as an administrator from the vSphere Client.

Click Administration > vCenter Management Server Configuration > Database.

Enter the new password in the Database Password fields.

Click OK.

Note: You must manually restart the VMware VirtualCenter Server service when this change is made, or reboot the host. This method only allows for you to change the database password. If you need to change the username follow the steps in the article above.

Updating the vCenter Server 4.x database user password:

To update the database user password stored in vCenter Server 4.x using the vSphere Client, see Updating the database user password stored in vCenter Server (2000493).

For translated versions of this article, see:

Español: La instalación de vCenter Server falla con errores de ODBC y DSN (2034983)

Português: Falha na instalação do vCenter Server com erro de ODBC e DSN (2037173)

Changing the vCenter Server database user ID and password
Upgrading vCenter Server fails with the error: DSN is pointing to an unsupported ODBC driver or unsupported database driver
Updating the database user password stored in vCenter Server
La instalación de vCenter Server falla con errores de ODBC y DSN
Falha na instalação do vCenter Server com erros de ODBC e DSN
vCenter Server 安装失败并出现 ODBC 和 DSN 错误
ODBC および DSN エラーが発生し、vCenter Server インストールに失敗する
How to stop, start, or restart vCenter Server 6.x services
Installation von vCenter Server schlägt mit ODBC- und DSN-Fehlern fehl

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (European)JapaneseSpanishEnglishGerman

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 7.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

view all

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant