You're letting a lot of bad links creep onto that page. Do a Google
search for "genesis world energy". The second item found is a broken
link to the newsroom. (The third item found explains how the page you
are working on is a stock fraud scam.)

Bump.

"V. Jenks" <spam@scientifik.com> wrote in message news:<033201c32f98$c27cf750$a501280a@phx.gbl>...
> I'm using an XmlTextWriter to write an xml file to disk.
> No matter what I do with the permissions and aspnet user,
> it will not allow me to write a file!
>
> My error:
>
> Exception Details: System.UnauthorizedAccessException:
> Access to the path "C:\Inetpub\www_genesis\proposal" is
> denied.
>
> ASP.NET is not authorized to access the requested
> resource. Consider granting access rights to the resource
> to the ASP.NET request identity. ASP.NET has a base
> process identity (typically {MACHINE}\ASPNET on IIS 5 or
> Network Service on IIS 6) that is used if the application
> is not impersonating. If the application is impersonating
> via <identity impersonate="true"/>, the identity will be
> the anonymous user (typically IUSR_MACHINENAME) or the
> authenticated request user.
>
> To grant ASP.NET write access to a file, right-click the
> file in Explorer, choose "Properties" and select the
> Security tab. Click "Add" to add the appropriate user or
> group. Highlight the ASP.NET account, and check the boxes
> for the desired access.
>
> ---Now, I have done this, the aspnet user has full
> control to that folder, including write permissions. I
> even went as far as to give the aspnet user full control
> over my entire C: drive, just to see if that would help,
> no such luck.
>
> I'm not using impersonation, that is also not the issue.
>
> I've tried this on 2 different servers and it isn't
> working anywhere. I used to have this problem w/ .net
> 1.0 and I would give the aspnet user write permissions to
> the directory I'm trying to write to - everything would
> work just fine.
>
> Now that I'm using .net 1.1 I'm seeing that this isn't
> working at all, is the framework the problem? is there
> some sort of security issue with the new 1.1 release
> preventing me from writing a file?
>
> Thanks for your help!