Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation Error - web.configInstallation Error - web.config
Previous
 
Next
New Post
3/22/2006 4:34 PM
 

I am getting the same error. I changed the tag to <CustomErrors mode="off"/>, and removed the other CustomErrors tag (there are two and this could be your problem) and am still gettting the same error. The CustomErrors tag does not seem to be getting read. I am using Godaddy also, and they gave me absolute zero help and seem to be promising that that is all I will ever get even though I just used the 'install' link on their site to install DotNetNuke which is one of their three value-added applications.

I am going to try to track this down in the code, but would prefer any help.

The sites are http://www.TestTheFullertonian.com (Godaddy)

and http://www.BackAlleyBar.com (1&1)

Yes, I am getting the same error from two diferrent providers. I have it all working wonderfully on a LAN but that is not visible from the internet. I have checked the web.config files about 15 times.

 
New Post
3/23/2006 7:20 AM
 
I had a similar problem whilst trying to solve my installation issues (as yet unsolved) but the web.config CustomErrors="Off" problem is now solved: I removed the web.config completely and then surfed into my application... which gives an error ... then I uploaded the new web.config. After that I get my asp errors.

Apparantly sometimes the web.config file gets cached.
 
New Post
12/19/2006 3:53 PM
 

I have read through the posts and searched for possible solutions to the Application Error and the custom errors page showing up.  I had installed several months ago to play around with DNN.  I had everything working and built some really nice sites, but then got busy and abandoned it for a while.  When I came back to take a look at things, I got the Server Error issue.  I knew I hadn't changed anything, so I looked through the settings on each of the sites.  I noticed that the tab for ASP.NET had no version selected.  When I selected version 2.0 (something, something), it gave me the hourglass, then back to the properties page.  When I refreshed my browser, the site came up.  I have done this for another site as well.  What I'm thinking is an incremental patch or change from Microsoft had made the ASP.NET bail.  This apparently corrects the issue.  Good Luck, and happy DNN'ing!

Kevin

 
New Post
1/24/2007 8:46 PM
 

I think the error everyone was getting was to turn the CustomErrors off. And when they turn the CustomErrors off in the web config they get a message to turn the CustomErrors off. And then when they double-check the setting they see that the CustomErrors="off". That is what makes it frustrating. Then when you tell people they say, 'Oh yeah, just set the CustomErrors="off" then you will see a lot more information.

 

Anyway this was happening to me and I checked the setting in the file so many times using so many methods that I thought I might go blind. What I discovered is that there was a web.config upstream from the virtual directory. For instance the Default Web Site was in C:\Inetpub\wwwroot and my dotnetnuke installation was in C:\Inetpub\wwwroot\DotNetNuke. The web.config I was editing was in C:\Inetpub\wwwroot\DotNetNuke but there was another web.config in C:\Inetpub\wwwroot which I had put there as a backup. IIS was reading that one and ignoring the one that I was editing. It is a process that I still don't fully understand. Or at least it appeared that way to me because when I removed it everything just started working.

 

I put this in here just for posterity sake. I swore that if I ever fixed this problem I would document it on this site. I hope this helps someone because that would mean I was not the only person dumb enough to put a backup in the upstream directory.

If you have any information on why IIS works this way or that this is not the actual problem or something that I am missing please post it and I will be grateful.

 

Thanks.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installation Error - web.configInstallation Error - web.config


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