I think the RPC message is irrelevant.
I have Windows XP Home on which I recently installed tasklist.exe.
When I invoke it without any arguments it spits out a list of running
processes, without any complaints.
When I tack on the /s argument with a remote or invalid system name it
gives me:
ERROR: The RPC server is unavailable.
even though tasklist runs OK without arguments.
When I use both the /u argument and /s with the local system name it
says:
WARNING: User credentials cannot be used for local connections.
and then it spits out a list of locally running processes.
If you got the RPC message then maybe you didn't correctly specify the
local system.
So the message
ERROR: Not Found
must mean something else. Maybe some DLL is missing, or a DLL has been
replaced by a version that doesn't have a required entry point. I
don't know any efficient way to identify that kind of error.