Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.
SQL and VMWare
SQL 2008 R2
Server 2008 R2
vCenter Server 4.1
I’m trying to get VMWare vCenter installed on my server. I have installed SQL and created a new database that I want to use for vCenter.
Under Database Options I select ‘Use and existing support database’.
I’ve tried to follow the directions in this article in order to set the connection up correctly:
http://www.techrepublic.com/blog/datacenter/installing-vmware-vcenter-prerequisites-on-windows-server-2008-r2/1791
1. Select the System DSN tab.
2. Click the Add button.
3. On the first page of the Create New Data Source wizard, choose SQL Native Client.
4. When prompted, provide a name and description of the new System DSN and indicate on which SQL Server the vCenter database resides.
When I select the dropdown list my system never finds my server so I type in the address 10.10.10.2.
5. For my example, I’ve used SQL Server authentication. On the authentication page, choose the authentication method most appropriate for your use. If you use SQL Server authentication, use the same login ID and password that you created as per the VMware documentation.
Under login I use my administrator credentials (to make this as painless as possible.)
I’ve gone to the database in SQL and made sure the administrator is the dbowner.
6. When prompted, test the data source to make sure it’s set up properly.
It fails with:
Connection failed:
SQL State: ‘08001’
SQL Server Error: 2
Could not open a connection to SQL Server [2]
SQL State: ‘HYT00’
SQL Server Error: 2
SQL Server Native Client 10.0 Login timeout expired.
Is this because I’m using the Admin account?
Server 2008 R2
vCenter Server 4.1
I’m trying to get VMWare vCenter installed on my server. I have installed SQL and created a new database that I want to use for vCenter.
Under Database Options I select ‘Use and existing support database’.
I’ve tried to follow the directions in this article in order to set the connection up correctly:
http://www.techrepublic.com/blog/datacenter/installing-vmware-vcenter-prerequisites-on-windows-server-2008-r2/1791
1. Select the System DSN tab.
2. Click the Add button.
3. On the first page of the Create New Data Source wizard, choose SQL Native Client.
4. When prompted, provide a name and description of the new System DSN and indicate on which SQL Server the vCenter database resides.
When I select the dropdown list my system never finds my server so I type in the address 10.10.10.2.
5. For my example, I’ve used SQL Server authentication. On the authentication page, choose the authentication method most appropriate for your use. If you use SQL Server authentication, use the same login ID and password that you created as per the VMware documentation.
Under login I use my administrator credentials (to make this as painless as possible.)
I’ve gone to the database in SQL and made sure the administrator is the dbowner.
6. When prompted, test the data source to make sure it’s set up properly.
It fails with:
Connection failed:
SQL State: ‘08001’
SQL Server Error: 2
Could not open a connection to SQL Server [2]
SQL State: ‘HYT00’
SQL Server Error: 2
SQL Server Native Client 10.0 Login timeout expired.
Is this because I’m using the Admin account?
Asked:
-
4
2
1 Solution
I'm running the install/setup from one machine. Firewall service is off. However, I turned it on and turn the firewall off.
Same error message.
Included that I didn't have on the original message is the line:
SQL Server Native Client 10.0 Named Pipes Provider:
However, I went in and enabled named pipes.
Same error message.
Included that I didn't have on the original message is the line:
SQL Server Native Client 10.0 Named Pipes Provider:
However, I went in and enabled named pipes.
Hello,
Is your SQL Server using the default instance? \\[ip address]\[instance]
That it didn't find the server with the dropdown is annoying, but ours had the same issue there. I would check to make sure the services for SQL Server are started, just to be sure.
If it's truly a login named 'administrator', ensure that the credentials are consisted in scope (AD network administrator: [domain]\Administrator, sql account: administrator, local administrator: .\administrator).
Thanks,
Chris
Is your SQL Server using the default instance? \\[ip address]\[instance]
That it didn't find the server with the dropdown is annoying, but ours had the same issue there. I would check to make sure the services for SQL Server are started, just to be sure.
If it's truly a login named 'administrator', ensure that the credentials are consisted in scope (AD network administrator: [domain]\Administrator, sql account: administrator, local administrator: .\administrator).
Thanks,
Chris
[domain]\Administrator - checked that
It's the administrative account for the box.
Defaul instance? No. I created a new instance (new database) called VMWareData to use.
It's the administrative account for the box.
Defaul instance? No. I created a new instance (new database) called VMWareData to use.
Hello again,
So in the spot where it asks for the SQL Server you'll need to type in:
\\10.10.10.2\VMWareData
Also, to rule out authorizations, make the domain\admin account a sys admin on the sql server instance (not just dbo). If I remember correctly, it want to create logins and other server objects and not just database objects.
Thanks,
Chris
So in the spot where it asks for the SQL Server you'll need to type in:
\\10.10.10.2\VMWareData
Also, to rule out authorizations, make the domain\admin account a sys admin on the sql server instance (not just dbo). If I remember correctly, it want to create logins and other server objects and not just database objects.
Thanks,
Chris
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Your question, your audience. Choose who sees your identity—and your question—with question security.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now