Hi all
class
AspNetMembershipProvider
function
GetMembershipUser(ByVal userName As String) As AspNetSecurity.MembershipUser
Instruction
Return AspNetSecurity.Membership.GetUser(userName)
I get SecurityException
Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
I use DNN 4.3.5 Source, SQL Server 2000 on Win XP SP2 IIS 5.1
I gave full control to the root folder DotNetNuke_2 to users ASPNET, IUSR_XXX, IWAM_XXX, and replaced permissions on all child objects in this folder.
As for Web.config, I only changed the SQL Server connection string, and that part is working as youo can see in the log below.
Any help? Thank you.
Installing DotNetNuke
Version: 04.03.05
Installation Status Report
00:00:00.484 - Installing Version: 3.1.0
00:00:00.500 - Installing Script: DotNetNuke.SetUp.SqlDataProvider Success
00:00:01.921 - Installing Script: DotNetNuke.Schema.SqlDataProvider Success
00:00:26.828 - Installing Script: DotNetNuke.Data.SqlDataProvider Success
00:00:30.093 - Installing MemberRole Provider:
00:00:30.093 - Executing InstallCommon.sql
00:00:33.406 - Executing InstallMembership.sql
00:00:35.953 - Executing InstallProfile.sql
00:00:37.140 - Executing InstallRoles.sql
Success
00:00:39.421 - Upgrading to Version: 3.1.1 Success
00:00:47.406 - Upgrading to Version: 3.2.0 Success
00:00:48.234 - Upgrading to Version: 3.2.1 Success
00:00:48.875 - Upgrading to Version: 3.2.2 Success
00:00:49.109 - Upgrading to Version: 3.2.3 Success
00:00:58.593 - Upgrading to Version: 3.2.4 Success
00:00:58.875 - Upgrading to Version: 3.2.5 Success
00:00:59.296 - Upgrading to Version: 3.2.6 Success
00:00:59.843 - Upgrading to Version: 3.2.7 Success
00: - Upgrading to Version: 3.3.0 Success
00:01:00.468 - Upgrading to Version: 3.3.1 Success
00:01:00.859 - Upgrading to Version: 3.3.2 Success
00:01:01.609 - Upgrading to Version: 3.3.3 Success
00:01:03.156 - Upgrading to Version: 4.0.0 Success
00:01:04.703 - Upgrading to Version: 4.0.1 Success
00:01:05.515 - Upgrading to Version: 4.0.2 Success
00:01:05.812 - Upgrading to Version: 4.0.3 Success
00:01:06.078 - Upgrading to Version: 4.0.4 Success
00:01:13.875 - Upgrading to Version: 4.0.5 Success
00:01:14.062 - Upgrading to Version: 4.0.6 Success
00:01:14.234 - Upgrading to Version: 4.0.7 Success
00:01:14.421 - Upgrading to Version: 4.3.0 Success
00:01:14.921 - Upgrading to Version: 4.3.1 Success
00:01:15.359 - Upgrading to Version: 4.3.2 Success
00:01:16.359 - Upgrading to Version: 4.3.3 Success
00:01:17.500 - Upgrading to Version: 4.3.4 Success
00:01:17.750 - Upgrading to Version: 4.3.5 Success
00:01:19.531 - Performing General Upgrades
00:01:24.750 - Loading Host Settings:
00:01:28.187 - Configuring SuperUser:
Server Error in '/DotNetNuke_2' Application.
Security Exception
Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.
Exception Details: System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario. |
Stack Trace:
[SecurityException: Request for the permission of type 'System.Security.Permissions.FileIOPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.]
System.Web.Security.Membership.Initialize() +207
System.Web.Security.Membership.get_RequiresQuestionAndAnswer() +19
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +9021
System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +158
System.Web.UI.Page.ProcessRequest() +85
System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +20
System.Web.UI.Page.ProcessRequest(HttpContext context) +110
ASP.install_install_aspx.ProcessRequest(HttpContext context) +29
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +317
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +65
|
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210