Click here to Skip to main content
13,558,743 members
Rate this:
Please Sign up or sign in to vote.

I posted this question on an article just now but I don't know how many people would see it there:
Process Information and Notifications using WMI[^]

So anyway. Many of the concepts I am using are explained in the article but here is my problem:

It just so happens that I have implemented almost identical code in a testing process monitor I have written. I use the code to keep an eye on any child (and [great]*grand kids) of a test process I have started. I do this because I need to know when the entire process completes and so I can kill any child processes if the test times out.

This code works fine 99.9% of the time but I am getting some rare errors specifically on Windows 7 computers and servers.
testing the code on my own windows 7 machine often gives me most common error which is "Exception from HRESULT: 0xFFFFFFFF" but LastWin32Error is 1008:
An attempt was made to reference a token that does not exist.

Here is the code that triggers the error:
    const string queryString = "SELECT *" +
                               "  FROM __InstanceOperationEvent " +
                               "WITHIN  " + pol +
                               " WHERE TargetInstance ISA 'Win32_Process' ";

    MachineName = ".";
    // You could replace the dot by a machine name to watch to that machine
    const string scope = @"\\.\root\CIMV2";

    // create the watcher and start to listen

    _watcher = new ManagementEventWatcher(scope, queryString);
_watcher.EventArrived += WatcherOnEventArrived;
    _watcher.Start(); // ERROR

Is would appear that once this error occurs once then it is almost certain to happen the next several times I try, so try-catch-retry code doesn't help.

Any ideas what I can do to get by this or look into it further?

Posted 3-Mar-13 23:42pm
Updated 5-Mar-13 0:02am
Jegan Thiyagesan 5-Mar-13 7:06am
I tried your source code in my x64 W7 machine, I did not see any exceptions yet. I even enabled all the exceptions but could not reproduce.

Andy Lanng 19-Mar-13 12:35pm
I usually have to run the code several times before I get the error myself but when this is in use it could be called many times over and over again (not from the same instance)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web02 | 2.8.180515.1 | Last Updated 5 Mar 2013
Copyright © CodeProject, 1999-2018
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100