469,319 Members | 2,408 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,319 developers. It's quick & easy.

Impersonation on Windows 2003 Server

Does a user being impersonated within and ASP.NET application (using
programatic impersonation) on a Windows 2003 Server machine need any
different privileges or policies than the same ASP.NET user and application
running under Windows XP. I am using a set of classes that expose the COM
Windows TaskScheduler. When I try to instantiate the COM class within an
ASP.NET Application on Windows 2003 Server, I get an access denied, but not
when running under Windows Xp.

Thanks,
craig
Nov 18 '05 #1
2 1524
in Windows Server 2003 the process that runs your web apps is called wp3.exe
and the user account is "Network Service". This account does not by default
have permissions to create COM objects (which involves accessing the
registry). The TaskSchedulerAPI tries to write a file to a directory (don't
remember where) in the operating system. You may be getting an "Access
Denied" error because "Network Service" does not have permissions to this
system folder.

"Craig Neuwirt" wrote:
Does a user being impersonated within and ASP.NET application (using
programatic impersonation) on a Windows 2003 Server machine need any
different privileges or policies than the same ASP.NET user and application
running under Windows XP. I am using a set of classes that expose the COM
Windows TaskScheduler. When I try to instantiate the COM class within an
ASP.NET Application on Windows 2003 Server, I get an access denied, but not
when running under Windows Xp.

Thanks,
craig

Nov 18 '05 #2
I neglected to say that the account I am using for impersonation is in the
Administrator group. Therefore, it should be able to write to any
directory. I am wondering if it is more of a permission/policy problem than
a true access problem.

thanks,
craig
"Jorge Matos" <Jo********@discussions.microsoft.com> wrote in message
news:EB**********************************@microsof t.com...
in Windows Server 2003 the process that runs your web apps is called wp3.exe and the user account is "Network Service". This account does not by default have permissions to create COM objects (which involves accessing the
registry). The TaskSchedulerAPI tries to write a file to a directory (don't remember where) in the operating system. You may be getting an "Access
Denied" error because "Network Service" does not have permissions to this
system folder.

"Craig Neuwirt" wrote:
Does a user being impersonated within and ASP.NET application (using
programatic impersonation) on a Windows 2003 Server machine need any
different privileges or policies than the same ASP.NET user and application running under Windows XP. I am using a set of classes that expose the COM Windows TaskScheduler. When I try to instantiate the COM class within an ASP.NET Application on Windows 2003 Server, I get an access denied, but not when running under Windows Xp.

Thanks,
craig

Nov 18 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Mark | last post: by
reply views Thread by Wim Hollebrandse | last post: by
1 post views Thread by Matt Tapia | last post: by
4 posts views Thread by David Cablalero | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by mdpf | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.