I get tasklist.exe and taskkill.exe: ERROR: Not Found

4,377 views
Skip to first unread message

FMDRA

unread,
Apr 8, 2008, 5:10:25 PM4/8/08
to Windows XP
When running WinXP with the lastest service pack (SP2) Home, I'm
getting the following error:

command pormpt> tasklist
ERROR: Not Found

I DO have tasklist.exe installed. It is in windows\system32. When I
type
command prompt> tasklist /?
I get the regular help message.

Thank you


Jack Hubbs

unread,
Apr 9, 2008, 10:52:23 AM4/9/08
to Wind...@googlegroups.com
Take a look at the /? options.  My question to you is what context are you running the command?  If you are not running as an administrator you may get the error.  Try using the /u options when you run the command.

Jack

FMDRA

unread,
Apr 15, 2008, 10:05:16 PM4/15/08
to Windows XP
I'm just typing tasklist at the command prompt and it outputs the
error. Here are the results of the commands I have tried after your
input.

C:\Documents and Settings\...>tasklist
ERROR: Not found.

C:\Documents and Settings\...>tasklist /u MyUser
ERROR: Invalid Syntax. /U can be specified only when /S is specified.
Type "TASKLIST /?" for usage.

C:\Documents and Settings\...>tasklist /u MyUser /s
MyMachine'sNetbiosName
ERROR: The RPC server is unavailable.

C:\Documents and Settings\...>


On Apr 9, 10:52 am, "Jack Hubbs" <hub...@gmail.com> wrote:
> Take a look at the /? options. My question to you is what context are you
> running the command? If you are not running as an administrator you may get
> the error. Try using the /u options when you run the command.
>
> Jack
>

marty39

unread,
Apr 16, 2008, 5:20:22 AM4/16/08
to Windows XP
If Windows XP could not find the command "tasklist" you would see a
message like:

'tasklist' is not recognized as an internal or external command,
operable program or batch file.

Instead you're seeing a message of the same form as all the other
error messages from tasklist.
Evidently the message:

ERROR: Not found

is coming from tasklist itself. Tasklist is complaining that it can't
find something -- what, I don't know.

Jack Hubbs

unread,
Apr 16, 2008, 1:39:53 PM4/16/08
to Wind...@googlegroups.com
Check and see if your "Remote Procedure Call (RPC)" service is running.  From the DOS prompt type NET START and look at the list.  If it is not started go into Services and start it, or you can type from the DOS prompt:  NET START "Remote Procedure Call (RPC)".  You need to include the quote marks.  After it is started try your tasklist command again.

Good luck,

Jack

tec...@gmail.com

unread,
Apr 16, 2008, 5:55:38 PM4/16/08
to Windows XP
I believe both of those executables were left out of the Home Edition
of Windows XP.

You get Not Found because they are really not on your system.

FMDRA

unread,
Apr 16, 2008, 10:04:53 PM4/16/08
to Windows XP
This is not true. In similar windows system (also home and also
version 2002) the command works.

FMDRA

unread,
Apr 22, 2008, 12:54:01 AM4/22/08
to Windows XP
I really don't know, why my post is not published. I have written this
three times, but anyway, sorry for the late reply,

the RPC procedure IS running. It is listed when the net start command
is called.

Thanks anyway for your help.

On Apr 16, 1:39 pm, "Jack Hubbs" <hub...@gmail.com> wrote:
> Check and see if your "Remote Procedure Call (RPC)" service is running.
> From the DOS prompt type NET START and look at the list. If it is not
> started go into Services and start it, or you can type from the DOS prompt:
> NET START "Remote Procedure Call (RPC)". You need to include the quote
> marks. After it is started try your tasklist command again.
>
> Good luck,
>
> Jack
>

marty39

unread,
Apr 23, 2008, 11:26:41 AM4/23/08
to Windows XP
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.
Reply all
Reply to author
Forward
0 new messages