Re: command prompt: 'tasklist' logon failure

Excellent post, Scott! Thanks for the update.

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
Windows® Troubleshooting http://www.winhelponline.com


"sfeeser" <sfeeser@xxxxxxxxxxx> wrote in message news:1184863317.688119.188600@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have successfully solved the problem.

The root of the problem was actually DCOM, which caused WMI to fail,
which caused tasklist to fail (msinfo32 showed the "wmi missing" error
message on the main tab). Checked all the obvious WMI problems and
performed many of the commonly posted WMI fixes like delete/rebuild
repository, re-register associated WMI .dll and .exe files, etc. and
nothing worked. Then I came across a very useful tool from MS called
WmiDiag.vbs. It produces an extremely detailed set of reports about
everything related to WMI. After studying these logs for some time,
it became apparent the issue was an incorrect permission in DCOM that
caused WMI to run at the wrong permission level. Anyhow, the final
solution was setting "local_access" and "local_launch" permissions for
the "everyone" user in DCOM default permissions.

The error was my fault, in the process of configuring other software
tools that use DCOM for remote solution processes, I set remote access
and remote launch for the everyone user and apparently cleared the
local access permissions. Wow, what a headache for clearing one
checkbox!

Scott




.

Relevant Pages

  • DCOM Error 10016 after installing SP2
    ... to retrieve data from a SQL Server 2000 database on a Windows 2003 Server. ... Event Source: DCOM ... The application-specific permission settings do not grant Local Activation ... Activation and Remote Activation in the Launch Permissions dialog box (Edit ...
    (microsoft.public.windowsxp.general)
  • Re: command prompt: tasklist logon failure
    ... The root of the problem was actually DCOM, which caused WMI to fail, ... caused WMI to run at the wrong permission level. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Registy access via WMI in C#
    ... I am just trying to understand why you are hooked on WMI. ... you cannot accomplish otherwise, do not use it. ... Most likely it is DCOM, ... >>> of our applications is to update the Windows registry on a remote host ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Credentials via Locator Object
    ... When using the Locator object to make a connection to WMI with different credentials, is the name/password encrypted for remote calls via DCOM? ...
    (microsoft.public.windowsxp.wmi)
  • WMI wouldnt start. My fix.
    ... >Local Activation permission for the COM Server ... WMI wouldn't start. ... >>on..using the Dependencies tab in it's service. ... >>9) close the window with OK, then click on the MSDTC tab ...
    (microsoft.public.windowsxp.wmi)