Config Baseline for KBs in error state 80072EE2

I have a configuration baseline that is checking for the following 2 patches:

  • KB2834140
  • KB2670838

These are prerequisite patches for IE 11 (which we are beginning to roll out). I wanted to try to address machines that don't have the updated ahead of IE 11 deployment. I created a single configuration baseline that looks for the x86 and x64 patches, then deployed that to all my workstations.

I was kind of surprised to see the number of machines that have error 80072EE2 (which is an HTTP timeout). I presume that the timeout is trying to reach MS updates, but I can't find a log that points me in that direction. The DcmWmiProvider.log has the following entries:

Initialize called for the provider	UDAProvider	5/28/2015 8:05:38 AM	4608 (0x1200)
CreateInstanceEnumAsync called for the provider	UDAProvider	5/28/2015 8:05:38 AM	4608 (0x1200)
CreateInstanceEnumAsync called for the provider	UDAProvider	5/28/2015 8:05:44 AM	4608 (0x1200)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:06:37 AM	3600 (0x0E10)
ScanForUpdate called in the provider	DcmSUMProvider	5/28/2015 8:06:37 AM	3600 (0x0E10)
Adding error code: (0x80072ee2) for Job:F74CEB40-B92A-4A78-973D-D0C3A4662821	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed in discovering instance. 
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed to do HandleCreateInstanceEnumAsync(). 
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Failed to process CSUMProvider::GExecQueryAsync. 
Unknown error (Error: 80072EE2; Source: Unknown)	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExtractLanternJobID Succeeded	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
Job: F74CEB40-B92A-4A78-973D-D0C3A4662821 already had error returned earlier. Returning the same error.	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)
ExecQueryAsync Failed	DcmSUMProvider	5/28/2015 8:07:58 AM	3600 (0x0E10)

I'd like to understand what DCM is doing here, and what next steps would be, but I'm a little stuck on where to go from here. Pointers would be appreciated.

May 29th, 2015 8:39am

0x80072EE2 = "Operation Timed Out"

Have you reviewed WindowsUpdate.log for corresponding activity?

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 1:23pm

I hadn't. I'll check the WindowsUpdate log on another PC. My 2 test devices have miraculously started working.

I guess what I'd really like is some information on the process behind how configuration baselines work for software updates. The documentation on TechNet seems a little light.

My assumption was be that the baseline would use data from the Software Updates scan cycle to determine compliance. Since both test devices were receiving patches, I had no reason to believe that the scan cycle would be failing.

May 29th, 2015 3:04pm

I hadn't. I'll check the WindowsUpdate log on another PC. My 2 test devices have miraculously started working.

<...>

My assumption was be that the baseline would use data from the Software Updates scan cycle to determine compliance. Since both test devices were receiving patches, I had no reason to believe that the scan cycle would be failing.

If your check into the windowsupdate.log reveals stuff like: WARNING: ISusInternal::

Your WSUS (SUP) could be needing some maintenance done on it.

We had a very sketchy problem, scans weren't always failing, nor always succeeding, patching was happening but not reliably. Client would sometimes be fine, othertimes would timeout with this error.

Free Windows Admin Tool Kit Click here and download it now
May 29th, 2015 5:33pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics