Failed to start monitoring changes to web.config because access is denied.

Question

User-830789927 posted
I developed a single plain text webPage with VB2005 I selected "Local IIS" , location HTTP and option creat a "new webapplication" System: XP IIS 5.1 Microsoft .NET Framework Version:2.0.50727.42 ASP.NET Version:2.0.50727.42 when I try to run page from IIS folder the following error shows up: Server Error in '/Web1' 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: An error occurred loading a configuration file: Failed to start monitoring changes to 'c:\inetpub\wwwroot\web.config' because access is denied. Source Error: [No relevant source lines] Source File: c:\inetpub\wwwroot\web.config Line: 0 Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

Answer 1

User1684693608 posted

 Is your application exists in this path c:\inetpub\wwwroot\web.config direct or it's included in subfolder ?

Answer 2

User-830789927 posted
The application is the following subfolder: C:\Inetpub\wwwroot\Web2 Web2 folder has read and write access for all users , web sharing option is enable.

Answer 3

User1684693608 posted

I think you have a problem in the application path because the error message showing in correct path

Parser Error Message: An error occurred loading a configuration file: Failed to start monitoring changes to 'c:\inetpub\wwwroot\web.config' because access is denied

Answer 4

User-830789927 posted
You are right , however I got the same error message if I save the application directly on wwwroot folder or inside subfolder web2.

Answer 5

User217838333 posted

Hi,

Your Web.Config File should be in correct folder.

You have not placed your application in seperate folder.

Answer 6

User-1535033130 posted

It is not problem of application path. It is problem of user credentials configured in the application pool. So please check both app pool account and as well as application path security account.