EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB9637: "Access denied to 'C:\Documents and Settings\NameOfProfile\My Documents'. Failed to start monitoring file changes" error message occurs when starting MicroStrategy Web.


Community Admin

• Strategy


When launching MicroStrategy Web, the following error message appears: Access denied to 'C:\Directory name...'. Failed to start monitoring file changes.

SYMPTOM:
When launching Strategy Web, the following error message appears:
 
Access denied to 'C:\Directory name...'. Failed to start monitoring file changes.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.HttpException: Access denied to 'C:\Directory name…'. Failed to start monitoring file changes.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
CAUSE:
This issue occurs because of Microsoft ASP.NET failing to monitor a directory path which is set in the Internet Information Server (IIS) configuration, as shown in the screen shot below:
 

ka04W000000Od3XQAS_0EM440000002944.jpeg

 
ACTION:
To resolve this issue, perform the following steps:
 

  1. Ensure that all of the directory names in the hierarchy of the Local Path (as shown in the screen shot above) are less than nine characters long.
  2. Grant the required permissions on all of the directories in the hierarchy to the ASP.NET process account (ASPNET by default) or to the impersonated account (if impersonation is turned on).

 


Comment

0 comments

Details

Knowledge Article

Published:

June 23, 2017

Last Updated:

June 23, 2017