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 to 5.06 - Hostname Nolonger RedirectsUpgrade to 5.06 - Hostname Nolonger Redirects
Previous
 
Next
New Post
11/19/2010 9:45 AM
 
Can you revert upgrade, set "UsePortNumber" and upgrade website after?

Papayas DnnAutoUpgrade - automatic DotNetNuke upgrade without any problems!
www.papayasdnn.com
 
New Post
11/19/2010 11:02 AM
 
Friends, I am having the same problem
 
New Post
11/25/2010 5:03 AM
 
We have the same problem, portial allias table seems fine, root url gives an error, but no exception in de eventlog. subdomains and /default.aspx seems to work fine.
 
New Post
11/25/2010 5:40 PM
 
I've tried this and sadly no joy.

I've also tried another web site and that hasn't worked either.

I'll wait until a future version contains a fix for the portal issues and try then.

Thanks,

James
 
New Post
11/26/2010 11:45 AM
 
I'm experiencing the same problem with my Sites since running the 5.6.0 Upgrade. I Posted this in another Thread, maybe it will help some of you temporarily.

There is definately a problem with the 5.6.0 Upgrade. I attempted to Upgrade a number of my 5.5.1 Sites that are Hosted on a Dedicated Server at PowerDNN and I had problems with every one of them.

I had the same problem with the Site not loading correctly unless you clicked on the "Return to Site" botton which essentially adds the Default.aspx ending to the URL.

I figured out the by switching the Sites from ASP.NET 4.0 back to ASP.NET 2.0 under IIS and then removing this text (requestValidationMode="2.0") from one line in the Web.Config (I get a New Error Message if I dont' remove that text) I could get my Site to load normally. The only problem is that now I've got Modules that require ASP.NET 4.0 that are loaded on a few of the Sites that will not work correctly. Someone needs to fix this problem ASAP.

P.S. If I switch the Sites back to ASP.NET 4.0 they become broken again. I played around with this for a couple hours to nail down exactly what was causing this problem.


 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade to 5.06 - Hostname Nolonger RedirectsUpgrade to 5.06 - Hostname Nolonger Redirects


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