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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...FileIOPermission after move to new serverFileIOPermission after move to new server
Previous
 
Next
New Post
8/26/2011 7:10 AM
 
Hi all

My hosting company have migrated to new servers and now DNN is throwing FileIOPermission exceptions. I'll paste the error below. That's what happens if I login as host and click on "Host Settings".  More importantly, we can't add new pages. I think it's the same error but we just get the abbreviated "A critical error has occurred. Exception has been thrown by the target of an invocation." as soon as we hit the Add button.

I'm sure this is a simple permissions problem but the host support people tell me they have "reset the DNN permissions" twice. Could this be anything else? What could I tell them that would be helpful?

This is happening on two different sites. One is a test copy of the other and neither have had anything changed for months. It only happened after the server migration.

Unfortunately this has happened at the worst possible time. It's a school which is about to open for the new year and needs to post new info for parents.

Thanks

DotNetNuke.Services.Exceptions.PageLoadException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> 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.Reflection.Assembly.VerifyCodeBaseDiscovery(String codeBase) at System.Reflection.Assembly.get_CodeBase() at System.Web.Handlers.ScriptResourceHandler.GetCodeBaseWithAssert(Assembly assembly) at System.Web.Handlers.ScriptResourceHandler.GetLastWriteTime(Assembly assembly) at System.Web.Handlers.ScriptResourceHandler.GetAssemblyInfoInternal(Assembly assembly) at System.Web.Handlers.ScriptResourceHandler.GetAssemblyInfo(Assembly assembly) at
 
New Post
8/26/2011 8:07 AM
 
one thing to check is that files downloaded from the internet have their zone-file information set to mark them as unsafe - to work around this, please ensure that the files (or the zip files that contains them) is right clicked, select properties and click "unblock". Also, please check that .net 3.5sp1 is installed as some invocation issues come from Ajax (which is part of that release but not part of .net 2.0)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/26/2011 9:59 AM
 
Thanks Cathal

I think you might be right about the zones. I can see that unblock button on some files with my Windows 7 desktop.

Unfortunately, Windows Explorer doesn't seem to provide a way of unblocking multiple files in one operation. If you select multiple files and hit properties then you get a different popup.

Which files would they need to unblock? Is it just the dll files in bin ?

Cheers
Ross
 
New Post
8/26/2011 10:55 AM
 
hmm, it should just be the dll files in the bin but I'd be inclined to do all files (i.e. get a fresh upgrade zip file and do it on the zip and that will propagate to all files - and then overwrite the files with those versions)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/29/2011 7:25 AM
 
Well ... good and bad news.

I finally discovered that it was related to Ajax. If I disable Ajax using SQL (because I can't get to the host settings page) then the FileIOPermission problem goes away so the immediate crisis is solved.

Unfortunately the host has given up on this problem so we may need to live without Ajax. They've told me to "consult the DNN experts". It appears that Ajax is attempting to access something outside of the web root but I have no real way of knowing what it's trying to access or why. The thing is that this worked fine on their old server but as far as they're concerned, all the settings are the same. We do indeed seem to have the usual full read/write permission on the web root and sub folders. I temporarily put some testing / debugging code in Default.aspx.vb to confirm that. They assure me that we have .NET 3.5sp1.

Does anyone have any suggestions of what the problem could be?

I'm embarrassed to say it but this is DNN 04.08.02. I know we should upgrade but some of the modules are not upgradable and it's been generally working fine. I patched the file upload venerability that we got hit with a few times. We may be building a new site in the next few months.

I might install a clean copy of the latest version of DNN and see if it happens with that. If it does then I can say to the host that you effectively no longer support DNN.

Thanks
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...FileIOPermission after move to new serverFileIOPermission after move to new server


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