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/31/2011 12:05 PM
 
ah-as thats a very old version, MS Ajax was contained in the BIN folder (it's the system.web.extensions.dll) - this file needs full trust code access security, so if your host is not running as that you will have problems. The correct way to deal with this is to have the host have it installed on the server (which makes it available to all sites and removes the full trust requirement). You may need to manually remove this dll if the host has it removed and the website permissions are not correct (i.e. we check on app startup and attempt to delete the file if it appears unneeded)

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
8/31/2011 1:38 PM
 
Thanks Cathal. I think you're pointing me in the right direction.

I deleted System.Web.Extensions.dll but now it complains that it can't find the assembly or one of its dependencies in this line of web.config. Does that suggest the host does not have it installed in the GAC? I wonder if DNN does some other test to determine that it's "not needed".

<add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
 
New Post
8/31/2011 4:59 PM
 
Fixed!

I had to replace all occurrences in web.config of 1.0.61025.0 related to System.Web.Extensions to 3.5.0.0.

Thanks for help.  

Cheers
Ross
 
New Post
8/31/2011 7:16 PM
 
thats great to hear - but I would recommend you get the host to check that they applied modify permissions from the root down as it means the automated code that is supposed to delete the dll (and update the web.config references) was not working - and unless that version had a bug (might do as it's a long time since i looked at it) then the likely culprit would be windows permissions.

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
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