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...Using Modules a...Using Modules a...Cannot Access Website After Uninstalling ExtensionCannot Access Website After Uninstalling Extension
Previous
 
Next
New Post
6/11/2011 2:39 AM
 
Hi,

I just uninstalled the DDR Menu, but did not remove it from the page it was being used on before I uninstalled it. Now, I am getting an error when I try to access my website (see below). I tried to access the database to see what I could do from there, but it is set as read only and I cannot figure out how to change that either.

If someone could please help me with this, I would really appreciate it as I am now at a stand still.

Thanks so much!
Jenny

Server Error in '/DotNetNuke' Application.

Could not load provider DotNetNuke.Web.DDRMenu.DDRMenuNavigationProvider, DotNetNuke.Web.DDRMenu

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.Configuration.Configurati sException: Could not load provider DotNetNuke.Web.DDRMenu.DDRMenuNavigationProvider, DotNetNuke.Web.DDRMenu

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:

[Configurati sException: Could not load provider DotNetNuke.Web.DDRMenu.DDRMenuNavigationProvider, DotNetNuke.Web.DDRMenu] DotNetNuke.ComponentModel.ProviderInstaller.InstallProvider(IContainer container, Provider provider) +580 DotNetNuke.ComponentModel.ProviderInstaller.InstallComponents(IContainer container) +324 DotNetNuke.ComponentModel.ComponentFactory.InstallComponents(IComponentInstaller[] installers) +121 DotNetNuke.Common.Global.Application_Start(Object Sender, EventArgs E) +1756 [HttpException (0x80004005): Could not load provider DotNetNuke.Web.DDRMenu.DDRMenuNavigationProvider, DotNetNuke.Web.DDRMenu] System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +4174081 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +205 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +336 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +350 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +382 [HttpException (0x80004005): Could not load provider DotNetNuke.Web.DDRMenu.DDRMenuNavigationProvider, DotNetNuke.Web.DDRMenu] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +11305670 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +88 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +4342340 
 
New Post
6/11/2011 6:35 AM
 
you need to rename the skin folder (inside /portals/_default/skins or /portals/[portal_id]/Skins) to force a fallback to default skin ans should be able to re-install it afterwards.
another option would be uploading the mene extension package to /install/module and call /install/install.aspx?mode=installResources in your browser.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/11/2011 9:01 PM
 
Thanks for your reply. I tried both of your suggestions and am still getting the same error.

Just so I'm understanding correctly, when you suggested to upload the menu extension to the install/module folder, did you mean to copy the .zip file there?

Thanks again!
 
New Post
6/12/2011 2:31 AM
Accepted Answer 
yes, upload may copy the zip file.
You may first need to edit your web.config file and remove the ddnmenu reference.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
6/12/2011 7:01 PM
 
Thank you so much! That's exactly what I needed to do :o)
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Using Modules a...Using Modules a...Cannot Access Website After Uninstalling ExtensionCannot Access Website After Uninstalling Extension


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