Failed to start monitoring file changes.

[Mark]

Hello,

I have researched and tried every thing I have found on the web, in groups
and MS KB articles. Here is what I have.

I have a Windows 2000 Domain Controller all service packs and every thing
else from windows update.
..NET 1.0 and 1.1 installed on the server. Actually .NET was installed
before the server was made a DC.


This server is a VMWare virtual machine so when I have the ability to roll
back all changes and "try" again.


What I am trying to do is impersonation. I have a VERY simple test site
that I am using to get impersonation to work on a DC. The site name is
"test" and the only page is "default.aspx" with the content of "test page".
Pretty complex I know..... ha

Now, the web site works perfect with just that content. It will display
"test page" in the web browser. But if I add a web.config file with
impersonation added to the web.config i receive the error "Access denied to
'c:\inetpub\wwwroot\test\Default.aspx'. Failed to start monitoring file
changes."

The user that I have added to the impersonation element is none other than
the Domain administrator account. I am just using it for fun to get this
stuff to work. The final product will run under a normal user with hopefully
only the required rights to run the site. But you know what how can I
figure that out when i can't even get a domain administrator to work in
impersonation.

I am loged in as the Administrator created all of the content and testing
while using the same account to impersonate with. So I do not see how the
administrator account cannot have access to files IT just created!

What can I do to allow this user to work? What must I do then to make a
standard domain user to work. Answers please!! It seems no one knows how or
why this happens and I have seen where people have burned MSDN support calls
and STILL do not have a solution.

 

[Hernan de Lahitte]

Check for folder permissions of your account.
Here you have some useful links about this:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;317955
http://support.microsoft.com/default.aspx?scid=kb;EN-US;316721


--
Hernan de Lahitte
Lagash Systems S.A.
http://weblogs.asp.net/hernandl


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Mark]

I have read these and tried them. How does a "Domain Administrator" not
have access? The Domain administrator was the user that created these
folders. By default this means the administrator is the owner and does have
access to these folders, correct?

In my attempts to find where the folder that the Domain administrator did
not have access I just granted full access on c:\ to the administrator,
everyone, AND aspnet and the other web user account. I know this is nuts
but it is a VM and I can roll back the change later. But guess what, it
STILL gave the same error.

I am disturbed how other users have posted the same questions as myself do
not receive a straight answer. Every answer to this same question always
gets the same answer. Read x, x, x, KB articles download the file monitor
tool.

These KB articles did not solve the problem. Somthing else is wrong. If I
remove the impersonate line the test site works. Add the line the error
appears. Yes it is the correct password.

 

[Mark]

I have read these and tried them. How does a "Domain Administrator" not
have access? The Domain administrator was the user that created these
folders. By default this means the administrator is the owner and does have
access to these folders, correct?

In my attempts to find where the folder that the Domain administrator did
not have access I just granted full access on c:\ to the administrator,
everyone, AND aspnet and the other web user account. I know this is nuts
but it is a VM and I can roll back the change later. But guess what, it
STILL gave the same error.

I am disturbed how other users have posted the same questions as myself do
not receive a straight answer. Every answer to this same question always
gets the same answer. Read x, x, x, KB articles download the file monitor
tool.

These KB articles did not solve the problem. Somthing else is wrong. If I
remove the impersonate line the test site works. Add the line the error
appears. Yes it is the correct password.

 

[Mark]

Here is a small story of what I am doing.

I have a virtual machine Windows 2000 Enterprise server with .NET 1.0 and
1.1 installed and was upgraded to a DC.

1. Log in as Administrator
2. Create a folder C:\Inetpub\wwwroot\test
3. Create a file "default.aspx" content of the file is "hello world"
4. Load up Internet Information Services
5. Create "test" to be a web application or what ever that step would be
called. I click on the "create" button in the properties of "test"
6. Grant the user iwam_machinename to the
"C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files" folder
because it genreated a permission error when running the site.
7. Load up IE and access http://localhost/test and it works. The site
displays "hello world"

8. Create web.config with impersonate data. The user in the impersonate is
the Domain administrator account that is currently being used.
9. Accessing the site gives the error "Access denied to
'c:\inetpub\wwwroot\test\Default.aspx'. Failed to start monitoring file
changes."

WHY, WHY does this error happen?

When these same steps are performed on another VM that is a DC it actually
works. The same problem was not able to be reproduced. I have seen this
problem before so it is not a rare occurance with just this VM or my
install. It has happened when another network tech installed a windows DC
and another developer tried to setup an impersonate site. Same error and we
could not resolve the error so the machine was rebuilt. There are going to
be times where we will not be able to just "rebuild" the machine and the
problem has to be resolved.

In attempts to "fix" the problem
* aspnet_regiis -i was ran. Same result.
* .NET 1.0 and 1.1 uninstalled and reinstalled .NET 1.1. Same error still.
* Granting full control on c:\ just for kicks on everyone and administrator
and other user accounts. same error.


