Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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...Testing an upgradeTesting an upgrade
Previous
 
Next
New Post
1/4/2011 10:53 PM
 
Doug Walden


Joined: 9/26/2006
Posts: 28
Error I have been struggling with upgrading my DNN installation. I am currently running 05.01.04(3). I have read that the best way to get to the latest is to go to versions...5.4.4...then5.5.0...then5.6.0.
So I used my local machine to do a test...got it to upgrade to 5.6.0. Now on to my production Site.

Quick note here...My local test site was only one portal running on Windows XP SP2 with MS SQL 2005. My production site has 4 active portals and a few inactive.

During the upgrade I ran into several errors ones that I was not able to diagnose on the hosters servers. So what I have now done is taken a copy of the web site and the database and put them on my local machine. I did a restore of the database to my local instance of my DNN database. I deleted the web files and folder in my DNN folder and took the zip file of the web site and extracted it into the DNN folder. Changed the web.config file to point to the database.

I was getting the error that it could not open the web page. Have got by that error by updating the portalAlias table to have "/ServerName/DNN" Where DNN is the Alias in IIS. I did this due to finding another forum entry indicating that the server name should be there. Interesting note: the original site that I was testing with had "localhost/dnn" and was working.

Anyway...Now that "/ServerName/DNN" is in there I now get DNN up on the Default.aspx page but, it now says DotNetNuke error Windows XP and has a Return to Site Button, which just puts me back on the same page with the same error.

Any Ideas?

Thanks, Doug
 
New Post
1/5/2011 10:13 AM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
You are seeing one of the issues resulting from changes to the UrlRewriteModule made in DNN 5.06.00. I am still not certain what particular configurations result in its appearance. There are several lengthy threads in the Installing and Upgrading DotNetNuke forums trying to resolve the causes of this issue and others related to the addition of the automatic portal alias mapping feature in DNN 5.06.00.

Some possible causes (note "possible"):
1. Running under an ASP.Net 4.0 application pool with clasic rather than integrated pipeline mode set in IIS.
2. Portal alias has a "/" as its last character.
3. Having mapped in IIS configuration non-aspx file extensions to be processed by the ASP.Net ISAPI handlers.
4. Multi-portal installation.

Several bug fixes and I believe an option to disable automatic portal alias mapping will be included in the forthcoming DotNetNuke version 05.06.01.

Although I have not been reliably able to replicate this issue on a local host install, I have not and cannot recommend upgrading live sites to 5.06.00 at this time. I would upgrade only to 5.05.01 now then when 5.06.01 is released test upgrading from 5.05.01.
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/5/2011 12:24 PM
 
Doug Walden


Joined: 9/26/2006
Posts: 28
Bill,

Thanks this is good information. Maybe I miss led you to believe that the restore of my production site to my local was at the 5.6.0 version. That restore is to the 5.1.4 version. I am restoring that to my local so that I can test the upgrade process (since it did not work at all on the production site) I thought it might have to do with data and or purchased modules that are installed.

So I thought I could better diagnose the issue on my local machine.

With this new information...does that change the solution at all?

Thank you, Doug
 
New Post
1/5/2011 2:36 PM
 
William Severance


www.wesnetdesigns.com
Joined: 2/18/2005
Posts: 3253
Sorry Doug . . . I had mis-read your original post and thought that after you migrated the site back to localhost and got past the portal alias issue you had made the upgrade to 5.06.00 locally at which time the error appeared.

In re-reading your original post now I did notice that you had added the portal alias /ServerName/DNN to the PortalAlias table. The problem may be that you have a leading forward slash in the alias. I've always used either localhost/DNN or ServerName/DNN where DNN is the IIS alias. Also, keep in mind that after changing or adding a portal alias in PortalAlias table you must force an IIS restart or application restart (re-saving web.config usually works) as the PortalAlias table is very heavily cached.

Also, am I correct that when you restored the database to local SQL Server you created a new user in both SQL Server and the database's Security->Users and also updated both database connection strings in web.config to match the new server and user/password credentials? As a test are you able to connect to the database using SQL Server Management Studio or other similar tool with SQL Authentication and those same credentials?
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/5/2011 3:08 PM
 
Doug Walden


Joined: 9/26/2006
Posts: 28
Thanks Bill.

If I change the Alias to not have the slash "ServerName/DNN" or use "localhost/dnn" I get the error indicating that it could not open the web page. Not sure why, because the initial install to my local machine had the "localhost/dnn" entry and worked. But this does tell me that my connection string is working properly because the change in the database gives a different result. I will try again and make sure I restart IIS...Thought I had but not sure.

Will get back with the results.

Any other help will be most welcome. Or if you have any better way of testing the migration that woud be great as well.

~ Doug
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Testing an upgradeTesting an upgrade


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