H
hoochiegooch
All,
I posted a message here recently regarding the difficulty
I'm having with CreateProcessWithLogonW() in an ASP.NET
application. I get the following Win32 error:
Error 183: Cannot create a file when that file already exists.
I thought it was Win2K3 or IIS6 giving me grief, but it
appears to behave the same way on a WinXP/IIS5 system.
I impersonated a domain admin and even wrote a small
test console app that is launched and logs the current
user info. This runs when spawned from another console
app (and has the correct new impersonation), but never
works from the ASP.NET app.
Is this kind of thing not permitted, no matter what
rights the user may have? I'm almost tempted to
create a simple .NET Remoting setup to do this
(and turn the 2nd app into a remoting server --
singleton -- which could work fine), but that seems
like a silly way to go.
Any ideas? I can provide more info if needed.
Thanks!
bn
I posted a message here recently regarding the difficulty
I'm having with CreateProcessWithLogonW() in an ASP.NET
application. I get the following Win32 error:
Error 183: Cannot create a file when that file already exists.
I thought it was Win2K3 or IIS6 giving me grief, but it
appears to behave the same way on a WinXP/IIS5 system.
I impersonated a domain admin and even wrote a small
test console app that is launched and logs the current
user info. This runs when spawned from another console
app (and has the correct new impersonation), but never
works from the ASP.NET app.
Is this kind of thing not permitted, no matter what
rights the user may have? I'm almost tempted to
create a simple .NET Remoting setup to do this
(and turn the 2nd app into a remoting server --
singleton -- which could work fine), but that seems
like a silly way to go.
Any ideas? I can provide more info if needed.
Thanks!
bn