View Single Post
  #2 (permalink)  
Old November 8th, 2009, 03:48 AM
Imar's Avatar
Imar Imar is offline
Wrox Author
Points: 72,055, Level: 100
Points: 72,055, Level: 100 Points: 72,055, Level: 100 Points: 72,055, Level: 100
Activity: 100%
Activity: 100% Activity: 100% Activity: 100%
 
Join Date: Jun 2003
Location: Utrecht, Netherlands.
Posts: 17,086
Thanks: 80
Thanked 1,587 Times in 1,563 Posts
Default

Hi Geoff,
Quote:
but I also have SQL Server 2005 installed.
And do you want to use this version, or the Express edition? You often get this error when you try to target a SQL Server version that doesn't have user instances enabled, but the connection string tries that anyway.

You can try a few things:

1. Remove User Instance=True from the connection string

2. Change your connection string so it doesn't target the Express edition, but your full version of SQL Server.

I think you already saw this article: http://social.msdn.microsoft.com/For...5-cac99740949b

If not, take a look as it contains a lot of useful tips.

If this doesn't help, can you provide more info? E.g. whether you're on the machine directly or using remote desktop, whether you ran "sp_configure 'user instances enabled'" against the Express edition and any other relevant information?

I've seen this problem reported many times before, every time with a different fix, so it's not easy to fix it for you remotely... ;-)

Cheers,

Imar
__________________
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Follow me on Twitter

Author of Beginning ASP.NET 4.5 : in C# and VB, Beginning ASP.NET Web Pages with WebMatrix
and Beginning ASP.NET 4 : in C# and VB.
Did this post help you? Click the button below this post to show your appreciation!
Reply With Quote