Error 80041002 is loged on an WMI query.


  • I have found this error in the WMI logs file (C:\WINDOWS\system32\wbem\Logs\wbemcore.log)

    (Fri Jul 06 09:31:32 2007.160820187) : Error 80041002 occured executing request for CancelProvAsyncCall for sink 06B707C0
    (Fri Jul 06 09:31:32 2007.160820187) : CAsyncReq_CancelProvAsyncCall call failed

    The code used to make the querry is in C#:
    using System;
    using System.Collections.Generic;
    using System.Management;
    connected = false;
       string query = string.Format("SELECT NetConnectionStatus, MACAddress FROM Win32_NetworkAdapter");
       using (ManagementObjectSearcher searcher = new ManagementObjectSearcher(query))
          if (searcher.Get().Count > 0)
             connected = true;
    catch (Exception ex)
       Console.WriteLine("Error occured in query.");

    The error is logged each time the process executing the code above terminates.
    runing as administrator does not help
    The program work has expected but I would like to know if there is a way to get rid of this error in the logs.

    Friday, July 06, 2007 5:40 PM

All replies

  • My wbemcore.log is flooded with this same message although everything appears to be working properly in my SMS 2003 environment.


    Error 80041002 occurred executing request for CancelProvAsyncCall for sink XXXXXXXX
    CAsyncReq_CancelProvAsyncCall call failed.


    I have rebuilt my WMI namespaces, checked and rechecked DCOM security, re-registered dll's, opened a case with Microsoft...still getting the errors. Perhaps the error is nothing to worry about but if anyone has any ideas, send them my way. 


    Monday, December 10, 2007 4:32 PM
  • I know this is a bit old, but did you/anybody ever get an resolution to this problem?  I get this error only as a certain user when querying a specific table (Win32_Service), which is really friggin strange because it works as another user, and the same user with same security does not get the error on a different computer.  I've done everything I can think of, but it just refuses to play nice =/  Testing with wbemtest

    To summarize, accessing computer remotely:
    Computer1 + User1 + Win32_Service = Generic WMI Failure  0x80041001
    Computer1 + User1 (logged in locally and executing locally) + Win32_Service = Success
    Computer1 + User1/2 + Win32_Process = Success
    Computer1 + User2 + Win32_Service = Success

    Computer2 + User1/2 + Win32_Service = Success

    Computer1 == Computer2 in terms of security settings (all via GPO/VBS)

    Thanks for any ideas.
    • Edited by TBKdan Monday, June 30, 2008 3:06 PM Local login/execute works fine
    Monday, June 30, 2008 2:56 PM