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 ...Error doing upgrade from 4.8.0 to 5.2.2 using GoDaddyError doing upgrade from 4.8.0 to 5.2.2 using GoDaddy
Previous
 
Next
New Post
3/7/2010 11:38 AM
 

 

I am getting the following error since I upgraded from v 4.8.0 to v5.2.2.

GoDaddy recommened I uninstall and do a re-install.  My question is will a re-insall low away my current websit/portal info.

I have backed up my SQL Server Info and also the entire "dotnetnuke" directory.  Will I have to do a restore or does the install presever the existing portal info.

 

 


Upgrading DotNetNuke

Current Assembly Version: 05.02.02

Current Database Version: 05.02.02



 

Upgrade Status Report

00:00:00.015 - Upgrading to Version: 05.02.02
00:00:00.015 - Performing General Upgrades
 

 

 

 


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

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>

 
New Post
3/7/2010 2:02 PM
 

An uninstall followed by a reinstall of DotNetNuke will result in a loss of all current website/portal contents.

You mentioned that you "backed up your SQL Server Info and the entire DotNetNuke directory". Were the backups of the database and the site files done BEFORE you upgraded from v 4.8.0 to v 5.2.2 ? If they were done immediately BEFORE the upgrade from v 4.8.0, I would recommend that you restore the site using the backed up files and database, try to figure what went wrong during the upgrade, and they re attempt the upgrade after making any changes in the procedure. One change would be to upgrade from v 4.8.0 to v 4.9.5 then to the current v 5.2.3.

If the backups were made AFTER the upgrade then you won't be able to roll back to v 4.8.0 and will need to find out what went wrong and try to correct the upgrade issues. In that case, here are some troubleshooting tips and questions for you . . .

1. The screen shot that you show woud appear to be a reinstall of v 5.2.2 done after the upgrade to 5.2.2 failed - hence the same assembly and database version message. Do you recall receiving any errors during the upgrade from v4.8.0 to v 5.2.2 ?

2. Please check the site folder Providers\DataProviders\SqlDataProvider for any non-empty log files. These will have the name "xx.xx.xx.log" where xx.xx.xx represents the version number for which errors were logged during the upgrade.

3. Next we need to get a more detailed error message than the Server Error in "/dotnetnuke" application that you have posted. In your site's web.config file, find the line <customErrors mode="RemoteOnly" /> and change it to

<customErrors mode="Off" />

Note that "Off" begins with an upper case letter "O". Resave the modified web.config file. Then navigate back to the site address in your browser. A more detailed error message should now be shown. Post it here in the forum.

4. If you have database access using a tool such as SQL Server Management Studio Express, please examine the EventLog table for error messages logged at the time of the upgrade and later. The details will be in the LogProperties column as xml text.


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
3/7/2010 2:50 PM
 

Ok.  I modified my web.config and here is the latest error.

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Data at the root level is invalid. Line 1, position 1.

Source Error:

Line 1:  <browsers>
Line 2:  
Line 3:  	<!-- sample UA "Mozilla/5.0+(X11;+U;+Linux+i686;+en-US;+rv:1.9.0.10)+Gecko/2009042523+Ubuntu/9.04+(jaunty)+Firefox/3.0.10" -->

Source File: /dotnetnuke/App_Browsers/MozillaPatch.browser    Line: 1

Server Error in '/dotnetnuke' Application.

Parser Error

 


Version Information: Microsoft .NET Framework Version:2.0.50727.3603; ASP.NET Version:2.0.50727.3053

 

 
New Post
3/7/2010 6:52 PM
 

I was able to roll my version back to v 4.9.0.  I'm now getting the following error:

Does anyone know what may be causing this error.

 

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: Parameter count does not match Parameter Value count.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ArgumentException: Parameter count does not match Parameter Value count.]
   Microsoft.ApplicationBlocks.Data.SqlHelper.AssignParameterValues(SqlParameter[] commandParameters, Object[] parameterValues) +146
   Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteReader(String connectionString, String spName, Object[] parameterValues) +228
   DotNetNuke.Data.SqlDataProvider.GetPortal(Int32 PortalId) +92
   DotNetNuke.Entities.Portals.PortalController.GetPortal(Int32 PortalId) +143
   DotNetNuke.Entities.Portals.PortalSettings.GetPortalSettings(Int32 TabId, PortalAliasInfo objPortalAliasInfo) +135
   DotNetNuke.Entities.Portals.PortalSettings..ctor(Int32 tabId, PortalAliasInfo objPortalAliasInfo) +77
   DotNetNuke.HttpModules.UrlRewriteModule.OnBeginRequest(Object s, EventArgs e) +3394
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +68
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +75

Server Error in '/dotnetnuke' Application.

Parameter count does not match Parameter Value count.

 

 
New Post
3/7/2010 9:29 PM
 

Ok.  I modified my web.config and here is the latest error.

Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Data at the root level is invalid. Line 1, position 1.


I had never encountered that particular error but a bit of searching on Google turned up many results all of which related to having installed FrontPage extensions on the server or having used SharePoint Designer or Expression Web to publish the site. This caused folders named _vti_cnf to be created in many of a site's folders. In most cases, these folders (which contain information used by FrontPage, etc. to know which files have changed and need to be republished) cause no problem to an ASP.Net website. HOWEVER, if a _vti_cnf folder is created in the website's App_Browsers folder, an exception identical to yours will be generated.

Please check the folder /dotnetnuke/App_Browsers for the existance of a folder named _vti_cnf. If it is present, delete it and all of its contents. Then, try re-visiting your site.

EDITED: I responded with the above to your 5.2.2 error before noticing that you had a later post in the moderation queue. I'll address that error separately.


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
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Error doing upgrade from 4.8.0 to 5.2.2 using GoDaddyError doing upgrade from 4.8.0 to 5.2.2 using GoDaddy


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