We have been running DNN successfully at Crystaltech using their cheap Developer plans for some time under Windows Server 2003.  New sites have just started to use Windows Server 2008 with IIS 7.  The Developer plans run in Medium Trust (I think).  The sites get the exception listed below for [Host][Host Settings] and [Admin][Site Settings].

So, Crystaltech are currently only able to support DNN on Server 2008 on their more expensive Intermediate plans which run in Full Trust.  They also say: "To be honest this is going to be something for the DNN core team to look into..."

Anyway it would be great if DNN could be persuaded back into Medium Trust.  Any advice gratefully received.

From tomorrow I am away for a week, so I cannot help immediately, but I'd like to report this now.  In a quick search I could not see any similar posts, but apologies if this is a repeat of a known problem.

Chris Cant

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 System.Web.Handlers.ScriptResourceHandler.RuntimeScriptResourceHandler.System.Web.Handlers.IScriptResourceHandler.GetScriptResourceUrl(Assembly assembly, String resourceName, CultureInfo culture, Boolean zip, Boolean notifyScriptLoaded) at System.Web.UI.ScriptManager.GetScriptResourceUrl(String resourceName, Assembly assembly) at System.Web.UI.ScriptRegistrationManager.RegisterClientScriptResource(Control control, Type type, String resourceName) at System.Web.UI.ScriptManager.RegisterClientScriptResource(Control control, Type type, String resourceName) 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 --- at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) at System.Web.UI.WebControls.ValidatorCompatibilityHelper.RegisterClientScriptResource(Control control, Type type, String resourceName) at System.Web.UI.WebControls.BaseValidator.RegisterValidatorCommonScript() at System.Web.UI.WebControls.BaseValidator.OnPreRender(EventArgs e) at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Control.PreRenderRecursiveInternal() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

It is interesting how I have not found a single article related to the .NET trust level when installing to Windows Vista and IIS 7. In my case that was the "detail" that prevented the installation from passing the permissions test.

Assigning Full Control permissions to NT AUTHORITY/NETWORK SERVICE on the root directory of the web site took care of pretty much everything (file create, delete), except for the directory create permission, where I kept on getting the following exception:

Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib ... etc.... failed

After doing some research, I found this thread, set the trust level to High and the installation proceeded seamlessly. This is a development machine so I wasn't too concerned about the .NET trust level.

Another interesting tidbit is that a few months ago, I had set up a couple of other DNN sites on this machine, so I expected that a new 4.9 installation will be nothing but routine. I don't know what may have changed in the meantime, other than installing the usual Microsoft patches and SP1 for Vista,  but it appears that the trust level was been previously set by default to Full (internal). For some reason, it is now defaulting to medium.

To set the trust levels in IIS 7: http://technet.microsoft.com/en-us/library/cc753658.aspx

One of the references about installing DNN on Vista: http://www.sunsethill.ca/Resources/DotNetNuke/tabid/362/articleType/ArticleView/articleId/16/Default.aspx