DNN siite suddenly broken after years

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

Home All Forums

1
2
3
4
5

Home

Our Community

General Discuss...

DNN siite suddenly broken after years

8/12/2007 12:28 PM

vidar brekke

Joined: 7/29/2004

Posts: 3

DNN siite suddenly broken after years

My DNN site stopped working after almost 2 years of operation. No changes or updates were made, but suddenly all I get is an error message. Before I spend many nights trying to troubleshoot this the wrong way (I'm no expert, I'll admit that), can anyone tell me what the problem (and solution!) might be from the following error message:

String was not recognized as a valid Boolean.

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.FormatException: String was not recognized as a valid Boolean.

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:

[FormatException: String was not recognized as a valid Boolean.]
   System.Boolean.Parse(String value) +2678388
   DotNetNuke.UI.Skins.Controls.SolPartMenu.Page_Load(Object sender, EventArgs e) +220

[ModuleLoadException: An error has occurred.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control UserCtrl, Exception exc) +291
   DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(Control UserCtrl, Exception exc) +42
   DotNetNuke.UI.Skins.Controls.SolPartMenu.Page_Load(Object sender, EventArgs e) +2874
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   System.Web.UI.Control.LoadRecursive() +47
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Control.LoadRecursive() +131
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061

[PageLoadException: An error has occurred.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +351
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +377
   System.Web.UI.TemplateControl.OnError(EventArgs e) +105
   System.Web.UI.Page.HandleError(Exception e) +73
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6969
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +213
   System.Web.UI.Page.ProcessRequest() +86
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +4
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +303
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64

Page 1 of 1

Home

Our Community

General Discuss...

DNN siite suddenly broken after years

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:

No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
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.
Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
No Flaming or Trolling.
No Profanity, Racism, or Prejudice.
Site Moderators have the final word on approving / removing a thread or post or comment.
English language posting only, please.

Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

String was not recognized as a valid Boolean.

DNN Corp. (DotNetNuke)