What errors do you get?

If creating a blank database and restoring over it works, do it!

I suspect that I am doing something wrong. I cannot seem to create a new db...permission issues. Anyway, I don't want to do anything different that what is normal. I am thinking that I should try to do it exactly as Lee suggests...so I can figure out how to undo it.

So, with that as a backdrop. I have three dbs on my system. On is SQLExpress and is running DNN5.0_test for 3rd party module testing. That is completely clean...no modifications, yet. I want my production site to run locally so I can upgrade it. Should I be able to do this exactly as the video says when running Vista? And, already having ONE DNN install working?

Either this machine has issues, or I have them. I REPEATED all the steps EXACTLY like I did several times earlier. The only thing different is that I restarted my box.

The restoration was completed EXACTLY as it was advertised in the tutorial! So, the database issue is no longer an issue. ON to the next thingy.

Thank you.

Okay, I reviewed the entire set of tutorials again. I am seeing things in vista that are different than Lee's OS, I think. In Vista, the IIS configuration looks different. I never see the choice to "tick Execute." And, there is NO properties when I right click the virtual directory. I muttered through, guessing as I went along. I also did not get a choice to add ASP to the permissions... Since I got the DNN 5.0 working using Network System, I choose that. Here's the results:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:


Line 60:
Line 61: <!-- Ensure validationkey is not set to AutoGenerate,IsolateApps so it correctly supports webfarms -->
Line 62:
Line 63: <!-- HttpModules for Common Functionality -->
Line 64:


Source File: C:\DotNetNuke Sites\dnn_NKY_471\web.config Line: 62



Show Additional Configuration Errors:


It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\DotNetNuke Sites\dnn_NKY_471\web.config line 121)
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\DotNetNuke Sites\dnn_NKY_471\web.config line 179)
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. (C:\DotNetNuke Sites\dnn_NKY_471\web.config line 180)
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

Of course, I see this line, "This error can be caused by a virtual directory not being configured as an application in IIS." But, I have NO idea how to remedy the matter.

Make sure that you viewed How to install DotNetNuke to Vista

I have viewed that tutorial and was successful in installing DNN 5.0. As I slept, I realized the IIS problems I was seeing start with the fact that I created a Virtual Server....as the "Backing up hosted DNN to localhost" says I should; BUT, when I configured IIS for the DNN 5.0 installation, I configured IIS as an APPLICATION (rather than a virtual server). I will try the "application" route and see what happens.

"Progress over perfection," means I have reconfigured the localhost as an application instead of a virtual server and I am no longer seeing the error reported above. Now, I see "This site is currently Unavailable Please check back later." Since I have 4 portal alias' (3 parent and 1 child), I am wondering if I am required to install all of those in order to get live site up on my localhost (I thought I could get the main one up and then add the remaining alias'). I will add those other alias(es) and see what happens.

More progress? I now see: "Exception Details: System.Data.SqlClient.SqlException: Login failed for user 'NorthernKYian'. The user is not associated with a trusted SQL Server connection."

This seems to imply I did something wrong in setting up my connection string from SQL2005 to SQLExpress. The username and password match the permissions in db.

This parameter in my web.config is suspect: "providerName="System.Data.SqlClient" That follows the userID and Password in the connection string. It was part of the string in 2005 and Lee does not specifically indicate it should be cut, so I left it (I thought I saw it there).

Any guidance?

I cut the parameter and I am back to "This site is currently Unavailable
Please check back later." The only other thing that is questionable to me is that child portal. In trying to "add application" in IIS7, I could not add a "/" for that child. I will have to look at how I named that alias in my live site.

No, you do not want to remove providerName="System.Data.SqlClient" from the connection string.

The error message indicates that you do not have a "trusted connection" to the database.  Google for that phrase.

Yes, I do understand. I reviewed both series of tutorials again. I replaced the "providerName" line and tried it again. My first browse returns the Under Construction screen, but an additional attempt returns the TRUST issue:

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

I went through the security options and I have the "user" configured in SQLExpress and the password associated with the user and the login added to the db. I have no idea what I am missing.

I don't have Visual Studio express, would that help me troubleshoot the connection issue? Would it guide me?

Okay, this seems like a problem to me:

"Windows Authentication" is the selected Authentication Method. Since I am very unskilled in DBs, I am guessing that is wrong....because I am passing an ID and password. It is not apparent to me, how to change that method. Can you guide me? BTW...at some point in the restore process, I think I should have stumbled upon this option.

In an effort to find an example to work from, I attempted to look at my DNN 5.0 file. It is not working any longer.

Dang!

Progress? Followed the Microsoft instructions for allowing my server to use mixed mode authentication. I have a new (non specific) error:

DotNetNuke Error: - Version 04.08.04

An error has occurred.
An error has occurred.

Double-Dang!

In the URL bar, I see this: "Default.aspx?tabid=36&error=Object+reference+not+set+to+an+instance+of+an+object.&content=0"

What the heck?

Do you have SQL Server Management Studio Express?  Can you use it to connect to your database?

I have using SQL Server Management Studio Express to do EVERYTHING with the db...including restore it, add user, and add login to the database.

The connection string in web.config should use the same parameters that you use to connect with SSMSE.  Server name, database name, userid, password.

If you are using integrated security for SSMSE, see if works in DotNetNuke.

Note that there are two forms of the connection string: one for SQL Server and one for SQL Server Express.

Also note that there are two places where you specify the connection string in web.config.


If you've already done all of that, I'm stumped! 

Okay:

If you are using integrated security for SSMSE, see if works in DotNetNuke.
<<<>>>>

Note that there are two forms of the connection string: one for SQL Server and one for SQL Server Express.

<<<>>

Also note that there are two places where you specify the connection string in web.config.

<<<


<!-- Connection String for SQL Server 2005 Express -->
providerName="System.Data.SqlClient"/>
<!-- Connection String for SQL Server 2000/2005 -->
<!--add
name="SiteSqlServer"
connectionString="Server=*****.com;Database=*****;uid=*****;pwd=*****;"
providerName="System.Data.SqlClient" />
-->


<!-- Connection String for SQL Server 2005 Express - kept for backwards compatability - legacy modules -->

<!-- Connection String for SQL Server 2000/2005 - kept for backwards compatability - legacy modules

-->