Article ID: 320117 - View products that this article applies to.
This article was previously published under Q320117
When you open ASP.NET (.aspx) pages in your browser, you may receive the following error message and stack trace:
Value cannot be null. Parameter name: path2.
Stack Trace: [ArgumentNullException: Value cannot be null. Parameter name: path2] System.IO.Path.Combine(String path1, String path2) System.Web.FilePathParse..ctor(String path, Boolean isFile, Boolean getShortNames) System.Web.FileChangesMonitor.StartMonitoringDirectoryRenamesAndBinDirectory(String dir, FileChangeEventHandler callback) System.Web.HttpRuntime.StartMonitoringDirectoryRenamesAndBinDirectory() System.Web.HttpRuntime.FirstRequestInit(HttpContext context) [HttpException (0x80004005): ASP.NET Initialization Error] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr)
File Change detection requires that the process identity and the impersonated user identity have specific permissions to all of the directories in the hierarchy of the file path for the file that ASP.NET is monitoring if any of the directories in that hierarchy have more than eight characters in their names.
Some of the files that ASP.NET monitors are:
To work around this problem, use one of the following methods.
Workaround 1Make sure that all of the directory names in the hierarchy of that file path are less than nine characters long. For example:
Workaround 2Grant the required permissions to the Aspnet_wp.exe process identity (the ASPNET account by default) on all of the directories in that hierarchy or the impersonated account (if impersonation is turned on).
To do this, follow these steps:
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article. This bug was corrected in ASP.NET (included with the .NET Framework) 1.1.
If the error message that you receive is the same as the error message that is listed in the "Symptoms" section of this article, but the stack trace does not match the stack trace in the "Symptoms" section, the cause of your error message may be different. For more information, see the "References" section of this article.
For additional information about a different error message for the same cause, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/316721/EN-US/ )PRB: "Failed to Start Monitoring Directory Changes" Error Message When You Browse to ASP.NET Page
317955For additional information about the minimum permissions that you must grant to the ASPNET account to run your ASP.NET applications, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/317955/EN-US/ )BUG: "Failed to Start Monitoring Directory Changes" Error Message When You Browse to an ASP.NET Page
317012For additional information about ASP.NET security, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/317012/EN-US/ )INFO: Process and Request Identity in ASP.NET
(http://support.microsoft.com/kb/306590/EN-US/ )INFO: ASP.NET Security Overview
Article ID: 320117 - Last Review: March 21, 2003 - Revision: 2.1
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Contact us for more help