RE: Error: Failed to start monitoring changes - Framework 1.1

From: Gary Brown (Brown_at_discussions.microsoft.com)
Date: 09/19/04 

Date: Sun, 19 Sep 2004 11:44:48 -0700

We are having the exact same problem. On our system, this error does not
appear to surface until after the 5th or 6th web app has been launched.
Other than that, the problem does not occur in any consistent manner, that we
can see.

As a temporary fix, I moved the web folder to the local drive on our server
and set the home directory in IIS. This appeared to solve the problem. I
will post back here, as soon as I find out anything else.

-Gary B.

 

 As a temporary fix, I copied the web folder from the NAS to the local drive
on the server and changed the home directory in IIS. This appeared to solve
the problem. I will I will post back here as soon I find out anything else.

"David Good" wrote:

> 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.DirMonCompletion..ctor(DirectoryMonitor dirMon, String dir,
> Boolean watchSubtree, UInt32 notifyFilter)
> at System.Web.DirectoryMonitor.StartMonitoring()
> at System.Web.DirectoryMonitor.StartMonitoringFile(String file,
> FileChangeEventHandler callback, String alias)
> at System.Web.FileChangesMonitor.StartMonitoringFile(String alias,
> FileChangeEventHandler 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.DirectoryMonitor 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.