Re: ASP.NET app permissions

From: www.VoiceInformation.com (AMichalik_at_gmail.com)
Date: 06/13/05


Date: 13 Jun 2005 13:27:13 -0700


"Failed to start monitoring file changes" - Watch out for fix described
in http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317955

I was trying to install a Web Mail C# VS.Net project onto one of our
Windows 2000 development machines. Through a painful trial and error
process, I found a series of operations that fixed a problem similar to
yours.

I am going to include the whole chain here so that you can see it in
reference to the other issues.

1) It all started when I built a VS.Net project that ran successfully
on my local machine. When I loaded it onto the Windows 2000 server, and
I went to my site www.TekGuard.com (without specifying \Default.aspx).
The default page was set up correctly in IIS. Then when I specified
\Default.aspx, I would get "Failed to start monitoring file changes".

Problem #1) The browser returned "This Page Cannot Be Displayed", and
IIS logs showed a 403 Error the root directory (ex: www.TekGuard.com),
even though I had set up Default.aspx in IIS under the virtual web
"Documents" | "Enable Default Documents".
I was also getting "Failed to start monitoring file changes" when I
would actually get into the app and run the code within the site.
I tried to fix it using the instructions from
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q317955 (I did
not need to touch any of the subdirectories - the permissions were
inherited automatically). That fixed the "Failed to start monitoring
file changes", but did not fix the fact that I could not access the
default homepage using the root address (i.e., without specifying
\Default.aspx)

Fix #1) "All Tasks" | "Permissions Wizard" | "Select new security
settings from a template" | "Public Web Site". Now I could access the
default homepage using the root address www.TekGuard.com without
specifying \Default.aspx.

2) This then broke my ability to admin the site when on the IIS
machine. I would get "You are not authorized to view this page"
whenever I tried to invoke the admin tools that use SharePoint.

Problem #2) "All Tasks" | "Check Server Extensions 2002" "You are not
authorized to view this page"

Fix #2a) Go to Properties | Directory Security | Edit (Authentication
Methods), Check "Integrated Windows Authentication" is checked

Fix #2b) In a separate instance, but on a related note, after
installing Windows 2003 SP1, I found I could not admin the sites from
the IIS Server machine, and would get the "You are not authorized to
view this page". In this case, I could successfully admin the site from
a remote computer using FrontPage.
I made the fix from
http://support.microsoft.com/default.aspx?scid=kb;en-us;896861

1. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
2. Right-click Lsa, point to New, and then click DWORD Value.
3. Type DisableLoopbackCheck, and then press ENTER.
4. Right-click DisableLoopbackCheck, and then click Modify.
5. In the Value data box, type 1, and then click OK.

This allowed me to admin the site both from the local IIS machine and
remotely.

#3) When I went to edit portions of the site using FrontPage, FrontPage
said I did not have permission to save the file changes.

Problem #3) FrontPage authoring permissions denied access.

Fix #3) I went back onto the IIS machine, and for the site ran "All
Tasks" | "Check Server Extensions 2002" Detect and Repair.

Now everything seems to be operating normally!

---------------------------------------------------------------------------------------------
Toll Free Automated Attendant Follow-Me Integrated Messaging:
www.VoiceInformation.com
---------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------
Free Mail Server, Anti-Spam Server & PlugIn, Free Source, Unlimited
Users/Domain: www.TekGuard.com
---------------------------------------------------------------------------------------------



Relevant Pages

  • Re: IIS ASP.NET 2.0 Bug
    ... problem SO YOU CAN FIX IT. ... I will obviously not be fixing IIS even if I ... I did appreciate your help in telling me how to turn Casini off. ... The purpose, when you debug, is to identify problems. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: MS01-035 Hot Fix for IIS
    ... MS01-035 Hot Fix for IIS ... was identified in the patch for MS01-035 last week. ... Further, if the administrator does select it for installation, a ...
    (Bugtraq)
  • Re: ISA Event
    ... external interface so would no longer be in conflict with the ISA listeners. ... listeners and IIS bound to the same interface. ... It is in no way SBS specific. ... > The fix you reckon works didn't. ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: RWW. OWE. Possible DNS Issue. Page Cannot Be Displayed Prob
    ... the easiest fix would probably be to run the ICW ... then focus on the web listeners within ISA. ... IIS for that matter. ... It has worked great until a contractor messing with IIS on the server - i ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Error 2147023570
    ... The fix is not posted on our site. ... Please do not send email directly to this alias. ... >>Call PSS and ask to speak to an engineer on the IIS ... >>Microsoft Exchange Support ...
    (microsoft.public.exchange.clients)