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...Upgrade runs fine, then site fails.Upgrade runs fine, then site fails.
Previous
 
Next
New Post
1/3/2014 8:14 AM
 
Floyd Shadwick


Joined: 11/20/2013
Posts: 24

I finally got my site upgraded to 5.6.8 and running beautifully. I fun upgrade to 6.0.0, it runs with no errors. but then the site won't load. Upon start-up all I get is a red box stating 'An error has occurred. An error has occurred.'

Checking the error logs reveals a single entry: Upgrade to .NET 4.0 failed. Error reported during attempt to update:Error: Object reference not set to an instance of an object.   at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)     at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)     at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)     at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()     at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String configFile, Version version, String reason).

Can anyone point me to a resolution?

Thanks.

 
 
New Post
1/3/2014 8:34 AM
 
Floyd Shadwick


Joined: 11/20/2013
Posts: 24

Floyd Shadwick wrote:

On page load this error is logged:

AssemblyVersion = 6.0.0
PortalID = 0
PortalName = :: Check Into Cash ::
UserID = -1
UserName
ActiveTabID = 70
ActiveTabName = Home
RawURL = /dotnetnuke/Default.aspx?tabid=70&error=An%20unexpected%20error%20has%20occurred&content=0
AbsoluteURL = /dotnetnuke/Default.aspx
AbsoluteURLReferrer
UserAgent = Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/6.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; CMDTDFJS)
DefaultDataProvider = DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID = ef2d41da-38cb-46be-a5ce-44d55fd5f4cd
InnerException = String was not recognized as a valid Boolean.
FileName
FileLineNumber = 0
FileColumnNumber = 0
Method = System.Boolean.Parse
StackTrace
Message = DotNetNuke.Services.Exceptions.PageLoadException: String was not recognized as a valid Boolean. ---> System.FormatException: String was not recognized as a valid Boolean.    
 at System.Boolean.Parse(String value)    
 at DotNetNuke.NavigationControl.SolpartMenuNavigationProvider.set_ForceCrawlerDisplay(String value)    
 at DotNetNuke.UI.Skins.NavObjectBase.AssignControlProperties()    
 at DotNetNuke.UI.Skins.NavObjectBase.InitializeNavControl(Control objParent, String strDefaultProvider)    
 at DotNetNuke.UI.Skins.Controls.SolPartMenu.OnInit(EventArgs e)    
 at System.Web.UI.Control.InitRecursive(Control namingContainer)    
 at System.Web.UI.Control.InitRecursive(Control namingContainer)    
 at System.Web.UI.Control.InitRecursive(Control namingContainer)    
 at System.Web.UI.Control.AddedControl(Control control, Int32 index)    
 at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e)    
 at System.Web.UI.Control.InitRecursive(Control namingContainer)    
 at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)    
 --- End of inner exception stack trace ---
Source
 
New Post
1/4/2014 2:03 AM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
I suspect this is a changing pre-requisities issue -as 6.0 and above require .net 3.5sp1 (and .net 7.0 require asp.net 4.0), please ensure those versions are installed and (where necessary) the application pool has been changed to the right version (dependant on the DNN version you upgrade to) - also as a general note, whilst it's counterintuitive, it's often a good idea to use a .1 release when changing major branch i.e. 6.0.1 or 7.0.1. As a major branch change signifies lots of change, theres more risk in updating to that version - typically the .01 version of it has fixed any major issues (i.e. similar to the way some people wait for service pack 1 to come out when MS release a new operating system)
Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
1/6/2014 3:02 PM
 
Floyd Shadwick


Joined: 11/20/2013
Posts: 24

Thanks for the reply I thought it was a good possibility. I finally fixed that problem by removing a couple of unnecessary browser files.

I didn't mention I'm trying the upgrade on a Win7 workstation. Now I have a new problem. When I get to the 5.3.0 of the 5.4.4 upgrade now it fails with the following events:

AssemblyVersion 5.4.4
RawURL   /dotnetnuke/Install/Install.aspx?mode=upgrade
ExceptionGUID 7bf18b97-c5d2-47b5-b44f-ba4178b1bf3f
InnerException Object reference not set to an instance of an object.
Method   DotNetNuke.Services.Installer.XmlMerge.UpdateNode
Message   System.NullReferenceException: Object reference not set to an instance of an object.    
     at DotNetNuke.Services.Installer.XmlMerge.UpdateNode(XmlNode rootNode, XmlNode actionNode)    
     at DotNetNuke.Services.Installer.XmlMerge.ProcessNode(XmlNode node)    
     at DotNetNuke.Services.Installer.XmlMerge.ProcessNodes(XmlNodeList nodes, Boolean saveConfig)    
     at DotNetNuke.Services.Installer.XmlMerge.UpdateConfigs()    
     at DotNetNuke.Services.Upgrade.Upgrade.UpdateConfig(String strConfigFile, Version version, String strReason)

AssemblyVersion 5.4.4
RawURL   /dotnetnuke/Install/Install.aspx?mode=upgrade
ExceptionGUID 90a4e1a7-83dd-4928-9d0f-533c7b5421b2
InnerException Cannot create a file when that file already exists. 
Method   System.IO.__Error.WinIOError
Message   System.IO.IOException: Cannot create a file when that file already exists.      
     at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)    
     at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)    
     at DotNetNuke.Services.Upgrade.Upgrade.UpgradeToVersion_530()    
     at DotNetNuke.Services.Upgrade.Upgrade.UpgradeApplication(Version version, Boolean writeFeedback)

I'll gladly start a new thread if necessary.

Again thanks in advance.
 
New Post
1/7/2014 9:10 AM
 
cathal connolly


cathal connolly's Avatar

www.cathal.co.uk
Joined: 4/9/2003
Posts: 9676
that indicates a failure to upgrade web.config - typically this happens for one of a few reasons 1. the site permissions are not correct (either you have not granted modify permissions to the user that the website/application pool is running under, or you have not granted them to web.config), 2. web.config is readonly (this can occur if you've checked a site out of source control such as TFS), or 3. the web.config contains multiple tags and this is breaking the xmlmerge. Based on your 2nd exception it appears to be a permissions issue
Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
 Page 1 of 2
12Next 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...Upgrade runs fine, then site fails.Upgrade runs fine, then site fails.


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