Process attaching is not possible on Windows 2003 Server - "Permission Denied"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start ospy
2. Select "Capture" and then "Attach to process"

What is the expected output? What do you see instead?
"Permission denied - you need to run ospy with administrative privileges in
order to do this"  Although I am logged on as "administrator".

What version of the product are you using? On what operating system?
1.10.4 on Windows 2003 Server, Standard Edition, Service Pack 2 

Please provide any additional information below.
I suppose ospy needs a hook for windows 2003 so it looks for the "system"
user instead of "administrator"?

Original issue reported on code.google.com by tom.vand...@gmail.com on 17 Nov 2009 at 11:30

[GoogleCodeExporter]

Hmm... Did you try explicitly launching oSpy as Administrator? (By 
right-clicking on 
the executable and "Run as administrator"?) oSpy doesn't check the username 
you're 
running as, but handles an exception typically thrown by insufficient 
permissions.

Original comment by ole...@gmail.com on 15 Mar 2010 at 12:38

[GoogleCodeExporter]

Original comment by ole...@gmail.com on 15 Mar 2010 at 12:39

• Changed state: Accepted

[GoogleCodeExporter]

Original comment by ole...@gmail.com on 15 Mar 2010 at 12:41

[GoogleCodeExporter]

same issue in vista

Original comment by d...@drown.the.cat on 15 Mar 2010 at 8:54

[GoogleCodeExporter]

Do you have any AV software installed?

Original comment by ole...@gmail.com on 15 Mar 2010 at 8:56

[GoogleCodeExporter]

no AV, software firewall but hasn't caused problems of this nature before, UAC 
is off
though, that could be the issue.

Original comment by d...@drown.the.cat on 15 Mar 2010 at 9:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Ok. I haven't tested with UAC off in a long time, so that could possibly be an 
issue.

Original comment by ole...@gmail.com on 15 Mar 2010 at 9:05

[GoogleCodeExporter]

If turning UAC back on doesn't help, could you try disabling the software 
firewall just 
in case?

Original comment by ole...@gmail.com on 15 Mar 2010 at 9:06

[GoogleCodeExporter]

disabled the firewall to no effect, uac requires a restart which I won't be 
able to
do for a long time

Original comment by d...@drown.the.cat on 15 Mar 2010 at 9:11

[GoogleCodeExporter]

Ok, thanks. I'll leave this issue open for the time being, I might come across 
a 2k3 
system to test on at some point.

Original comment by ole...@gmail.com on 15 Mar 2010 at 9:29

[GoogleCodeExporter]

Same issue with UAC, with and without choosing "run as administrator". If you 
build a
debug version that logs the return values/exceptions thrown I'll try it.

Original comment by d...@drown.the.cat on 16 Mar 2010 at 1:44

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Version I built works! Replaced the original binary in the original directory 
and it
still works. No idea what the problem was.

Original comment by d...@drown.the.cat on 16 Mar 2010 at 2:37

[GoogleCodeExporter]

Hmm.. strange. System-wide binary blacklisting of some kind?

Original comment by ole...@gmail.com on 6 May 2010 at 10:33

[GoogleCodeExporter]

I solved this problem.
Simply select the folder in which oSpy is installed.
Right click and select Properties > Security Tab > Edit > Add > Advanced > Find 
Now >

Double Click on "SYSTEM" in "Search Results" > OK
Set Permissions for SYSTEM to Full Control > OK > OK

Attaching now works perfectly!

Original comment by niche...@gmail.com on 14 Feb 2011 at 1:07