From roles.config access error TO XML error

Jun 11, 2008 at 12:25 PM
We initiatilly for the Parser Error Message: Access to the path 'C:\Inetpub\MyWebPagesStarterKit\App_Data\Roles.config' is denied.

After reading the discussion topics and the manual regarding access rights and trust levels, my web-hoster has change the access rights and trust levels(and I quote from the hoster):

"We have just re-ensured that the medium trust level has been setup properly to enable fileIo operation to write to the App_Data directory at server level's web.config  file. I have also ensured that proper permission set have been given to appropriate folders."
We now get the following error message.  Frustrating!  Any ideas?


Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: There is an error in XML document (0, 0).

Source Error:

Line 50:       <providers>
Line 51: 				<clear/>
Line 52: <add name="CustomRoleProvider" type="MyWebPagesStarterKit.Providers.CustomRoleProvider"/>Line 53: 			</providers>
Line 54: 		</roleManager>

Source File: C:\Inetpub\vhosts\\httpdocs\web.config    Line: 52

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
<!-- [ConfigurationErrorsException]: There is an error in XML document (0, 0). (C:\Inetpub\vhosts\\httpdocs\web.config line 52) at System.Web.Security.Roles.Initialize() at System.Web.Security.Roles.get_CacheRolesInCookie() at System.Web.Security.RoleManagerModule.OnLeave(Object source, EventArgs eventArgs) at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --><!-- This error page might contain sensitive information because ASP.NET is configured to show verbose error messages using <customErrors mode="Off"/>. Consider using <customErrors mode="On"/> or <customErrors mode="RemoteOnly"/> in production environments.-->
Jun 11, 2008 at 2:59 PM
If your web.config is not at the root level, it will not work. If folder is your root, then web.config should be right under there, not  under httpdocs.
"C:\Inetpub\vhosts\\httpdocs\web.config". If I am mistaken, sorry. J.
Jun 12, 2008 at 12:51 PM
Thanks Juliafllorida.

I tried moving web.config to the root directory.  No success.  The web hoster is now checking if that needs access permission.

If I may, another question.
I have placed the MyWebPages Starter kit sub directories in a folder httpdocs.  Is it better to have a directory structure as follows:
Level 0:  root-directory:
             Level 1:  web.config <<File>>
             Level 1:  MyWebPagesStarterKit_1.1.4 <<Directory>>
                          Level 1.1 App_Data <<Directory>>
                          Level 1.1 App_Code  <<Directory>>
                          Level 1.1 other files and directories of MyWebPagesStarterKit_1.1.4 directory
The reason I ask is that when decompressing (unzipping) the starter kit it creates a directory called MyWebPagesStarterKit_1.1.4.  I have copied all the subdirectories of this folder (MyWebPagesStarterKit_1.1.4) to my web-hosters httpdocs folder (i.e. the httpdocs acts as the root directory for the MyStarterKit application.  I do not have a MyWebPagesStarterKit_1.1.4 directory). 

I did this as my web host had already provided me with an Apps_Data sub folder (folder where access rights are critical) in httpsdoc. 

Does not having a MyWebPagesStarterKit_1.1.4 directory the cause of the problems?

Thanks in advance, Peter
Jun 12, 2008 at 2:28 PM
You do not need MyWebPagesStarterKit_1.1.4 as root directory. Any name is fine. Under the root directory, all the files hierarchy should look the same as testing environment (meaning App_Data, App_Code and web.config should be the same level).  So, if you have root directory "httpdocs", your site should look like


If this is what you already have, then the problem is something else, I think.

Jun 14, 2008 at 1:16 PM

Many thanks Juliaflorida.

The above directory structure you write above is what I have.  I finally got MWPSK to work simply by switching providers to DailyRazor.

After spending a week with my web-hoster, the best recommendation I can make is use a provider such as DailyRazor. 

I am not sure why for them (DailyRazor) getting MWPSK to work is a breeze compared to others.