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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN update killed site???DNN update killed site???
Previous
 
Next
New Post
11/22/2008 11:57 AM
 

I attempted to complete the DNN update a few nights ago and once the update completed, the site was not there, and I got a "Runtime Error page that has the text on it that I am adding here. I tried to opt out and undo the update, but it did not bring back the site. This is the message on the site;

  

Server Error in '/Skydiving/skyride' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

  My hosting is through Godaddy and they don't seem to know what the problem is. I have given them a week now to correct the problem and they have yet to do anything.  This is the URL for the site; http://1800skyrideripoff.com/Skydiving/skyride/ 

Does anyone have any ideas?

                 Thanks, Jeff...

 
New Post
11/22/2008 12:39 PM
 

First we need to determine what is the actual error. Please modify your web.config file as indicated to set customErrors mode="Off" and then revisit your site. Copy the entire error message especially the stack trace portion and paste it into the reply to this post. There is a slight (very slight) chance that making this modification (which will restart your website application) might correct the problem. If not in addition to posting the exact error . . .

please answer the following:

1. What was the DNN version from which you were upgrading?

2. What is the DNN version to which you attempted to upgrade?

3. Did you make a backup of your website files (especially the old web.config file) and the database before the upgrade?

4. Did you see any error messages during the upgrade?

5. What did you do to try to undo the update?

6. Do you have access to the site's MSSQL database (using SQL Server Management Studio, etc.) to take a look at the EventLog table, etc.?


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
11/22/2008 8:33 PM
 

This is what I got after changing the file to off.

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: Unrecognized element 'configuration'.

Source Error:

Line 89:     <compilation debug="true" strict="false">
Line 90:       <!-- Web.Config Configuration File -->
Line 91:       <configuration>
Line 92:         <system.web>
Line 93:           <customErrors mode="Off" />

Source File: d:\hosting\jumpdude1\Skydiving\skyride\web.config    Line: 91

Server Error in '/Skydiving/skyride' Application.

Configuration Error

 


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

The old version was 4.5.3 and I was going to the 4.7.0. I tried to back out of the upgrade, but got no luck. Godaddy offers a quick, one click upgrade, Juck click to upgrade, then click "OK" and it does the rest. I did not see any messages at the time of the upgrade. I did two other sites at the same time and had no problem. The people at Godaddy tell me that all the contant is still there, it just apears that the webconfig file is screwed up somehow.          

 

 
New Post
11/22/2008 9:15 PM
 

It appears that in making the change in the customErrors node of the web.config file you introduced a new error by adding in new <configuration> and <system.web> nodes. Please revert back to the previous version of web.config (just before you tried to change the customErrors mode) then locate the <customErrors> node and change ONLY the value of the mode attribute from either "On" or "RemoteOnly" to "Off". Do not make any other changes or additions to the web.config file.

Hopefully you will be able to revert back to the earlier web.config or otherwise correct the new error. You should then be able to see more information about the actual error which is keeping you site from working and post it here for review.

 


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
11/22/2008 9:37 PM
 

OK, I am certain that the Webconfig file is the problem, or at least I think I'm sure. I did a test by taking the file from one of my other sites and pasted it into the FTP for this site, it showed up as a DNN update for a couple of minutes then went to the other site just as if it was the site with the problem. I then repasted to original webconfig file back in place, but go the same message as originally in this post. Unfortunately, I do not have the original file. I did the change to off in ALL the areas on the file that offers the <customerrors> to "off" and got the message I posted here after the first change.

 I hope that gives you some idea of what I got here.

 Thanks, Jeff...

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN update killed site???DNN update killed site???


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