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 ...Error on Classic Control PanelError on Classic Control Panel
Previous
 
Next
New Post
10/3/2012 10:35 PM
 

When I switch to Classic Cotrol Pale in the Hosting Settings,

I tried the suggested solution (to revert back to the iconbar, but it did not work)

 http://www.dotnetnuke.com/Resources/Forums/forumid/7/threadid/127333/scope/posts.aspx

I checked files are in the referred directory, a;; are there

I prefer to remove the "classic" setting all together, just in case and would be safer

I am using 6.2.2

I get the following message:

 

Server Error in '/' Application.

Object reference not set to an instance of an object.

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.NullReferenceException: Object reference not set to an instance of an object.

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:

[NullReferenceException: Object reference not set to an instance of an object.] DotNetNuke.UI.ControlPanels.Classic.Page_Load(Object sender, EventArgs e) +2483 [ModuleLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +361 [PageLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +558 DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, Control ctrl, Exception exc, Boolean DisplayErrorMessage) +1045 DotNetNuke.UI.ControlPanels.Classic.Page_Load(Object sender, EventArgs e) +2964 System.Web.UI.Control.LoadRecursive() +71 System.Web.UI.Control.LoadRecursive() +190 System.Web.UI.Control.LoadRecursive() +190 System.Web.UI.Control.LoadRecursive() +190 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3064 [PageLoadException: An error has occurred.] DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +558 System.Web.UI.Page.HandleError(Exception e) +182 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +11439382 System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +11438910 System.Web.UI.Page.ProcessRequest() +269 System.Web.UI.Page.ProcessRequest(HttpContext context) +167 System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +625 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +270 



Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

 
New Post
10/7/2012 3:02 AM
 

the referred solution worked to put the web portal back alive but not resolving the issue, i like to remove the classic option all together frorm the host settings, just in case.



http://www.dotnetnuke.com/Resources/Forums/forumid/7/threadid/127333/scope/posts.aspx
 

 
New Post
10/7/2012 2:11 PM
 
I am not sure atm, whether controls panels are getting registered or just files being looked up in /admin/controlpanel folder. Try temporarily remove classic control panel and check, whether it still shows up in Host Settings DDL

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/7/2012 2:28 PM
 

Thanks for your reply, I removed Classic.ascx and Classic.ascx.vb in   the controlpanel folder, but i can still see the "classic" in the drop down in the host settings

 
New Post
10/7/2012 2:44 PM
 
ok, I checked it in the database. You need to run the following query from Host :: SQL:
DELETE FROM {databaseOwner}[{objectQualifier}ModuleControls] WHERE ControlSrc Like 'Admin/ControlPanel/Classic.ascx' AND ControlType = -3
backup your database first and restart your application after you executed the script.
BTW: AFAIK the Classic Control Panel will be removed from DNN package in DNN 7.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Error on Classic Control PanelError on Classic Control Panel


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