I hear you Carlos, I like tostep through some DNN code and modules to see how other developers do things.
Never know what I might pick up and learn... I have developed a few modules and have a site up live in DNN 3.5.x

No going through the throws of building everything in DNN 4.5.1 and NOT doing the upgrade but a whole new site and porting my modules over to DNN 4.5.1.

Thanks fo rthose thoughts though. You are right, really.

Anyway, as for the issue in this thread:

OK, this is embarassing...

I've been pulling my hair out and posting messages and ... turns out "authentication mode" in web.config was set to Windows.
Following various posts here, I changed that to Forms and ALL WORKED!

I have full access to everything appropriate to each account.

When I get around to it, I will try to post a few basic items to be sure to check when investigating similar errors...

Thanks ALL for your help!

Lindsay

Dregalia:

The database issue you are facing is quite common, specially among those with some SQL Server knowledge but not fully aware of the new SQL Server 2005 Express idiosyncrasies. You see, ASP.Net 2.0 and SQL Server 2005 Express make installing Web apps easier with the use of the App_Data directory. This architecture allows for XCopy rollout of databases, meaning that you do not need to create the database before-hand prior to running DNN the first time (you do need to install the SQL Server 2005 Express software by hand however). You don’t need to modify the Web.config connect string for the default install either (using the DB in App_Data). This kind of database configuration is also confusing because even though the site will work just fine, if you go to the SQL Server Management Studio Express tool you will not see the database. The tool will only see databases created in the old fashion way a la SQL Server 2000. Databases in the App_Data directory are part of what is called a “User Instance” of the database. They can be converted to a regular database and managed the usual way but then you have to take care of changing the Web.config connect string and deal with the SQL Server login and its DB rights.

So, if your database is in the “program files/mssql/3.0/data” directory, that means that you created it by hand and are not taking advantage of the new XCopy DB rollout feature. This also means that you need to take care of modifying the Web.config connect string (which will be different from your machine setup to the production server), and the creation of the SQL Server login account as well as its access rights to the DNN DB, Tables, and objects. This is where your problem is. You need to give the SQL Server login account write access to the DNN database. Same applies if you are using Windows authentication I believe (Integrated Security=True;).

I hope this helps.

Carlos

Carlos,

Half of my issues were from using 4.5.2 (the account login module issue). Now that I'm back on 4.5.1, I still can't login from another computer. This doesn't make sense, as I was able to do this before. What kind of troubleshooting can I do here? It's no longer just IE7- I've verified that this is happening on a 3rd computer with IE6.

Logging in on the main computer through either localhost/site or my_comp/site works.

I'm at wits end. Please help. Thanks.