hi,
a good way to troubleshoot such problems is to used auditing.
1. enable "object access" auditing in the local security policy
(success/failure)
2. enable auditing on the temp dir -> folder properties -> security ->
advanced -> auditing -> add -> everyone, full control : success/failure
then
ed discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] On Behalf Of Adrian Bateman
Sent: Dienstag, 20. Januar 2004 08:26
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] XmlSerializer problem through WebService
Rick,
If it isn't a file permission problem as Jon suggests, then i
Hi,
I had a similar problem under IIS 6 - when I used a custom account as
process identity.
my custom account had no read/write rights on the temp assembly dir
check the acls on C:\DOCUME~1\USPSCR~1\ASPNET\LOCALS~1\Temp\
in my case it was (w2k3) -> c:\windows\temp
bye
dominick
-Original M
] On Behalf Of Jon Flanders
> Sent: 19 January 2004 23:43
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] XmlSerializer problem through
> WebService
>
> In my experience this is almost always an ACL issue, that the
> ASPNET user cannot read or write to the correct directo
In my experience this is almost always an ACL issue, that the ASPNET user
cannot read or write to the correct directories.
Usually the directory in question is c:\winnt\temp. But in your case it
appears to be in documents and settings\aspnet. I'd do two things:
1) Give the ASPNET user access to
