I'm teaching myself, using a book called "Beginning.ASP.NET.2.0" (WROX-2005). In chapter 4, we're doing the login control. After adding the control to the page, we are instructed to Administer the Website. When I click that, an instance of IE comes up. I am then told to click "Security". This is where it doesn't do what the book says it will.

When I click Security, after a long, long wait, I get this:

"There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.
The following message may help in diagnosing the problem: Unable to connect to SQL Server database."

I then click the "Select Data Store" button at the bottom of the page. That brings me this message:

--------------

Use this page to configure how Web site management data such as membership is stored. You can use a single provider for all the management data for your site or you can specify a different provider for each feature.

Your application is currently configured to use the provider: AspNetSqlProvider

Select a single provider for all site management data
Select a different provider for each feature (advanced)

=======

Obviously, I select the top link, to select a single provider. I get a page with a single radio button and a link to test the connection. I click "Test" and after a wait, I get this message:

----------

Could not establish a connection to the database.
If you have not yet created the SQL Server database, exit the Web Site Administration tool, use the aspnet_regsql command-line utility to create and configure the database, and then return to this tool to set the provider.

--------

I'm not sure what to do at this point. I followed instructions to the letter. The term "aspnet_regsql" is not mentioned in the book.

Finally, I found this old thread on the Wrox forum:

http://p2p.wrox.com/topic.asp?TOPIC_ID=41864

However, step (c) and (d) have stopped me cold. I don't have the Configuration Manager that it mentions (I am using SQL Server 2005 Standard).


thanks in advance

Hi there, That is the root cause of the problem.

ASP.NET - by default - assumes you have a local SQL Server called (local)\SqlExpress. The Standard edition installs itself as (local). Then, when ASP.NET tries to access or create the required database, it cannot find SQL Server which results in the problems you listed

Two ways to solve the problem:

1. Install SQL Server 2005 Express (www.microsoft.com/sql/express)

2. Read these articles:

http://weblogs.asp.net/scottgu/archi...25/423703.aspx
http://imar.spaanjaars.com/QuickDocId.aspx?quickdoc=395

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.

The instructions in the first article did the trick. Thanks very much!

You're welcome.

Cheers,

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of Beginning ASP.NET 3.5 : in C# and VB, ASP.NET 2.0 Instant Results and Dreamweaver MX 2004
Want to be my colleague? Then check out this post.