Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 649
  • Last Modified:

MS SQL Express 2008 upgrade headache...Cannot connect...Instance failure.

Decided to put MS SQL Express 2008 on my Windows Server 2003 machine to replace MSSE2005.  All was working fine with the website with the 2005 version.  

Now, however, I can build and then connect to the site through the MS Visual Web Developer Express 2008, but when I try to hit the web site remotely, I get the 'failure to create an instance...'

I've uninstalled and installed several times.  When I try to get to the website remotely, I make sure the VWDE2008  is closed and not locking any files.  I've set the SQL service to run as 'Local System'; I've looked for stray \SQLEXPRESS directories to delete.

Very frustrating that everything works in the VWDE, but not when I try to connect remotely.  This was not a problem when using the 2005 VWDE and 2005 SQL Express.

Any help would be greatly appreciated.
  • 2
  • 2
1 Solution
So, show us the connection string you're using....   remember that the Express editions are expecting to provide [Your Server name]\SQLEXPRESS in the connect string
trinfoAuthor Commented:

 <add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\App_Data\ASPNETDB.MDF;Integrated Security=False;Connect Timeout=120;User ID=./Administrator;Password=XXXXXX" providerName="System.Data.SqlClient"/>

Changed to:  

<add name="ConnectionString" connectionString="Data Source=PSDXW701\SQLEXPRESS;AttachDbFilename=|DataDirectory|\App_Data\ASPNETDB.MDF;Integrated Security=False;Connect Timeout=120;User ID=PSDXW701/Administrator;Password=XXXXXX" providerName="System.Data.SqlClient"/>

Still no luck.  :-(
It appears as if you're using the "User Instance" feature of SQL Server...  where you are explicitly mounting an *.MDF file just for your application.   Is this what you were intending?  If so, then you should add/change to:
          Integrated Security=True;
          User Instance=True"

There is a pretty good write-up on User Instances here:  http://msdn.microsoft.com/en-us/library/bb264564.aspx
Recall that in the non-User Instance scenario, the user must  have Administrator rights to mount the database via the AttachDbFilename feature

trinfoAuthor Commented:
graye thanks for the input.  I originally had these parameters, and then changed to what you see now with a username with all rights.

I've decided to abandon MS SQL Express 8.  I was only using it for authentication.  I'm now using page authentication with another db and a little home grown code.

Something got messed up in the internals on that machine when I added MSSE8...and, this small re-write is easier than spending another two days on it.

Again, thanks for the effort!

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now