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

HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Extensions Stored ProcedureExtensions Stored Procedure
Previous
 
Next
New Post
10/17/2011 1:35 PM
 
Ok, here's the simple version of my issue. I developed a Module and tried to add it to a page. When the module did not appear on the page I followed the instructions posted by Will Strohl for removing the module: http://www.willstrohl.com/Blog/EntryI....  However, after going through these steps I still have the module displaying in the Extensions under the host which I cannot delete without getting this error:

Error: is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: 'EndElement' is an invalid XmlNodeType. Line 11, position 7. ---> System.Xml.XmlException: 'EndElement' is an invalid XmlNodeType. Line 11, position 7. at System.Xml.XmlReader.ReadStartElement(String name) at DotNetNuke.Entities.Modules.Definitions.ModuleDefinitionInfo.ReadModuleControls(XmlReader reader) at DotNetNuke.Entities.Modules.Definitions.ModuleDefinitionInfo.ReadXml(XmlReader reader) at DotNetNuke.Entities.Modules.DesktopModuleInfo.ReadModuleDefinitions(XmlReader reader) at DotNetNuke.Entities.Modules.DesktopModuleInfo.ReadXml(XmlReader reader) at DotNetNuke.Common.Utilities.CBO.DeserializeObject[TObject](XmlReader reader) at DotNetNuke.Common.Utilities.CBO.DeserializeObject[TObject](TextReader reader) at DotNetNuke.Services.Installer.Installers.ModuleInstaller.ReadManifest(XPathNavigator manifestNav) at DotNetNuke.Services.Installer.Installers.InstallerFactory.GetInstaller(XPathNavigator manifestNav, PackageInfo package) at DotNetNuke.Services.Installer.Installers.PackageInstaller.ReadComponents(XPathNavigator manifestNav) at DotNetNuke.Services.Installer.Installers.PackageInstaller..ctor(PackageInfo package) at DotNetNuke.Services.Installer.Installer..ctor(PackageInfo package, String physicalSitePath) at DotNetNuke.Modules.Admin.Extensions.UnInstall.UnInstallPackage() at DotNetNuke.Modules.Admin.Extensions.UnInstall.cmdUninstall_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---


I was hoping to determine what Stored Procedure populates the extensions list so I can determine how to remove this reference.  The Dropdown list under modules does not display this module so I am basically trying to remove the module so I can attempt adding another version of my developed code. 

Any assistance would be appreciated.

Thanks,
Jeff
 
New Post
10/17/2011 3:34 PM
 
That blog post is over 2 years old, and DNN has had a large number of changes since then - including many architectural changes.  That blog post is really only good for the 4.x series of releases.  

Do you see this error on page load?

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
10/17/2011 3:45 PM
 
Will,

Thanks for your prompt response!  No the error I posted displays when I click the Uninstall Extension (red X) next to the module and then click Uninstall Package under the Host >> Extensions area.  I have gone through the tables I would have thought would contain the ModuleName and not found where this could be listed from.  I am currently on version 6.0.2 in the environment I am working in.

Any assistance you cna provide is greatly appreciated.

Thanks,
Jeff
 
New Post
10/17/2011 6:47 PM
 
I am not sure how comfortable you are with digging through the innards of DNN, that's how I originally wrote that blog post.  I ran into the same thing you are right now, and I had to step through the DesktopModules, Modules, TabModules, and other related tables to see where the orphaned module information was being kept.

The best place to start is to begin looking at the DeleteModule* stored procedures, checking all of the tables that it is referencing.  You are basically reverse-engineering the uninstall process to find the orphaned data.  This is what I had done in the past, and this is the way where you're going to find out exactly where the orphaned information is to delete.

When you're doing this, just be sure to not delete data without getting the big picture.  Map out where you module begins and ends - then begin planning the delete commands to get rid of it.

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
10/18/2011 8:12 AM
 
Will,

Thanks again for your propmt response!  The DeleteModule Stored Procedure just hits the Modules table, in which I am unable to find the orphaned reference.  I have also skimmed all the other Module and DesktopModule related tables looking for where the FriendlyName could be being displayed from without any success.

For that reason I thought looking at the Stored Procedure that populates the extensions screen would provide me more insight into where the orphaned record is coming from since the FriendlyName of the orphaned record is being displayed on that screen (I am also unable to add another module with the name I have chosen).  Any idea which Stored Procedure populates the Extensions screen?  I think that might be the best bet in my situation for resolving this issue.

Unfortunately, I also tried doing an integrity Check under the tools which also did not resolve this issue.

Thanks,

Jeff
 
Previous
 
Next
HomeHomeDevelopment and...Development and...DNN Platform (o...DNN Platform (o...Extensions Stored ProcedureExtensions Stored Procedure


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