ASP.NET Fails after SP4 with Impersonation

[Raymond Basque]

Michael,

See [url]http://support.microsoft.com/default.aspx?scid=kb;[/url][LN];821546


"Michael Kennedy [UB]" <mkennedy@REMOVETHIS.unitedbinary.com> wrote in
message news:ujp$QUNPDHA.3236@TK2MSFTNGP10.phx.gbl...

> Hi Everyone,
>
> Last night we installed SP4 on our Windows 2000 Advanced Server which was
> are using as an ASP.NET web server (.NET 1.1). This morning we found out
> that our ASP.NET applications that use impersonation. That is from the
> web.config:
>
> <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD" />
>
> fail with the message "Access Denied: Failed to start monitoring
> c:\inetpub\wwwroot\myapp\default.aspx for changes."
>
> This application worked fine before. Moreover, if I remove the

impersonation

> line from the web.config, everything is find again except of course things
> that required the impersonation fail.
>
> Does anyone know why this happens? Better yet, anyone know how to fix it?
>
> Thanks in advance!
> Michael
>
>
>

[Bassel Tabbara [MSFT]]

Hello Michael,
Try to add read, execute, and list access for the account on the root Web
site or on any virtual directory, follow these steps:



1. In Windows Explorer, browse to the folder that contains the root Web
site (which is C:\Inetpub\Wwwroot by default) or the virtual directory.

2. Right-click the folder, and then click Properties.

3. On the Security tab, click Add.

4. Type "<ComputerName>\ASPNET" (without the quotation marks) (for
example, on a computer named Webdev, type "Webdev\Account" (without the
quotation marks)), and then click OK.

5. Allow the following permissions for the custom account:

- Read & Execute

- List Folder Contents

- Read



6. Click OK to close the Properties dialog box and to save the changes.


NOTE: You do not need to perform these steps if the Everyone group or the
Users group has read access to the root Web site or virtual directory.

You might check also the following Kb article:
317955 FIX: "Failed to Start Monitoring Directory Changes" Error Message
When
[url]http://support.microsoft.com/?id=317955[/url]


Please let me know if this solves the problem.


Thanks,
Bassel Tabbara
Microsoft, ASP.NET

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


--------------------
| From: "Michael Kennedy [UB]" <mkennedy@REMOVETHIS.unitedbinary.com>
| Subject: ASP.NET Fails after SP4 with Impersonation
| Date: Fri, 27 Jun 2003 10:53:47 -0700
| Lines: 23
| Organization: United Binary, LLC.
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <ujp$QUNPDHA.3236@TK2MSFTNGP10.phx.gbl>
| Newsgroups:
microsoft.public.dotnet.framework.aspnet,microsoft .public.win2000.general
| NNTP-Posting-Host: 130.191.240.187
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.general:55001
microsoft.public.dotnet.framework.aspnet:155514
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Hi Everyone,
|
| Last night we installed SP4 on our Windows 2000 Advanced Server which was
| are using as an ASP.NET web server (.NET 1.1). This morning we found out
| that our ASP.NET applications that use impersonation. That is from the
| web.config:
|
| <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD" />
|
| fail with the message "Access Denied: Failed to start monitoring
| c:\inetpub\wwwroot\myapp\default.aspx for changes."
|
| This application worked fine before. Moreover, if I remove the
impersonation
| line from the web.config, everything is find again except of course things
| that required the impersonation fail.
|
| Does anyone know why this happens? Better yet, anyone know how to fix it?
|
| Thanks in advance!
| Michael
|
|
|
|

[John Saunders]

It's impressive how quickly MS has addressed this issue.

I would also be impressed if someone would tell me how we were supposed to
know about this problem? There's a HUGE list of bug fixes in SP4. Were we
supposed to read every one of those KB articles?

--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]


"Raymond Basque" <NOSPAMrbasque@jednm.comNO_SPAM> wrote in message
news:uki0ctNPDHA.1624@tk2msftngp13.phx.gbl...

> Michael,
>
> See [url]http://support.microsoft.com/default.aspx?scid=kb;[/url][LN];821546
>
>
> "Michael Kennedy [UB]" <mkennedy@REMOVETHIS.unitedbinary.com> wrote in
> message news:ujp$QUNPDHA.3236@TK2MSFTNGP10.phx.gbl...

> > Hi Everyone,
> >
> > Last night we installed SP4 on our Windows 2000 Advanced Server which

was

> > are using as an ASP.NET web server (.NET 1.1). This morning we found out
> > that our ASP.NET applications that use impersonation. That is from the
> > web.config:
> >
> > <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD"

/>

> >
> > fail with the message "Access Denied: Failed to start monitoring
> > c:\inetpub\wwwroot\myapp\default.aspx for changes."
> >
> > This application worked fine before. Moreover, if I remove the

> impersonation

> > line from the web.config, everything is find again except of course

things

> > that required the impersonation fail.
> >
> > Does anyone know why this happens? Better yet, anyone know how to fix

it?

> >
> > Thanks in advance!
> > Michael
> >
> >
> >

>
>

