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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLError After UpgradeError After Upgrade
Previous
 
Next
New Post
9/10/2011 1:17 PM
 
I upgraded my website to DNN 6.0.1.  I had a problem, see here, but got everything working except the XML module.   I upgraded the XML module to 6.0.1 after upgrading DNN.  Here is the error that I get from the event viewer:

ModuleId: 858
ModuleDefId: 128
FriendlyName: Webelo 1 Events
ModuleControlSource: DesktopModules/XML/XmlModule.ascx
AssemblyVersion: 6.0.1
PortalID: 3
PortalName: Cub Scout Pack 285
UserID: 1
UserName: host
ActiveTabID: 155
ActiveTabName: Webelos 1
RawURL: /Dens/Webelos1/tabid/155/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.cubscoutpack285.org/Forums...
UserAgent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 1440445f-097b-415f-ba35-864f57d62138
InnerException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Security.CodeAccessSecurityEngine.Check
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. ---> System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) at System.Security.CodeAccessPermission.Demand() at System.Net.NetworkCredential.get_Password() at DotNetNuke.Modules.Xml.Components.Utils.GetSha256HashCode(NetworkCredential credential) at DotNetNuke.Modules.Xml.Providers.XmlDataProvider.HttpRequest.Provider.GetCacheKey(String contentUrl, NetworkCredential credential) at DotNetNuke.Modules.Xml.Providers.XmlDataProvider.HttpRequest.Provider.GetXmlContent(String contentUrl, NetworkCredential credential, Boolean useCache) at DotNetNuke.Modules.Xml.Providers.XmlDataProvider.HttpRequest.Provider.Load(Int32 moduleId, Int32 portalId, Hashtable settings) at DotNetNuke.Modules.Xml.Components.XmlBaseController.get_XmlSource() at DotNetNuke.Modules.Xml.Components.XmlBaseController.Render(TextWriter output) at DotNetNuke.Modules.Xml.XmlModule.Page_Load(Object sender, EventArgs e) The action that failed was: Demand The type of the first permission that failed was: System.Security.Permissions.SecurityPermission The Zone of the assembly that failed was: MyComputer --- End of inner exception stack trace ---
Source:
Server Name: P3SWH190

It appears to be an security issue, but everyting else on the website is working fine.

Any help would be appreciated as I do not know the first step in resolving this problem.

Thanks,
Greg
 
New Post
9/10/2011 5:34 PM
 
So I think I have figured out the problem.  My production website is using Shared Hosting where IIS6 is locked down to a medium trust.  All of my testing has been done on my personal server with the default or full trust.  On my personal server I changed the web.config file to a medium or full trust and I can reproduce the error. 

So it appears the 6.0.1 XML module is not going to work with Shared Hosting. 

So how can I revert back to the 4.3.5 XML module that works with a medium trust?

Thanks,
Greg
 
New Post
9/11/2011 7:06 AM
 
The very best way would be to restore a backup before upgrade!

Other options:
  • Wait for a hot fix release though I cannot promise anything
  • If you are not running DNN6 (*):
    Copy DotNetNuke.Modules.Xml.dll from Xml6.0.0 to your bin (*)
  • If you are running DNN6(*)
    Install XML4.3.5 on a different server, delete bin/DotNetNuke.Modules.Xml.dll and copy all files within desktopmodules/xml and app_code/xml from there to  your server.

* If you need to follow these instructions, it looks like you did not have a working backup to revert the installation. I never tested the downgrade, and I can't guarantee it will work.
I strongly recommend that you test the procedure on a staging system. And please don't do anything without a fresh backup.

You must be aware that a manual downgrade may  result in a working solution, though it is NOT a real downgrade. Chances are high that it will never possible to upgrade again.  
 
New Post
9/15/2011 6:29 PM
 
I uploaded Xml6.0.2 to codeplex, it should fix the issue within Medium Trust

Use on your own risk, it is not much tested yet. As always, ensure that you have a fresh backup.
 
New Post
9/16/2011 8:06 AM
 
OK.  I will install on my development site (which now in configured for a medium trust) and test.

On my production site I noted all of my XML module usage/configuration and then uninstalled the 6.0.1 and installed 4.3.5.  Then I added the XML module back to the pages and everything is working fine.  I should be in good shape to upgrade to the 6.0.2 after testing.

Thanks,
Greg
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsXMLXMLError After UpgradeError After Upgrade


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