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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...This has happened on two sites but I do not know the problemThis has happened on two sites but I do not know the problem
Previous
 
Next
New Post
4/22/2007 11:02 PM
 

 Unfortunately U cannot turn debug on after the fact. This site had the Authentication enabled and wouldn't upgrade. Disabling authentication allowed the upgrade, but then it bombed with this error. Now I cannot login to the site with AD Authentication. Not only that, I have to comment out the Authentication line (below) to get access to my site. I'm totally bummed!

Any ideas? Suggestions?

<!--

add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->

Upgrading DotNetNuke

Current Assembly Version: 04.05.01

Current Database Version: 04.04.01



Upgrade Status Report

00:00:00.015 - Upgrading to Version: 4.5.1
00:00:00.031 -   Executing Script: 04.05.00.SqlDataProvider Success
00:00:01.375 -   Executing Script: 04.05.01.SqlDataProvider Success
00:00:01.859 - Performing General Upgrades
 

 


Server Error in '/' Application.

Data at the root level is invalid. Line 1, position 1.

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.Xml.XmlException: Data at the root level is invalid. Line 1, position 1.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[XmlException: Data at the root level is invalid. Line 1, position 1.]
   System.Xml.XmlTextReaderImpl.Throw(Exception e) +87
   System.Xml.XmlTextReaderImpl.Throw(String res, String arg) +127
   System.Xml.XmlTextReaderImpl.ParseRootLevelWhitespace() +1906670
   System.Xml.XmlTextReaderImpl.ParseDocumentContent() +503
   System.Xml.XmlTextReaderImpl.Read() +38
   System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace) +145
   System.Xml.XmlDocument.Load(XmlReader reader) +96
   System.Xml.XmlDocument.Load(String filename) +157
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.InstallPortal(String strFile, Boolean writeFeedback, Int32 indent) +291
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent, String type) +867
   DotNetNuke.Modules.Admin.ResourceInstaller.ResourceInstaller.Install(Boolean writeFeedback, Int32 indent) +17
   DotNetNuke.Services.Install.Install.UpgradeApplication() +933
   DotNetNuke.Services.Install.Install.Page_Load(Object sender, EventArgs e) +286
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210

 
New Post
4/22/2007 11:23 PM
 

Now every time I attempt to upgrade a module it kicks me out.

Please, any suggestions here?

<JP>

 
New Post
4/23/2007 11:02 AM
 

It sounds like you might have a mal-formed web.config file that is causing the errors.  Did you use the release.config file and then merge your old data into that file?


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
4/23/2007 2:05 PM
 

Yes, I use the release.config and just add my SQL strings and the only other additional item I have in the web config is the following:
      <add name="HTTPHandler_SSL_PA" type="tt.SSL_Module.HTTPHandler_SSL, tt.SSL_Module" />
Plus, I upgraded with BOTH the upgrade code AND the Install Code with the same results.

Any assistance appreciated!  <JP>

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...This has happened on two sites but I do not know the problemThis has happened on two sites but I do not know the problem


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