I am unsure but same as gWaldo said it may be a setting in the Local Security Policy
i believe that you need to enable Impersonate a client after authentication (i may be wrong)
From Microsoft
To work around this problem, verify
that the ASPNET account has the
correct user rights as follows:
%windir%\Microsoft.NET\Framework\Version\Temporary
ASP.NET Files: Full Control
%windir%\Temp: Full Control
Application folder: Read
%installroot% hierarchy (for example,
%windir%\Microsoft.Net\Framework\Version):
Read
%windir%\Assembly: Read
Note This is the global assembly
cache. You cannot directly use Windows
Explorer to edit ACLs for this folder.
Instead, open a command window, and
then run the following command:
cacls %windir%\assembly /e /t /p
domain\useraccount:R
Alternatively, before you use Windows
Explorer, run the following command to
unregister Shfusion.dll: regsvr32–u
shfusion.dll
After you set user rights in Windows
Explorer, run the following command to
re-register Shfusion.dll: regsvr32
shfusion.dll
Web site root (for example,
%root%\Inetpub\Wwwroot) or the path
that the default Web site points to:
Read %windir%\System32: Read
(Typically, the ASPNET account has
already been granted user rights as a
member of the Users group.)