Quantcast
Channel: Configuration Manager 2007 Software Updates Management forum
Viewing all articles
Browse latest Browse all 700

Software updates hung ‘Waiting for another installation to complete’

$
0
0

Hi

I have a problem where a set of machines in our environment (about 100 out of 8000 total) are failing to apply Windows Updates as they are currently hung attempting to install prior update(s). If I run the report ‘Last 1000 messages for a specific computer (Errors and Warnings)’ on affected machines I can see messages such as:

Failed to download contents for update b24f5f88-b7a2-42d2-bd30-28deed69fcce. The operating system reported error -2147023436: This operation returned because the timeout period expired.

The problem I’m seeing looks very similar to that described here http://blogs.technet.com/b/configurationmgr/archive/2011/08/23/troubleshooting-a-configuration-manager-2007-installation-of-office-2010.aspx but what’s confusing me is that, according to the blog article, update b24f5f88-b7a2-42d2-bd30-28deed69fcce is Access Runtime MUI SP1 which is bundled with Office 2010 SP1. If I create a Search Folder in the SCCM console to query Unique Update IDs and enter the Unique ID for the update, I get no results. If I query the Unique ID for Office 2010 SP1 it returns the update, but I’m not distributing Office 2010 SP1 in any deployments, which is confirmed when I click on the Deployment Status tab for Office 2010 SP1.

When I look at the CAS log on this particular affected client, I see:

Location update from CTM for content 87804958-b464-405c-a87b-2eaf0e7bb692.1 and request {CE0DD543-BA02-4297-9B4E-CA29CE79C4A0}                ContentAccess  20/11/2013 12:42:40        4372 (0x1114)

Download request only, ignoring location update             ContentAccess  20/11/2013 12:42:40        4372 (0x1114)

Location update from CTM for content b24f5f88-b7a2-42d2-bd30-28deed69fcce.1 and request {E03E11FC-514E-4A29-B23B-2A3C6D58EB3D}                ContentAccess  20/11/2013 12:42:40        5312 (0x14C0)

Download request only, ignoring location update             ContentAccess  20/11/2013 12:42:40        5312 (0x14C0)

Location update from CTM for content 87804958-b464-405c-a87b-2eaf0e7bb692.1 and request {CE0DD543-BA02-4297-9B4E-CA29CE79C4A0}                ContentAccess  20/11/2013 13:42:47        4904 (0x1328)

Download request only, ignoring location update             ContentAccess  20/11/2013 13:42:47        4904 (0x1328)

Location update from CTM for content b24f5f88-b7a2-42d2-bd30-28deed69fcce.1 and request {E03E11FC-514E-4A29-B23B-2A3C6D58EB3D}                ContentAccess  20/11/2013 13:42:47        6140 (0x17FC)

Download request only, ignoring location update             ContentAccess  20/11/2013 13:42:47        6140 (0x17FC)

Location update from CTM for content 87804958-b464-405c-a87b-2eaf0e7bb692.1 and request {CE0DD543-BA02-4297-9B4E-CA29CE79C4A0}                ContentAccess  20/11/2013 14:42:52        4144 (0x1030)

Download request only, ignoring location update             ContentAccess  20/11/2013 14:42:52        4144 (0x1030)

Location update from CTM for content b24f5f88-b7a2-42d2-bd30-28deed69fcce.1 and request {E03E11FC-514E-4A29-B23B-2A3C6D58EB3D}                ContentAccess  20/11/2013 14:42:52        4144 (0x1030)

Download request only, ignoring location update             ContentAccess  20/11/2013 14:42:52        4144 (0x1030)

As per the blog article, this indicates I have no distribution point with the required content available. I copied the Unique IDs for the requests rather than the Updates from the CAS log and added this column into the view under Deployment Management in the SCCM console but I get zilch searching for those IDs.

Could it be that the clients are attempting to download content for a deployment that no longer exists? I’m at a loss to figure out how to resolve the problem as I can’t understand which deployment(s) the client(s ) are attempting to download the content for.

Thanks in advance


Viewing all articles
Browse latest Browse all 700

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>