How can this be fixed on a server with out a rebuild of the server?

 

[Ken Schaefer]

Please use the Sysinternals Filemon tool to see what file is generating the
Access denied error, and which account is being used to access the file.
That will give you some idea as to why you are getting this error.

Cheers
Ken

: Here is a small story of what I am doing.
:
: I have a virtual machine Windows 2000 Enterprise server with .NET 1.0 and
: 1.1 installed and was upgraded to a DC.
:
: 1. Log in as Administrator
: 2. Create a folder C:\Inetpub\wwwroot\test
: 3. Create a file "default.aspx" content of the file is "hello world"
: 4. Load up Internet Information Services
: 5. Create "test" to be a web application or what ever that step would be
: called. I click on the "create" button in the properties of "test"
: 6. Grant the user iwam_machinename to the
: "C:\WINNT\Microsoft.NET\Framework\v1.1.4322\Temporary ASP.NET Files"
folder
: because it genreated a permission error when running the site.
: 7. Load up IE and access http://localhost/test and it works. The site
: displays "hello world"
:
: 8. Create web.config with impersonate data. The user in the impersonate
is
: the Domain administrator account that is currently being used.
: 9. Accessing the site gives the error "Access denied to
: 'c:\inetpub\wwwroot\test\Default.aspx'. Failed to start monitoring file
: changes."
:
: WHY, WHY does this error happen?
:
: When these same steps are performed on another VM that is a DC it actually
: works. The same problem was not able to be reproduced. I have seen this
: problem before so it is not a rare occurance with just this VM or my
: install. It has happened when another network tech installed a windows DC
: and another developer tried to setup an impersonate site. Same error and
we
: could not resolve the error so the machine was rebuilt. There are going
to
: be times where we will not be able to just "rebuild" the machine and the
: problem has to be resolved.
:
: In attempts to "fix" the problem
: * aspnet_regiis -i was ran. Same result.
: * .NET 1.0 and 1.1 uninstalled and reinstalled .NET 1.1. Same error
still.
: * Granting full control on c:\ just for kicks on everyone and
administrator
: and other user accounts. same error.
:
:
: How can this be fixed on a server with out a rebuild of the server?
:
:
:

 

[Mark]

I must admit I did use it, but this time.. I REALLY used the tool now. So,
here is what I have found. The following is a snipit from the log.

The Domain is "Win2000DC"
The aspnet_wp user "Win2000DC\IWAM_Wrongway"

The result from aspnet_wp.exe accessing the
C:\inetpub\wwwroot\test\Default.aspx is 0xC00000A5

0xC00000A5 = 0 0xc00000a5 0x001f0003 NT_STATUS_BAD_IMPERSONATION_LEVEL

I have not a clue what this means or how to solve this.

In the web.config i have the following under <system.web>

<identity impersonate="true"
userName="Win2000DC\administrator"
password="password" />

What is crazy is that the same default.aspx and web.config work on another
DC, yet we are unable to get it working on this DC. I have granted the
IWAM_Wrongway user access to c:\, c:\inetpub, c:\inetpub\wwwroot,
c:\inetpub\wwwroot\test and the same result is returned.

14 7:09:25 AM inetinfo.exe:1916 OPEN C:\INETPUB\WWWROOT\TEST\DEFAULT.HTM
FILE NOT FOUND Options: Open Access: All
15 7:09:25 AM inetinfo.exe:1916 OPEN C:\INETPUB\WWWROOT\TEST\DEFAULT.ASP
FILE NOT FOUND Options: Open Access: All
16 7:09:25 AM inetinfo.exe:1916 OPEN C:\INETPUB\WWWROOT\TEST\IISSTART.ASP
FILE NOT FOUND Options: Open Access: All
17 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
18 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
19 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\global.asax FILE NOT FOUND Attributes: Error
20 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
21 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
22 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
23 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
24 7:09:25 AM aspnet_wp.exe:1420 OPEN
C:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config *
0xC00000A5 Options: Open Access: All
25 7:09:25 AM aspnet_wp.exe:1420 OPEN
C:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config *
0xC00000A5 Options: Open Access: All
26 7:09:25 AM aspnet_wp.exe:1420 OPEN
C:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config *
0xC00000A5 Options: Open Access: All
27 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
28 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
29 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error
30 7:09:25 AM aspnet_wp.exe:1420 QUERY INFORMATION
C:\inetpub\wwwroot\test\Default.aspx * 0xC00000A5 Attributes: Error

 

[Mark]

So, the grand answer to this problem is.....
http://support.microsoft.com/default.aspx?scid=kb;en-us;824308

Now, this hopefully is documented that when you receive the "failed to start
monitoring file changes" and if you use the FileMon tool and see the result
code 0xC00000A5 you should check out the kb article 824308