[Michael Kennedy [UB]]

Thanks Raymond,

That seems to be exactly the problem I'm encountering. I have tried taking
all the steps mentioned in the KB article, but I'm still suffering the
problem. I'll keep looking into it

Thanks again!
Michael


"Raymond Basque" <NOSPAMrbasque@jednm.comNO_SPAM> wrote in message
news:uki0ctNPDHA.1624@tk2msftngp13.phx.gbl...

> Michael,
>
> See [url]http://support.microsoft.com/default.aspx?scid=kb;[/url][LN];821546
>
>
> "Michael Kennedy [UB]" <mkennedy@REMOVETHIS.unitedbinary.com> wrote in
> message news:ujp$QUNPDHA.3236@TK2MSFTNGP10.phx.gbl...

> > Hi Everyone,
> >
> > Last night we installed SP4 on our Windows 2000 Advanced Server which

was

> > are using as an ASP.NET web server (.NET 1.1). This morning we found out
> > that our ASP.NET applications that use impersonation. That is from the
> > web.config:
> >
> > <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD"

/>

> >
> > fail with the message "Access Denied: Failed to start monitoring
> > c:\inetpub\wwwroot\myapp\default.aspx for changes."
> >
> > This application worked fine before. Moreover, if I remove the

> impersonation

> > line from the web.config, everything is find again except of course

things

> > that required the impersonation fail.
> >
> > Does anyone know why this happens? Better yet, anyone know how to fix

it?

> >
> > Thanks in advance!
> > Michael
> >
> >
> >

>
>

[Michael Kennedy [UB]]

Hi Bassel,

Thanks. I think it may have been a combination of this and the KB article
mentioned previously by Raymond. I'm still working on it however. There is
something that is not quite right here. I'll let you know if I learn any
more details.

Michael

""Bassel Tabbara [MSFT]"" <basselt@online.microsoft.com> wrote in message
news:8VGEAZOPDHA.1200@cpmsftngxa06.phx.gbl...

> Hello Michael,
> Try to add read, execute, and list access for the account on the root Web
> site or on any virtual directory, follow these steps:
>
>
>
> 1. In Windows Explorer, browse to the folder that contains the root Web
> site (which is C:\Inetpub\Wwwroot by default) or the virtual directory.
>
> 2. Right-click the folder, and then click Properties.
>
> 3. On the Security tab, click Add.
>
> 4. Type "<ComputerName>\ASPNET" (without the quotation marks) (for
> example, on a computer named Webdev, type "Webdev\Account" (without the
> quotation marks)), and then click OK.
>
> 5. Allow the following permissions for the custom account:
>
> - Read & Execute
>
> - List Folder Contents
>
> - Read
>
>
>
> 6. Click OK to close the Properties dialog box and to save the changes.
>
>
> NOTE: You do not need to perform these steps if the Everyone group or the
> Users group has read access to the root Web site or virtual directory.
>
> You might check also the following Kb article:
> 317955 FIX: "Failed to Start Monitoring Directory Changes" Error Message
> When
> [url]http://support.microsoft.com/?id=317955[/url]
>
>
> Please let me know if this solves the problem.
>
>
> Thanks,
> Bassel Tabbara
> Microsoft, ASP.NET
>
> This posting is provided "AS IS", with no warranties, and confers no

rights.

>
>
> --------------------
> | From: "Michael Kennedy [UB]" <mkennedy@REMOVETHIS.unitedbinary.com>
> | Subject: ASP.NET Fails after SP4 with Impersonation
> | Date: Fri, 27 Jun 2003 10:53:47 -0700
> | Lines: 23
> | Organization: United Binary, LLC.
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> | Message-ID: <ujp$QUNPDHA.3236@TK2MSFTNGP10.phx.gbl>
> | Newsgroups:
> microsoft.public.dotnet.framework.aspnet,microsoft .public.win2000.general
> | NNTP-Posting-Host: 130.191.240.187
> | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTN GP10.phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.general:55001
> microsoft.public.dotnet.framework.aspnet:155514
> | X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
> |
> | Hi Everyone,
> |
> | Last night we installed SP4 on our Windows 2000 Advanced Server which

was

> | are using as an ASP.NET web server (.NET 1.1). This morning we found out
> | that our ASP.NET applications that use impersonation. That is from the
> | web.config:
> |
> | <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD"

/>

> |
> | fail with the message "Access Denied: Failed to start monitoring
> | c:\inetpub\wwwroot\myapp\default.aspx for changes."
> |
> | This application worked fine before. Moreover, if I remove the
> impersonation
> | line from the web.config, everything is find again except of course

things

> | that required the impersonation fail.
> |
> | Does anyone know why this happens? Better yet, anyone know how to fix

it?

> |
> | Thanks in advance!
> | Michael
> |
> |
> |
> |
>
>

[Hidulf]

I got the same problem after SP4, seems the SP4 got some update on the
IIS and some file have been replaced, so the ASP.NET system file is
removed from the web server.

I try to reinstall the .net framework 1.1 again and it works for me.

