New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Restoring and Connecting Locally to SQL ExpressRestoring and Connecting Locally to SQL Express
New Post
6/13/2012 2:10 PM

I am having some trouble connecting to my database in SQL 2008 R2 Express to activate a site on my local machine. I have done this several times in the past, but I am having issues on this new computer.

The files have been downloaded, the database backed up, downloaded, then restored in SQL 2008 R2 Express with the login user added. However, I am not able to restore the website locally.

I was able to create a new instance of DNN, but I cannot connect the older instance to the database that I have restored. I did add the portal alias "localhost" to the database. Gave DefaultAppPool full permissions to the folder. Changed my web.config file to...

<add name="SiteSqlServer" connectionString="Data Source=.\SQLEXPRESS;Initial Catalog=mydatabase;User ID=myuser;Password=mypassword" providerName="System.Data.SqlClient" />

It seems as though the IIS is not configured correctly. The DefaultAppPool has been selected in IIS 7.5.

Then I got a machine key error.  I have tried with WebMatrix and without it. Here is the error below.  

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 99: </system.webServer>Line 100: <system.web>Line 101: <machineKey validationKey="F96644F22F506793CDA1101F8D81B887F338825B" decryptionKey="9BA9D4FC3F355F3EFD902F17B2B91355EF0094AA48FE4715" decryption="3DES" validation="SHA1" />Line 102: <!-- HttpModules for Common Functionality -->Line 103: <httpModules>

Source File: C:\inetpub\wwwroot\maranata\web.config    Line: 101

Version Information: Microsoft .NET Framework Version:2.0.50727.5456; ASP.NET Version:2.0.50727.5456


Any help would be appreciated!


New Post
6/13/2012 7:04 PM
please make sure that your IIS website points to the DNN root folder and that there is NO web.config file in any sub directory

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
New Post
6/14/2012 7:34 AM
Like Sebastion said, either IIS doesn't have an entry for the website or there are multiple web.config files within DNN and that's causing the issue. Check both and let us know if it works.

New Post
6/14/2012 11:42 AM
Thanks Sebastion and Mark for the help. I will file this so as not to make the same mistake again. I had tried this dozens of times and though I ran into the machinekey problem once or twice, that was not my biggest problem. A simple rechecking (with your help) got me past that issue.

My problem was that I constantly kept getting the install wizard, or an index.html file though default.aspx was set. I tried different browsers and at first it gave me an error. I restarted the browser and IIS and all of a sudden the site appeared on a different browser. Come to find out I had the right connection strings and everything, but I had not deleted the cache in my browser. Everything else seemed to be set correctly. Though I had read many posts, nothing that I read mentioned the cache which was probably there from an initial trial run with incorrect settings. Though I deleted folders, database, and everything, the portal alias kept pulling up the cache.

Well, I am glad that is over! Maybe this post will help someone else.
HomeHomeDevelopment and...Development and...SQL and SQL Ser...SQL and SQL Ser...Restoring and Connecting Locally to SQL ExpressRestoring and Connecting Locally to SQL Express

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out