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...Upgrading DNN P...Upgrading DNN P...Upgrade from 5.2.2 to 5.5.1 finally worked, but now site is "error"Upgrade from 5.2.2 to 5.5.1 finally worked, but now site is "error"
Previous
 
Next
New Post
1/9/2011 11:45 PM
 
After several weeks of trying to get a move to GoDaddy to work directly, I decided to upgrade my existing site on WebHost4Life from 5.2.2 to 5.5.1 before moving to GoDaddy's environment. Easier said than done, primarily because of the Telerik crap changes required that are not in the upgrade setups. Why have them then?
Finally got the site to hit the upgrade scripts and everything was successful. When going to the only portal on this site (www.t-netters.org) I now get nothing but an error (and the DNN framework loads, so I can't even get the regular error pages.) I can tell that it is of the "object not set to instance" variety, but I cannot see the entire error (so I can't debug and fix it.)

Any suggestions on how to see the error or what might have caused it? The only 3rd party tools installed on this site are FatGeorge, XMOD, and Business Directory for XMOD.

Any help would be appreciated.

Rob Roberts
 
New Post
1/10/2011 9:10 AM
 
1) Modify the installation's web.config file as follows:

a. Search for the node <customErrors mode= . . . />
b. Change the value for the mode attribute to "Off" (note that this is case-sensitive so "O" must be capitalized and "ff" in lower case).
c. Save change to web.config and re-upload the modified file to your site's installation folder.
d. Revisit the site in your browser. You may now be able to see a detailed ASP.Net error page rather than the custom error page.

2) Try to access the installation's database remotely using either a web-based database management tool that may be provided by WebHost4Life or MS SQL Server Management Studio. If you are able to access the database, open the EventLog table and examine the LogProperties column for related error information that may give us a clue to what is preventing the site from opening.

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/10/2011 11:16 AM
 
Thanks, William.
I had tried the web.config setup, but that didn't help. I had also tried looking at the log, but the field LogProperties truncates at an enter.
I found the method for looking at all the LogProperties, which some here may not know (so I'll post.)
In SQLQueryAnalyzer (if connecting directly from the tool to the database) change the Results to Text instead of a Grid. You must also change the maximum field response size to 8000 (Tools>Options>Query Results>SqlServer>Results to Text and change max number of characters....)

On another note, this "upgrade" package bombed with Telerik--I had to manually update the web.config settings for the new version. It also wiped out all my subdirectories with XMOD and other modules in place. It has been more than a nightmare to upgrade. What happened to the good DNN? I followed the instructions for backing up, copying web.config to a safe place, and unzipping the upgrade files over the top of the existing files with "OVERWRITE" turned on. Doing this apparently wipes out the existing directories, too, eliminating all the config that I had previously done with XMOD and Business Directory. Never again.

I've already started shifting some of my sites to Drupal.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade from 5.2.2 to 5.5.1 finally worked, but now site is "error"Upgrade from 5.2.2 to 5.5.1 finally worked, but now site is "error"


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