VCenter on MS SQL 2008 R2 installation

Hello

I can't install vCenter (4.1 Update 1).

I installed a basic MS SQL Server R2 on a Windows Server 2008 R2.

Installing vCenter I block at the choice of the database level.

He therefore asks me if I want to use a 2005 Express version or a database of existing support. So I choose the second option, but it offers me nothing in the drop-down list (DSN).

When I enter the name of the previously created DSN (via the control panel > administrative tools > Data Source (ODBC)), I have an error message "the DSN"xxx"does not exist or is not a 64-bit system DSN. vCenter Server requires a 64-bit system DSN. »

1 - remember to install the client SQL 2008 R2 on the vCenter

2 good create a "System DSN" and not UN "user DSN".

3. to install at least a vCenter 4.1 (en 4.0 go looking for ODBC administration in SysWOW64)

Eric

Tags: VMware

Similar Questions

  • vCenter 4.1 & SQL 2008 R2

    I try to install vCenter 4.1.0 - 259021 on my new Server Windows 2008 R2 standard and SQL 2008 R2 Express 64 bit (build 10.50.1600)

    Is this a supported VMware platform? (no trace on vsp_compatibility_matrix.pdf)

    Thanks for help

    Mauro

    The OS is fine.

    But also check compatibility (page 12) DB.

    The ony SQL Express that is supported is the 2005 version.

    And SQL Server 2008 R2 is not supported at all, in fact. Only 2008 and 2005 versions.

    André

  • vCenter database for SQL 2008 recommendations

    (1) databases of vCenter 2.5 runs on SQL 2008?

    (2) vCenter 4 databases will work on SQL 2008?

    I have searched 2.5 vCenter database requirements and come up empty.  Does anyone know if VMware supports SQL 2008?

    I'd start on page 71 of the http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_vc_installation_guide.pdf

    Rick Blythe

    Social media specialist

    VMware Inc.

    http://Twitter.com/vmwarecares

    http://Twitter.com/vmwarekb

  • VCenter on Windows Server 2008 R2 installation

    I wonder if there could be problems installing VCenter on Windows Server 2008 R2?  We also manage VMware View in our environment VSphere and plan that upgrade to the latest version.  Anyone experiencing problems with the help of Windows Server 2008 R2 for VCenter?

    We are running the most recent version of vCenter on Windows Server 2008 R2, and he's not going great.

  • Configuration of SQL 2008 R2, Enterprise Edition for vCenter Server 5.1

    Greetings to all seasons.

    Kind of a newbie here. That's my lab environment.

    I have always used the vCenter Server install Simple option that also installs the shipped Microsoft SQL 2008 R2 Express edition.

    Now, I do an eval of vSphere 5.1 and I want to manually configure a database server using the Microsoft SQL 2008 R2 Enterprise Edition.

    I know how to install the database server and it works. But I do not know how exactly set up a database for vCenter Server.

    I looked at the guide Configuration / Installation of vSphere and I don't seem to be able to follow the preparation vCenter Server databases section, because I'm not a person to the database. Y at - it any other guide or a blog, I can follow? I searched a lot and found everything I was looking for. Thought I would ask here.

    Here are the virtual machines I have.

    Lab - DC1 (domain controller)

    Lab - DC2 (domain controller)

    Lab-SQL1 (SQL 2008 R2, Enterprise Edition)

    Lab-SQL2 (SQL 2008 R2 Enterprise - subsequently configure failover clustering)

    Lab-VC1(vCenter Server 1)

    Any help is appreciated!

    Happy holidays.  Here is a link to another site with a nice installation guide for SQL 2008 for VMware.  Version 4.x, published in lonesysadmin.net was very helpful, so I'm sure that the 5.x update (have not read through it again) must be all too packed with useful tips.

    http://lonesysadmin.NET/2011/10/06/how-to-install-Microsoft-SQL-Server-2008-R2-for-VMware-vCenter-5/

  • VCenter 4.1 install error on a french MS SQL 2008 SP1

    Hi, we have a problem with a windows 2008 R2 (US or EN) and a MS SQL 2008 EN SP1.

    We cannot install the vcenter server. We have an error "Error 25003. Installation failed to create the repository of the vCenter server. »

    It works with MS SQL Express 2005 or 2008 US.

    It also works with a MS SQL 2008 SP1 US.

    That's OK with a MS SQL 2008 SP1 EN when we install a vcenter 4.0 Update 1.

    We have another problem:

    We cannot account system choice when we install Vcenter 4.1 with a DSN for SQL 2008, even when we turn off the UAC.

    Kind regards.

    Xavier

    PS: Here is the error in the windows event viewer:

    Log name: Application

    Source: VMware VirtualCenter Server

    Date: 2010-07-21 15:22:14

    Event ID: 1000

    Task category: no

    Level: error

    Keywords: Classic

    User: n/a

    Computer: VCENTER

    Description:

    The description of event ID 1000 in the source VMware VirtualCenter Server is not found. The component that triggered the event is not installed on the local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the 'event originated on another computer, the information display must be registered with l' event.

    The following were included with the event:

    A database error: "ODBC error: (22007) - Microsoft . http://SQL Server Native Client 10.0SQL ServerLa a type conversion of varchar to datetime data type data has created an out of range value. "is returned when you run the SQL statement" "

    INSERT INTO VPX_LIC_METADATA (LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)

    "VALUES (0, ' 1900-12-31 00:00:00 ', 0, ' 1900-12-31 00:00:00 ', NULL, 1, 208).

    The message resource is present but the message is not in the table of chains or messages

    The event XML:

    PS2: error in the vpxd.log

    Section of VMware VirtualCenter, pid = 616, version = version 4.1.0 build-258902 = option = exit

    Current working directory: C:\Windows\system32

    Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs

    Initializing the SSL

    Using the libcrypto, version 9080CF

    Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

    A database error occurred: "ODBC error: (22007) - [http://SQL Server Native Client 10.0 | ]. http://SQL Server Native Client 10.0] [SQL Server] One of the type conversion of varchar to datetime data type data has created an out of range value. "is returned when you run the SQL statement" "

    INSERT INTO VPX_LIC_METADATA (LAST_SAMPLE_ID, LAST_SAMPLE_TIMESTAMP, RETAINED_SAMPLE_ID, RETAINED_SAMPLE_TIMESTAMP, GLOBAL_DIGEST, IS_STATE_VALID, WEEK_KEEP_COUNT)

    "VALUES (0, ' 1900-12-31 00:00:00 ', 0, ' 1900-12-31 00:00:00 ', NULL, 1, 208).

    Is not init tableDef object: Vdb instance is not initialized or is fired

    Failed to initialize LDAP backup

    Xavier, I got the same error (with German SQL Srv).

    I have changend a few values in the DSN configuration:

    • change the language of the system for English messages

    • Uncheck the perform Translation for character data

    • Uncheck the use regional settings when out currency, numbers, Dates, times and

    After that, I installed successfully vSphere 4.1 server.

    Kind regards

    Andreas

  • The installer of SQL 2008 R2 - I get could not open key: UNKNOWN\Components\C89F41A0CA86

    I'm trying to install SQL 2008 R2 on a Windows Server 2008 computer. There a SQL 2005 and 2008 R2 installed before.
    I uninstalled everything about SQL using the Add/Remove Programs, CCleaner and Windows Installer cleaner.
    I'm under SQLEXPRWT_x64_ENU.exe (date of Monday, April 5, 2010 09:29:28) I downloaded from Microsoft. I unlocked the file, I am logged in as an administrator and I run as administrator.
    I get
    The following error occurred:
    Could not open key: UNKNOWN\Components\43C313DB6EBAD154F901C6B5BFA69F06\C2BF01D69A282F04190DB76EC40FAD2F.   Check that you have sufficient access to that key or contact your support team.
    Another window shows:
    Description:
    SQL Server 2008 R2 Setup has encountered an error.

    Signature of the problem:
    Problem event name: SQL100MSI
    Signature of the problem 01: 10.50.1600.1
    Signature of the problem 02: 10.50.1600.1
    Signature of the problem 03: SqlSupport.msi
    Signature of the problem 04: 0xE1C5DEF0
    Signature of the 05:1402 problem
    Signature of the 06 problem: Install_SqlSupport
    OS version: 6.0.6002.2.2.0.272.7
    Locale ID: 1033

    More information about the problem:
    LCID: 1033

    It occurs during the installation of Support files, ExecuteStandardTimingsWorkflow.

    Someone at - it ideas?
    Thank you
    Deb

    Hi Deb,

    Your SQL 2008 R2 issue is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the IT Pro TechNet public. Please post your question in the SQL Server Forum. You can follow the link to your question:
    http://social.technet.Microsoft.com/forums/en-us/category/SQLServer

  • Change Vcenter DSN 2005 SQL native client for SQL 2008 native client

    Hi all.

    I tried to upgrade our Vsphere for VM Windows 5.5 to Vsphere 6.0 for Windows (latest version of January).

    The upgrade checking failed after entering the credentials of user Vcenter. The error is 'unsupported database driver.

    In fact the DSN connection uses the SQL native client 2005.90.2047. Is also on the system SQL native client 10. (Version 2009.100.2500) is installed. I think it's the SQL 2008 R2 native client.

    The SQL Vcenter database is on a remote database SQL 2008 R2 server.

    I tried to change the DSN of SQL native client 10. The service started, but I've seen lots of SQL errors in the vpxd.log. I could solve only to return to the snapshot and restore the SQL database.

    How can I change the SQL Native client to connect DSN correctly?

    Thank you very much in advance?

    Edy

    Have you removed the old DSN entry and created a new using the driver of the new (and good)? And have you checked the registry if your change reflected here (\VMware Virtualcenter\DB HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.)?

  • Leaving the vCenter, database SQL 2008 R2 to SQL 2012 R2

    Hi guys,.

    I have a project to move our of vCenter company database in SQL 2008 R2 Cluster at our new farm of R2 SQL 2012, is it as simple as:

    1. backup of database

    2 restore database in SQL 2012 R2

    3. set up new DSN (SQL Native 11 for 2012 R2?) pointing to vCenter server

    OR is there more to him because of the differences between SQL 2008 R2 and SQL 2012 R2?

    PL, refer following links: -.

    http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=7960893

    or even more plus easy & accurate steps are here:-

    Migration of database SQL Server of VMware vCenter. vDestination: you & #039; Re almost there

  • vCenter on vOrchestrator on SQL 2005 and SQL 2008?

    I was reading the support for vCenter and vOrchestrator matrix and was surprised to see that vCenter is fully supported on SQL 2008 but vOrchestrator is only supported on SQL 2005. As we all migrate to SQL 2008, we want to install as many vSPhere on SQL 2008 as possible. Is - it possible/decision-making supported to install vSphere on SQL 2008 and then separately install vOrchestrator on SQL 2005? Installing vCenter it seems to me that if both components have been installed at the same time, but maybe it was because I was in a lab environment and went with the built-in SQL Express.

    Any word on what vOrchestrator will support SQL 2008? I really don't like VMware may not have common requirements for all their products. I know that vOrchestorator was an acquisition, but still... come on people! Life is complicated enough.

    vCenter and Orchestrator use their own databases, you can install vCenter on SQL 2008 and Orchestrator 2005 without problem.

    ---

    VMware vExpert 2009

    http://blog.vadmin.ru

  • support for MS SQL 2008 vCenter

    Hello

    Does anyone have an idea what vCenter release will support Microsoft SQL 2008?

    Thank you

    vSphere supports SQL 2008 for the VC database - it also support WIndows 2008 for installing vCenter 4.0

    If you find this or any other answer useful please consider awarding points marking the answer correct or useful

  • Installation fails for SQL Server SP 2 on SQL 2008 R2

    I have SQL 2008 R2 Developer Edition (64-bit) running Windows 7 (64-bit). I followed many workaround solutions listed on this forum all to no prevail!

    I noticed an error in the log in details:

    2010-12-22 06:02:08 Slp: error: Action "SqlEngineConfigAction_patch_configrc_Cpu64" failed during execution.
    2010-12-22 06:02:08 Slp: Action 'ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi' will return false because of the following conditions:
    2010-12-22 06:02:08 Slp: Condition "condition of dependence of the action starring: ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64_Patch_ConfigRC_postmsi the condition check function: MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64.» There are 2 characteristics of the dependant. The feature is tested for results: ValidateResult, result. "has failed because it has returned false and true was expected.
    2010-12-22 06:02:08 Slp: Condition is false, because the required functionality SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 has failed in the result

    Hello

    Your question is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for SQL server on Technet. Please ask your question in the Technet forum .

    Diana

    Microsoft Answers Support Engineer

    Visit our Microsoft answers feedback Forum and let us know what you think.

    If this post can help solve your problem, please click the 'Mark as answer' or 'Useful' at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.

  • Migration of Vcenter DB from SQL SERVER 2005 to SQL 2008 Express

    Hello
    I'll migrate the physical vcenter server to a virtual machine, then I'll install a new VM with OS 2008R2 and SQL2008. But I need the migration plan
    vCenter DB from SQL 2005 to SQL2008. VMware also recommends

    Note: 1) VMware recommends now IP address and host name the same information to facilitate the migration.

    (2) software migration to different vCenter Server, Manager of update or VMware Orchestrator. For example, Site Recovery Manager is not migrated.

    (3) move the VMware Orchestrator database. You must do it manually.

    We can give to vcenter server new name and IP and if yes what will be then problem occur after the post migration.

    Thank you

    vmguy

    It takes to keep the same name and IP address? If we will give different vcenter and IP server name then how will transfer of post stage

    If you can keep the same name of host and IP, this would make it so much easier.  That said, if you need to change the host name and IP address of vCenter you can run into issues where all your guests appear as disconnected. Usually, you can right click and choose 'connect', asked credentials for your hosts of ESXi, but after that they should remain connected.

    In addition, just in case I posted above another KB.

  • SQL 2008 R2?

    Anyone running vCenter 4.0 U1 against SQL 2008 R2? I tried to make the switch last night with no luck. I want to do this so that we can go off the power for the installation of SQL SERVER 2005 Express, before moving on to 4.1.

    Any input would be much appreciated!

    not compatible for a DB vCenter

    VMware vSphere compatibility matrices

  • PROBLEM CONNECTING TO SQL 2008 EXPRESS WITH ASP CLASSIC BETWEEN THE WORKSTATIONS ON A PRIVATE NETWORK

    I have created a private network (no internet connection) of four workstations, each running a SQL Express 2008 installation.  All four laptops are running Windows 7 Professional.  I created a homegroup for this private network.  While I don't care sharing of files between the four workstations, I have three of them in order to connect to the SQL 2008 Express database on the fourth mobile through channels of connection in the classic ASP programs.  Each of the four laptops can see others in the network.  I can ping the ip addresses of each to the other without any problem.  When I try to launch the ASP program on three laptop computers that attempt to connect to the SQL database on the fourth, I get the server does not exist or don't access denied error '80004005'.  The same program can also run on the fourth laptop and connects to the SQL database with no problems.  I tried to use SQLOLEDB and SQLNCLI10 provider in the chain of connection on the other three.  This operation fails.  I tried to add the IP address of the computer hosting the database as a Data Source in the connection on the other three string and still fails.  Named pipes and TCP/IP are enabled.  Each laptop can connect to the instance of SQLEXPRESS executed on each, but I need three to be able to connect to the instance of SQL Express running on the fourth.  Any ideas what I can do wrong?  This connection string works fine in the ASP program to connect to the local database on each laptop:

    Connection.Open "PROVIDER = SQLOLEDB; Server = computername\sqlexpress; UID = MyUser; PWD = MyUserPassword; DATABASE = MyDatabase ".

    Nothing seems to work for the chain of connection than the other three laptops to do to connect to this database on the fourth laptop.

    This issue is beyond the scope of this site and must be placed on Technet or MSDN

    http://social.msdn.Microsoft.com/forums/en-us/home

Maybe you are looking for