Unable to read from/write to a text file.

From: bill charrette (jmial@ipopper.net)
Date: 09/30/02 

From: "bill charrette" <jmial@ipopper.net>
Date: Sun, 29 Sep 2002 17:10:28 -0700

Environment: Windown XP Pro, IIS 5.1, ASP

My IIS NTFS permissions don't allow the anonymous
internet user to write to a text file. In other words,
when a user tries to access or write to a text (.txt)
file from an ASP web page I get the following error:

HTTP 403.9 - Access Forbidden: Too many users are
connected Internet Information Services.

Web Sharing Properties: Access Permissions: "Read and
Write". Application Permissions: "Scripts"

Any ideas how I can change the NTSF permissions?

Relevant Pages

  • .mdb used with IIS > security?
    ... It's used on ASP pages via ODBC. ... I tried to remove the "Everyone" on the permissions and then only added ... the specific users as well as the IUSR_servername with Modify rights. ... internet user doesn't have the appropriate rights. ...
    (microsoft.public.access.security)
  • Unable to read from/write to a text file.
    ... Windown XP Pro, IIS 5.1, ASP ... My IIS NTFS permissions don't allow the anonymous ... internet user to write to a text file. ...
    (microsoft.public.inetserver.iis.security)
  • Re: .mdb used with IIS > security?
    ... But there a different db files in that folder and I don't want that ALL ... ASP web application. ... > i take it you are talking about Folder permissions? ... >>internet user doesn't have the appropriate rights. ...
    (microsoft.public.access.security)
  • Re: FolderExists and UNC path
    ... Traditionally ASP uses the IUSR_account so try mapping a drive using that username and password or assigning permissions to that account or changing to a different one if you don't know or can't change the password. ... When I ran this command from the server logged with my user it ...
    (microsoft.public.scripting.vbscript)
  • Re: Running vbs from WSH in ASP page
    ... > When I run the vbs from the command line all is well. ... > When I fire it from an ASP page ... I have a feeling it is> permissions based. ... > Set oShell = Nothing ...
    (microsoft.public.scripting.wsh)