Installation - Failed to connect to SQL database.

Question

When trying to install the TFSIntegrationTools (25 march 2011) I select the current SQL server instance on the machine (not the default SQLExpress).

When it starts to 'Executing SQL Strings' it throws an error stating 'Failed to connect to SQL database. (-2147467259 master )

At this point, I can only click OK and then the installer reverts everything.

Using SSMS (Microsoft Sql Server Management Studio) I can connect to the instance and query the master database using the same account.

 

 

---

MCP TFS 2010
Professional Scrum Developer Trainer - Scrum.org

Answer 1

What are you entering at the database prompt?   Just the current machine name (to use the default SQL server instance)?   Or <machine name>\<instance name>?  Or something else?   Are you an administrator of that SQL server instance?

Answer 2

I'm just using the 'default' instance of SQL Server, so I tried 'localhost', '<machinename>' and '.' : all give the same error.

I've verified using SSMS that I am indeed an administrator on the SQL server.

I'm doing this on a VM (the one available here: http://blogs.msdn.com/b/briankel/archive/2010/06/25/now-available-visual-studio-2010-rtm-virtual-machine-with-sample-data-and-hands-on-labs.aspx)

I have also run the Installation on my windows 7 install and that actually does run using the default 'localhost\sqlexpress'.

---

MCP TFS 2010
Professional Scrum Developer Trainer - Scrum.org

Answer 3

I got this error, so instead of LOCALHOST\SQLEXPRESS I installed it to MYCOMPUTERNAME\SQLEXPRESS  

This worked for me

Answer 4

I am getting the same error, and I have tried the 'machinename\instancename' with no luck.  I am on Win7 SP1 with SQL Server 2008 R2.  my account is a sysadmin role - so I'm not sure why this is failing.  any help is appreciated, thanks!

Answer 5

I'm also seeing this error.  An assistance would be appreciated

---

Matt Ruwe

Answer 6

I got same issue and got it resolve by replacing 'localhost' with '.'

Answer 7

I'm getting the same thing.  If I enter a bad server\instance name, installation doesn't get past the screen with that field.  But every combination I've tried goes through 80% of the installation and fails on "Executing SQL Strings" with this error.  And I've tried all these valid combinations because I have the default instance and SQL Express both installed:

.

localhost

<machine name>

.\SQLExpress

localhost\SQLExpress

<machine name>\SQLExpress

Also, I've run SQL Profiler and watched the queries that go through to the database engine.  I see the database get created, but then nothing happens when it reaches the step where it fails.  Is it failing connecting to the database it just created?