 |
BOOK: Beginning ASP.NET 3.5 : in C# and VB BOOK ISBN: 978-0-470-18759-3
 | This is the forum to discuss the Wrox book Beginning ASP.NET 3.5: In C# and VB by Imar Spaanjaars; ISBN: 9780470187593 |
|
Welcome to the p2p.wrox.com Forums.
You are currently viewing the BOOK: Beginning ASP.NET 3.5 : in C# and VB BOOK ISBN: 978-0-470-18759-3 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
|
|
|
|
|
November 24th, 2009, 12:35 PM
|
|
Authorized User
|
|
Join Date: Nov 2009
Posts: 15
Thanks: 0
Thanked 1 Time in 1 Post
|
|
Ch 11 and SQL Server Express
When I double click on the mdb in solutions explorer I get a message saying that SQL Server Express 2005 needs to be running. The message also gave a link to installing Express so I did so, except that the version is now 2008. I installed it and still get the same error message.
I checked and the server is running. Appendix B said to enable Named Pipes and TCP IP, in the configuration mgr and restart server. Did this, same error.
Am I on the right track? Not sure what is next. I am running the server on the same PC as VWD.
I looked for older posts dealing with this but could not find any.
The exact error message is Connection to SQL Server files (*.mdf) requires SQL Server Express 2005 to function properly.
Last edited by glenng; November 24th, 2009 at 02:21 PM..
|
|
November 24th, 2009, 04:16 PM
|
 |
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
Hi there,
What's the name of your SQL Server Express instance? Is that name consistent with what's configured in VWD?
http://aspadvice.com/blogs/name/arch...e-Project.aspx
Cheers,
Imar
|
|
November 24th, 2009, 05:14 PM
|
|
Authorized User
|
|
Join Date: Nov 2009
Posts: 15
Thanks: 0
Thanked 1 Time in 1 Post
|
|
Thank you. This is very weird. I entered SQLEXPRESS as the instance name and double clicked PlanetWrox.mdf and got the same error. So I went to Tools->Connect To Database and browsed to the PlanetWrox.mdf file and it connected. It added it to the project as PlanetWrox.mdf1. I still cannot connect to the original by double clicking, but can work with the one added as mdf1. Not sure what's going on, but it looks like I may at least have a workaround for now.
I am using a 64bit Win 7 computer. Not sure if that is a factor???
|
|
November 24th, 2009, 07:11 PM
|
|
Authorized User
|
|
Join Date: Nov 2009
Posts: 15
Thanks: 0
Thanked 1 Time in 1 Post
|
|
FYI in case anyone else runs into this:
After chasing this all day, I found this MS link:
http://support.microsoft.com/kb/957944
FIX: Error message when you connect to a 64-bit instance of SQL Server Express 2008 by using Visual Studio 2008 Service Pack 1 (SP1): "Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to function properly"
It says you have to obtain a hotfix from MS customer support or install a 32 bit version of SQL. The 64 bit version was installed as part of VWD so not sure yet how I will do this.
Here is a direct number of MS support 1-800-936-4900.
Last edited by glenng; November 24th, 2009 at 07:30 PM..
|
|
November 25th, 2009, 03:36 AM
|
|
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
You could also try this, as per the article you posted:
Quote:
|
To work around this problem, uninstall the 64-bit version of SQL Server Express 2008, and then install the 32-bit version of SQL Server Express 2008.
|
From the perspective of the Planet Wrox sample application, there isn't any benefit to run the 64 bit edition.
Imar
|
|
November 27th, 2009, 04:50 PM
|
|
Authorized User
|
|
Join Date: Nov 2009
Posts: 15
Thanks: 0
Thanked 1 Time in 1 Post
|
|
Thanks Imar. I tried that and continued to get errors. I uninstalled everything and started over, same thing. Finally, I reinstalled the default system, which is 64bit automatically, and applied the Hotfix when it was finally emailed to me. Like magic, all is fine now.
|
|
The Following User Says Thank You to glenng For This Useful Post:
|
Imar (November 28th, 2009)
|
|
November 28th, 2009, 05:39 AM
|
|
Wrox Author
|
|
Join Date: Jun 2003
Posts: 17,089
Thanks: 80
Thanked 1,576 Times in 1,552 Posts
|
|
Excellent, glad to hear it's working, and thanks for the follow up.
Cheers,
Imar
|
|
|
button below this post to show your appreciation!