Michael Kennedy [UB] wrote:

> Hi Everyone,
>
> Last night we installed SP4 on our Windows 2000 Advanced Server which was
> are using as an ASP.NET web server (.NET 1.1). This morning we found out
> that our ASP.NET applications that use impersonation. That is from the
> web.config:
>
> <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD" />
>
> fail with the message "Access Denied: Failed to start monitoring
> c:\inetpub\wwwroot\myapp\default.aspx for changes."
>
> This application worked fine before. Moreover, if I remove the impersonation
> line from the web.config, everything is find again except of course things
> that required the impersonation fail.
>
> Does anyone know why this happens? Better yet, anyone know how to fix it?
>
> Thanks in advance!
> Michael
>
>
>

[M B]

"John Saunders" <john.saunders@surfcontrol.com> wrote in message news:<eIdVneOPDHA.2480@tk2msftngp13.phx.gbl>...

> It's impressive how quickly MS has addressed this issue.
>
> I would also be impressed if someone would tell me how we were supposed to
> know about this problem? There's a HUGE list of bug fixes in SP4. Were we
> supposed to read every one of those KB articles?

Gee, maybe by reading the documents that are prominently listed on the main
SP4 web page? The ones that Microsoft says all users should read? Only four
documents are listed, and anybody who installs SP4 really should read all four:

System Requirements
Readme File
Release Notes
Windows 2000 SP4 FAQ

Here's what that page says about the Release Notes:

Release Notes for Windows 2000*Service*Pack*4
See this article in the Microsoft Knowledge Base for release notes
and information about known issues. Read these notes carefully
before you install SP4.

The phrase "known issues" should cause any decent admin to realize
that they really should read the info, as Microsoft recommends. The
link for the Release Notes is:

[url]http://support.microsoft.com/?kbid=813432[/url]

You did read those notes carefully before you installed SP4, right?
If so, you would have seen a very short page, listing eight items that
represent differences in SP4 that might cause you problems. The
very first one is this, under "Application Compatability":

821546 Some Programs That Use Impersonation Do Not
Work Correctly After You Install Windows 2000
Service Pack 4

Seemed very clear to me. It's already on our "investigation list" as we plan
to rollout SP4.

Microsoft's track record with reliability and lack of problems with Windows
Service Packs may be improving, but it's not perfect. You should always
read the available documentation first, even if you want to be on the
bleeding edge, and install it on the first day it's available.

[Michael Kennedy [UB]]

Hi,

Ah interesting. Maybe I will try reinstalling ASP.NET. Does anyone know the
command to refresh the install of ASP.NET without completely uninstalling
and then reinstalling the .NET Framework?

Thanks,
Michael

"Hidulf" <hidulf@netscape.net> wrote in message
news:3EFDD539.9060303@netscape.net...

> I got the same problem after SP4, seems the SP4 got some update on the
> IIS and some file have been replaced, so the ASP.NET system file is
> removed from the web server.
>
> I try to reinstall the .net framework 1.1 again and it works for me.
>
> Michael Kennedy [UB] wrote:

> > Hi Everyone,
> >
> > Last night we installed SP4 on our Windows 2000 Advanced Server which

was

> > are using as an ASP.NET web server (.NET 1.1). This morning we found out
> > that our ASP.NET applications that use impersonation. That is from the
> > web.config:
> >
> > <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD"

/>

> >
> > fail with the message "Access Denied: Failed to start monitoring
> > c:\inetpub\wwwroot\myapp\default.aspx for changes."
> >
> > This application worked fine before. Moreover, if I remove the

impersonation

> > line from the web.config, everything is find again except of course

things

> > that required the impersonation fail.
> >
> > Does anyone know why this happens? Better yet, anyone know how to fix

it?

> >
> > Thanks in advance!
> > Michael
> >
> >
> >

>

[Michael Kennedy [UB]]

Hi David,

Thanks. Yeah, they added some new, tighter security which some of the other
posts mentioned. I'm still having issues with them but I think I may need to
try some more.

Regards,
Michael


"David Adner" <davidadner@yahoo.com> wrote in message
news:3EFFB6DE.9113EE51@yahoo.com...

> Check out the release notes. They mention new User Rights surrounding
> impersonations.
>
> "Michael Kennedy [UB]" wrote:

> >
> > Hi Everyone,
> >
> > Last night we installed SP4 on our Windows 2000 Advanced Server which

was

> > are using as an ASP.NET web server (.NET 1.1). This morning we found out
> > that our ASP.NET applications that use impersonation. That is from the
> > web.config:
> >
> > <identity impersonate="true" userName="DOMAIN\USER" password="PASSWORD"

/>

> >
> > fail with the message "Access Denied: Failed to start monitoring
> > c:\inetpub\wwwroot\myapp\default.aspx for changes."
> >
> > This application worked fine before. Moreover, if I remove the

impersonation

> > line from the web.config, everything is find again except of course

things

> > that required the impersonation fail.
> >
> > Does anyone know why this happens? Better yet, anyone know how to fix

it?

> >
> > Thanks in advance!
> > Michael