Ok so after getting SqlExpress up and running again and then going in and attempting to switch it over to SqlServer2005 I am getting:

CREATE DATABASE permission denied in database 'master'.
An attempt to attach an auto-named database for file C:\Local Source Code\WroxUnited\App_Data\aspnetdb.mdf failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.

Which makes sence becuase aspnetdb is the default name for the roles database that is created whenusing aspnet_regsql.exe. So this program can't be run on a server that has run that utility. Maybe if wrox wrote the program to use a differnt db for roles then it could work?

At this point in time I think the program just can't run on sql server 2005. I was using this as a learning experience and I've leardned a lot but it took too much time. If wrox could figure this out it would have saved me a ton of time and made the first impression of the book positive.

(the aspnet_sqlreg.exe link again is: http://msdn.microsoft.com/asp.net/de...aspnet_sql.asp)

Hi gperrego,

It sounds to me like you're on the right track to get it working. You might try deleting the existing aspnetdb.mdf, that would get rid of the error message you're getting telling you that it already exists. If you want to try that, here is how:

I believe SQLExpress does not come with a graphical interface, so you will have to use the command line utility, sqlcmd.

Go to a command prompt.
Type this: sqlcmd -S .\SQLExpress
You should get a prompt that looks like this: 1>
Type this: exec sp_databases
Press enter and then type : go
Press enter.
This will list all the databases currently attached to your sql express instance.
If you see the aspnetdb in the list, then delete it like this:
1>DROP DATABASE aspnetdb
2>GO

When you are done, type exit and press enter. The database should be deleted.

Hope this helps. If it doesn't, post back.

Mike

Hi Everyone -

I've had the same problem of getting the site to work. I think I have joy though... the site seems to be working! :) I had the same error message (error: 26 - Error Locating Server/Instance Specified) posted here and elsewhere.

Here is my config:
XP Home
VS2005
SQLServer Enterprise 2005 (upgrade from SqlExpress: NOTE THIS IS IMPORTANT!)

Anyway I had trouble getting the site to run and I followed Chris' advice:
1. Add the [machine\ASPNET] and [NT AUTHORITY\NETWORK SERVICE] as logins
2. Attach the database (wroxunited.mdf), makeing ASPNET the db_owner
3. Add [machine\ASPNET] and [NT AUTHORITY\NETWORK SERVICE] as database users
4 Change the connection strings in web.config. That should be all for the WroxUnited database - then there's the providers, which can either be added to WroxUnited db or to a separate one.
5. Run aspnet_regsql (in the framework directory), to add the user/roles/etc tables/procs to he appropriate datbase
6. Add provider sections in web.config, for <membership>, <roles>, <profile>, setting the default provider for each to the new provider added. These providers should point at the ConnectionString for the database (so either WroxUnited or a new conn str if using another database).

I had no problem adding NT Authority\Network Service. The trick for adding this user is pretend that "Network Service" is part of the local machine domain, and don't use "NT Authority" as a domain.

I also had problems with steps 5 and 6. After much consternation and research on MSDN, I discovered some legacy code from SQL Express that wanted to link ASP2.0 to a non-existent SQL Express database in my machine.config file! Argh! :(

Here is a snippet from my modified machine.config:

  <connectionStrings>

    <add name="LocalSqlServer" connectionString="data source=tlaloc2;Integrated Security=SSPI;Initial Catalog=ASPNET2.0" providerName="System.Data.SqlClient" />
  </connectionStrings>

So basically I modified the connection string to reflect the database I set with aspnet_regsql utility.

Hope this helps!

Luis

I'm still having problems.
I added the logins [machine\ASPNET] and [NT AUTHORITY\NETWORK SERVICE] to the 2005 server.
I attached the wroxunited.mdf database as WROXUNITED with [machine/ASPNET] as db owner.
There were several database users after the wroxunited database was attached, including the following:
user [NT AUTHORITY\NETWORK SERVICE] with [NT AUTHORITY\NETWORK SERVICE] as the login and owning schema [NT AUTHORITY\NETWORK SERVICE]
user ASPNET with no login name specified and owning no schema. When looking at the properties for ASPNET user I must cancel not click OK as OK gives the error that a login name must be entered.

I can delete user ASPNET and try to add [machine\ASPNET] but I cannot use login name [machine\ASPNET] as that is the login for dbo.

When I run WroxUnited from IIS 5.1 I get Server Error in '/WroxUnited' Application. Login failed for user '(null'). Reason: Not associated with a trusted SQL Server.

I did modify the connection string in web.config but I don't know if it is correct.

Any ideas?

Hi there,

The error message you get seems to suggest your connection string does not use Integrated Security, but SQL Server security instead. Take a look at this site: http://www.connectionstrings.com/

Then expand SQL Server 2005 and then SqlConnection (.NET). Next, make sure your connection string looks like the one listed under "Trusted Connection", and not like the one listed under "Standard Security".

HtH,

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Thanks, Imar.
I made a couple of changes to the connection string, which now looks like this:

    <connectionStrings>
        <remove name="LocalSqlServer"/>
        <add name="LocalSqlServer"
      connectionString="Data Source=server\instance;
            Initial Catalog=WROXUNITED
            Integrated Security=SSPI;"
      providerName="System.Data.SqlClient" />
    </connectionStrings>

The error I now get is:

Login failed for user ''. Reason: The user is not associated with a trusted SQL Server connection.

I believe the problem is with the database user ASPNET not being associated with a login and/or not being able to add user [machine\ASPNET]

Thanks for the info, BettyB.

Usually you get this error when you try to connect to a SQL Server that only allows Windows Authentication, but you use SQL Authentication in the connection string.

Is server\instance in your connection string, or was that just an example?

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

server\instance is just an example. The rest of the connection string is copied from web.config file. I have an instance of SQL Server 2Ks and a named instance of 2005 on the machine.

BettyB.
www.flamingo-code.com

Hi BettyB,

Are you sure you configured the right application and the right web.config? The error indicates a connection with SQL Server authentication.

Have you seen this blog post before? http://weblogs.asp.net/scottgu/archi...25/423703.aspx

It may not directly fix your problems, but it may give you some insight in configuring your applications and SQL Server.

It is very possible to connect to a SQL Server 2005 database from any .NET web app. The reason why the Express edition is used so often because a) it's free, b) it's pretty easy to use and configure. Configuring a true SQL Server database can be a bit more tricky, and also requires a bit more knowledge about the network and your machines.

If I find the time over the next days / week, I'll try to write an article about it on my site....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Hi Imar,

I'm not sure what your first question means. Most of the configuration that I am having problems with occurs in SQL Server. I am using SSMS. The problems I have are with the server logins, WroxUnited database owner and database users. I am not aware of anything at this point that specifies the application I am going to use. There is only one web.config per application AFAIK. The Wrox United application is where I have changed the connection string in the web.config. When I logon to my server in SSMS I logon with Windows authentication. Do I need to change my connection string? Using info from ConnectionStrings.com I tried to set up the connection string as SqlConnect (.NET) | Trusted Connection.

I understand that 'Configuring a true SQL Server database can be a bit more tricky' but I doubt that using SQL Server Express to work my way thru the beginning ASP.NET book will give me the information to enable me to use true SQL Server 2005. Of course, I may be wrong.

I have looked at the blog post but didn't think it answered any of the login|db owner|db user conflicts that I am having. I will go through it again.

Thanks

--
BettyB.
www.flamingo-code.com