G
Guest
Hi,
System.Diagnostics.Process.GetCurrentProcess().ProcessName fails for a
caller with minimal privilege on Windows 2003 Server:
System.InvalidOperationException - Couldn't get process information from
remote machine.
System.ComponentModel.Win32Exception - Access is denied.
It works ok on Windows 2000 Professional.
A web search concerning this issue suggests that this is considered to be a
bug in 2003 Server in some quarters. The only work-around that I've come
across so far is to grant the caller access to the performance counters.
This is unacceptable.
Can anyone suggest another way for a caller with minimal privilege to
discover the name of the Win32 process within which it is executing? I don't
mind if it involves Interop, just as long as it works with minimal privilege.
Thanks
David Razzetti
System.Diagnostics.Process.GetCurrentProcess().ProcessName fails for a
caller with minimal privilege on Windows 2003 Server:
System.InvalidOperationException - Couldn't get process information from
remote machine.
System.ComponentModel.Win32Exception - Access is denied.
It works ok on Windows 2000 Professional.
A web search concerning this issue suggests that this is considered to be a
bug in 2003 Server in some quarters. The only work-around that I've come
across so far is to grant the caller access to the performance counters.
This is unacceptable.
Can anyone suggest another way for a caller with minimal privilege to
discover the name of the Win32 process within which it is executing? I don't
mind if it involves Interop, just as long as it works with minimal privilege.
Thanks
David Razzetti