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 ...Configure my web.config to allow install errors to showConfigure my web.config to allow install errors to show
Previous
 
Next
New Post
1/16/2012 9:49 PM
Accepted Answer 

Generally only the yellow screen unhandled application errors can be seen in more detail by turning off customErrors in web.config. The generic error "An error has occurred" is one thst is generated by the DNN framework. Here are a few ways to start troubleshooting this:

1. Did you note any errors being reported during the upgrade? If so, those errors may have been logged in the corresponding xx.xx.xx.log.resources files found in the site's Providers/DataProviders/SqlDataProvider folder.

2. DNN 6 introduced a new logging mechanism (log4net). If you upgraded to 6.x any errors logged to this system should be found in files named yyyy.mm.dd.log.resources (where yyyy is the year, mm the month and dd the day) found in the site folder Portals/_default/Logs/.

in either case the log files are simply text files which may be opened with Notepad, etc.

3. Unfortunately you may need to look through the EventLog table in the site's MS SQL Server database for additional clues. Most of the error details are found in the LogProperties column as an Xml serialized string. It's hard to read - I've got to finish working on my WPF program to extract and format this information similarly to what is shown in the DNN Admin-->Event Viewer - but one brute force way is to copy the contents of one row of this column to the clipboard and paste it into a notepad text file which you save with an xml extension. You can then double click on this file to open it in your web browser to view properly formatted xml.


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
1/16/2012 10:07 PM
 

William,

Thanks for taking the time to respond to my message... looks like some good tips, I'll dig into that very soon!

Patrick

 
New Post
1/19/2012 12:45 AM
 

William,

Thanks to your tips I think I finally have my fist solid lead as to how to solve my update problem. Here's what I did:

Upgraded to 6.1.2, and got no errors on the install, but the site gave me the same default error when I tried to access the site. The Portals/_default/Logs/ folder did not contain a current log, so I looked in the EventLog table in the site's MS SQL Server database. There I found numerous PageLoad Exception errors. There seemed to be one for every time a page on my site which contained the HTML/Text module tried to load. The pertinent info is:

'~/Telerik.Web.UI.WebResource.axd' is missing in web.config. RadStyleSheetManager requires a HttpHandler registration in web.config. Please, use the control Smart Tag to add the handler automatically"

Can you tell me how I can do that, and perhaps suggest why that didn't happen automatically?

Thanks again so very much for making these suggestions.!

Patrick


 
New Post
1/19/2012 11:02 PM
 

I would like to send this post to follow up and conclude the issue which prompted me to post in the first place, namely the inability to locate a log of errors which could help me to diagnose a nagging install problem. Thanks to William Severance for pointing me in the right direction!

I had known about the Log Viewer on my portal, but when the portal would not launch, I did not know how to see the errors. I had initially believed, that if I turned off customErrors in my web.cong file that they would show on the page at the time they were generated. This was reinforced by others on this forum who told me that that would be the case…

It looks like, however, that this is not true if you host your site with a provider… so I had been looking for a solution that was not going to work for me.

With Bill’s help I learned that I should go instead to the EventLog table in my site's MS SQL Server database. Here I hit pay dirt. I used a simple SQL statement to select the last 20 records:

SELECT TOP 20 [LogTypeKey]

      ,[LogUserName]

      ,[LogPortalID]

      ,[LogCreateDate]

      ,[LogProperties]

FROM [Your_database].[dbo].[EventLog]

ORDER BY [LogCreateDate] DESC

Then, follow Bill instructions “copy the contents of one row of this column to the clipboard and paste it into a notepad text file which you save with an xml extension. You can then double click on this file to open it in your web browser to view properly formatted xml."

Using this method I was able to diagnose the problem, and finally get my site started.

Thanks to Bill and all others on this forum who give freely of their time and expertise to help novices like myself!

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Configure my web.config to allow install errors to showConfigure my web.config to allow install errors to show


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