We have a network running both Win2k and Win2k3 webservers and our web sites
reside on a UNC network share that happens to be a Network Appliance NAS.
Since moving the web root to the network share on the NAS, we have been
receiving various forms of the following error:
Failed to start monitoring changes to [path]
at System.Web.DirM onCompletion..c tor(DirectoryMo nitor dirMon, String dir,
Boolean watchSubtree, UInt32 notifyFilter)
at System.Web.Dire ctoryMonitor.St artMonitoring()
at System.Web.Dire ctoryMonitor.St artMonitoringFi le(String file,
FileChangeEvent Handler callback, String alias)
at System.Web.File ChangesMonitor. StartMonitoring File(String alias,
FileChangeEvent Handler callback)
....
We have exhausted every resource we can find but every reference, including
the MSDN knowledgebase includes "Access Denied" along with the error and some
security-related solution and indicates that these problems are resolved with
the Framework v 1.1.
However, we do not receive the Access Denied portion of the errors that
everyone else is reporting - just the "Failed to start monitoring...", we are
running Framework version 1.1.4322, and it happens on both IIS 5 and IIS 6.
We are on a Win2k3 Domain, including the NAS. We run the websites as a
domain account, have impersonation turned on, the domain account has full and
complete access to the network share, and at this point, in trying to resolve
the issue, "Everyone" has full control over the directories in question.
Unfortunately, the errors seem to be very random - we can not reproduce them
at will. In fact, when we encounter a page with the error, if we hit the
"back" button on the browser and click the link to the erring page again, it
will work fine.
There are, however, a couple of commonalities:
We've noticed that EVERY time we receive this error, it references a path to
a directory that contains Web User Controls utilized by the page. It happens
regardless of whether the user controls are explicity placed in the pages or
are dynamically added to pages through code.
We've also explored the 8.3 file-name problems that have been pointed out by
several people and did notice with ILDASM in the System.Web.dll that there
are references to Short File names. We're unsure what to make of this or
why, if that's the problem, that the errors are so random.
We're pretty sure the System.Web.Dire ctoryMonitor has some functionality
related to the JIT compiler so perhaps these errors are generated when the
aspnet process recycles?
We're at our wits end.
--
David Good
Patriot HR, Inc.
reside on a UNC network share that happens to be a Network Appliance NAS.
Since moving the web root to the network share on the NAS, we have been
receiving various forms of the following error:
Failed to start monitoring changes to [path]
at System.Web.DirM onCompletion..c tor(DirectoryMo nitor dirMon, String dir,
Boolean watchSubtree, UInt32 notifyFilter)
at System.Web.Dire ctoryMonitor.St artMonitoring()
at System.Web.Dire ctoryMonitor.St artMonitoringFi le(String file,
FileChangeEvent Handler callback, String alias)
at System.Web.File ChangesMonitor. StartMonitoring File(String alias,
FileChangeEvent Handler callback)
....
We have exhausted every resource we can find but every reference, including
the MSDN knowledgebase includes "Access Denied" along with the error and some
security-related solution and indicates that these problems are resolved with
the Framework v 1.1.
However, we do not receive the Access Denied portion of the errors that
everyone else is reporting - just the "Failed to start monitoring...", we are
running Framework version 1.1.4322, and it happens on both IIS 5 and IIS 6.
We are on a Win2k3 Domain, including the NAS. We run the websites as a
domain account, have impersonation turned on, the domain account has full and
complete access to the network share, and at this point, in trying to resolve
the issue, "Everyone" has full control over the directories in question.
Unfortunately, the errors seem to be very random - we can not reproduce them
at will. In fact, when we encounter a page with the error, if we hit the
"back" button on the browser and click the link to the erring page again, it
will work fine.
There are, however, a couple of commonalities:
We've noticed that EVERY time we receive this error, it references a path to
a directory that contains Web User Controls utilized by the page. It happens
regardless of whether the user controls are explicity placed in the pages or
are dynamically added to pages through code.
We've also explored the 8.3 file-name problems that have been pointed out by
several people and did notice with ILDASM in the System.Web.dll that there
are references to Short File names. We're unsure what to make of this or
why, if that's the problem, that the errors are so random.
We're pretty sure the System.Web.Dire ctoryMonitor has some functionality
related to the JIT compiler so perhaps these errors are generated when the
aspnet process recycles?
We're at our wits end.
--
David Good
Patriot HR, Inc.