Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

Error adding the DMX module after new install
Last Post 04/01/2008 1:26 PM by Peter Donker. 4 Replies.
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Sean Nolan
New Member
New Member
Posts:29


--
03/28/2008 5:23 AM

I installed on a hosted site. I checked all the things listed in the installation doc and everything checks out, all the files and database tables where they should be, but when I try to add the module to a page I get the following error:

Unhandled error loading module.
DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, 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.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at Bring2mind.DNN.Modules.DMX.Common.Settings.PortalSettings..ctor(Int32 PortalId) at Bring2mind.DNN.Modules.DMX.Common.Settings.PortalSettings.GetPortalSettings(Int32 PortalId) at Bring2mind.DNN.Modules.DMX.Common.Settings.Settings..ctor(Int32 PortalId, Int32 ModuleId) at Bring2mind.DNN.Modules.DMX.Framework.ModuleBase.get_Settings() at Bring2mind.DNN.Modules.DMX.Framework.ModuleBase.get_Query() at Bring2mind.DNN.Modules.DMX.Dispatch.ᜀ(Object A_0, EventArgs A_1) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) The action that failed was: Demand The type of the first permission that failed was: System.Security.Permissions.FileIOPermission The Zone of the assembly that failed was: MyComputer --- End of inner exception stack trace ---

My DNN installation and the DMX install have both created lots of folders on the site so I'm not sure why I'd be getting this error?

Sean

Sean Nolan
New Member
New Member
Posts:29


--
03/28/2008 5:29 AM

One thing to add in case it is relevant - I didn't create my portal folder in the default location as a numbered folder below Portals, I used a custom location. The custom folder I specified was created and the standard files and the Templates and Cache folders were created in the Portal folder.

Sean

Sean Nolan
New Member
New Member
Posts:29


--
03/28/2008 5:39 AM

OK, so I just tried to add the module in the host portal, which is located in the regular location (Portals/0) and it worked. So is there a known issue with using the module in portals that use a custom Home Directory? I'll create a new portal in the default location if I need to, but if I can make it work with my current portal that would be nice.

Thanks
Sean

Sean Nolan
New Member
New Member
Posts:29


--
03/29/2008 8:46 PM

I have managed to get this working - the custom portal directory for my portal had a slash (/) at the beginning of its name. I updated that directly in the database (its not editable through the DNN admin) and removed the leading slash. Now it seems to be working fine. This is something that DMX and probably DNN itself needs to handle a bit better I guess.

Peter Donker
Veteran Member
Veteran Member
Posts:4536


--
04/01/2008 1:26 PM
Hi Sean,

The error you got was 'System.Security.Permissions.FileIOPermission' failed. This means .net was overriding the application and refusing access to the location. There are only a few possibilities when you're experiencing file access problems:
1. Your server does not allow the application to access files/directories outside the application dir.
2. Permissions on disk were not properly set. This is common where people copy installations and expect them to work without checking the actual file permissions on disk.
3. A path error (apparently what you had). DMX expects a UNC type path to access contents. It is not aware of what happens in .net as it cannot actually do much as a .net application (all .net apps are 'managed'). If there's a path error you will get this type of error, yes.

Anyway, I'm glad you got it working.

Regards,

Peter
You are not authorized to post a reply.