Chapter 16

Harpist · December 19th, 2014, 05:23 PM

Just so you know, I wound up doing a fresh install of windows and of VS2013. I got to a point where I was having issues where sometimes the database would connect to SQL server 2008 and sometimes 2012. 2012 worked, 2008 didn't. I figure I would remove the problem by having only one server.

I wanted to practice using the login controls from Chap 16, so I created a new project, dragged the controls onto the page. Ran the page and I get:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Now if I use the site template (not the empty one) it makes a database just fine, so I can't figure out what setting I need to change to make this work for me.

Before I reinstalled everything, I had it working in both 2010 and 2013. With the new installs, not so much.

Imar · December 19th, 2014, 06:09 PM

Maybe you no longer have a SQL instance called .\SqlExpress? You can set the default instance that VS targets under Tools | Options | Database Tools | Data Connections.

Hope this helps,

Imar

Harpist · December 19th, 2014, 08:52 PM

my database is (localDB)\v11.0.

HOw to I create a server named .SQLExpress?

Harpist · December 20th, 2014, 07:37 AM

Quote:

Originally Posted by Imar

Maybe you no longer have a SQL instance called .\SqlExpress? You can set the default instance that VS targets under Tools | Options | Database Tools | Data Connections.

Hope this helps,

Imar

This turned out to be the right case. Setting the default instance did not work. What finally worked for me was:

<remove name ="LocalSqlServer"/>
<add name="LocalSqlServer" connectionString="data source=(LocalDB)\v11.0;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspn etdb.mdf" providerName="System.Data.SqlClient" />

in the web.config file. After what you said, I did a ton of searching on line and eventually found what I needed right in the book in the same chapter. Between what I learned online and what you provided in the book, I was able to replace the connection string used by membership database.

Now I just have to figure out why I don't have SQLEXPRESS installed or how to install it in case anything else uses it by default. Any insight for that?

The Harpist.

Imar · December 21st, 2014, 11:26 AM

Hi there,

>> Now I just have to figure out why I don't have SQLEXPRESS installed or how to install it in case anything else uses it by default. Any insight for that?

Appendix B has details on installing Management Studio for SQL Server Express. Alternatively, go here: http://msdn.microsoft.com/en-us/eval.../dn434042.aspx or search on Google for "install SQL Server Express"

You could also install LocalDB. It should have been installed with Visual Studio but maybe you uninstalled it? This link shows some articles that'll help you out installing it: https://www.google.nl/?gfe_rd=cr&ei=...Server+localdb

Cheers,

Imar

Harpist · December 21st, 2014, 02:27 PM

localDB is what I'm using now. I'm mostly concerned if I come across something else that defaults to .\SQLEXPRESS.

I also wanted to say thank you very much. Your book is well written for teaching beginners .NET. I have found it extremely helpful in developing skills. And you have been incredible helpful with the troubles I have had.

I have just purchased your new book for 4.51 and I plan to go through that when it comes, hopefully tomorrow.

Imar · December 21st, 2014, 03:34 PM

LocalDB and SqlExpress are functionally equivalent for a large part. LocalDB is meant for development, while SqlExpress is designed for small production scenarios (although i can be used for development as well).

Quote:

I also wanted to say thank you very much. Your book is well written for teaching beginners .NET. I have found it extremely helpful in developing skills.

Good to hear! You're very welcome!

Imar