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 ...Friendly URLS no longer work after upgrade to 5.6.2Friendly URLS no longer work after upgrade to 5.6.2
Previous
 
Next
New Post
3/25/2011 2:54 AM
 
Hit an error during upgrade from 5.6.1 to 5.6.2; I had followed the normal upgrade path - had the app_offline.htm in root folder and verified dnn was offline, checked autoupgrade was set to false, unzipped the upgrade package over the root, then renamed the app_offline.htm to app_offline.htm.save, then triggered the upgrade using the call to the install.aspx?mode=upgrade etc. but just when it looked like it would complete, it blew an error.  Here are all the status messages during the upgrade:



Upgrade Status Report

00:00:00.062 - Upgrading to Version: 05.06.02

00:00:00.358 -   Executing Script: 05.06.02.SqlDataProvider Success

00:00:03.603 -   Executing Application Upgrades: 05.06.02 Success

00:00:04.118 -   Cleaning Up Files: 05.06.02 Success

00:00:04.118 -   Updating Config Files: 05.06.02 Success

00:00:04.134 - Performing General Upgrades

00:00:05.195 - Installing Optional Modules:

00:00:05.257 -   Installing Package File HTML_Community_05.06.02_Install:  Success

00:00:19.064 -   Installing Package File Messaging_05.06.02_Install:  Success

00:00:23.776 -   Installing Package File Taxonomy_05.06.02_Install:  Success

00:00:30.359 -   Installing Package File Telerik_05.06.02_Install:  Success

00:00:36.490 - Installing Optional Skins:

00:00:36.506 - Installing Optional Containers:

00:00:36.537 - Installing Optional Languages:

00:00:36.568 - Installing Optional Providers:

00:00:36.600 -   Installing Package File FckHtmlEditorProvider_02.00.04_Install:



Server Error in '/main' 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 tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".



At this point I edited the web.config file to be able to see the errors, then tried the upgrade again.  At this point I got this strange error:



XML Parsing Error: no element found

Location: http://siteurl/install/install.aspx?m...

Line Number 1, Column 1:

^



So I then tried to just go to the base URL of the site, and it came up but has a serious problem:



None of the friendly URLs work - the only menu option that would work is the Host Settings option, where I could switch off the Friendly URL setting.  When it is off, I can get to the rest of the site using the menus.  When I set Friendly URLs on, using the default filters, I get this error for every page or a (similar one depending on which friendly url page is being tried) :



An error has occurred.



DotNetNuke.Services.Exceptions.PageLoadException: The file '/siteurl/Home.aspx' does not exist. ---> System.Web.HttpException: The file '/siteurl/Home.aspx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---




Gene W
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Friendly URLS no longer work after upgrade to 5.6.2Friendly URLS no longer work after upgrade to 5.6.2


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