Patch Management Solution

 View Only
  • 1.  Error trying to apply some updates

    Posted Jan 03, 2014 10:55 AM

    Hi everyone

    I have a big problem with some update bulletins..

    it is trying to apply on schedule but always end with an error number:

    when a ran those bulletins by hand I get a message saying that already have this bulleting installed

     

    This issue happens with this bulletings on windows xp and 7 professional both 32 bits:

    MS13-080
    MS13-A05
    MSWU-781
    MSWU-772
    MS13-A04
    MS13-006
     

    im getting a lot of pcs pending for this updates on the compliance report and i need to get them up to date ASAP 'cause will have a security audit in few days.

    By the way... i have this config on my NS server:

     

    OS: Windows 2008 R2 sp 1

    NS 7.1

    pmimport version: 7.1.472  (i didn't download the lastest version yet, 'cause i want to get all pcs up to date before install more updates so non get behind)

     

    *---------------------------------------------------*

    here is some data from the client log:

    <event date="Jan 03 10:37:14" severity="1" hostName="EDSUAREZ" source="SoftwareUpdateAgent" module="PatchMgmtAgents.dll" process="AeXNSAgent.exe" pid="1588" thread="264" tickCount="93249909"><![CDATA[Failed to apply software update [MS13-A05]:Windows6.1-KB2862966-x86.msu]]></event>

    <event date="Jan 03 10:37:14" severity="4" hostName="EDSUAREZ" source="SoftwareUpdateAgent" module="PatchMgmtAgents.dll" process="AeXNSAgent.exe" pid="1588" thread="264" tickCount="93249909"><![CDATA[Advertisement {8E5D25AF-7DE5-41A2-9E57-D0FBC42ADFB3} completed status (5) exitcode (2359302)]]></event>

    <event date="Jan 03 10:37:13" severity="4" hostName="EDSUAREZ" source="ProgramExec" module="smfagent.dll" process="AeXNSAgent.exe" pid="1588" thread="4556" tickCount="93248412"><![CDATA[Program 'Windows6.1-KB2829104-x86.msu for MS13-002, MS13-011, MS13-029, MS13-033, MS13-056, MS13-060, MS13-062, MS13-063, MS13-070, MS13-071, MS13-072, MS13-074, MS13-...' completed. Exit code=2359302]]></event>

     

    Thanx for your help



  • 2.  RE: Error trying to apply some updates

    Posted Jan 07, 2014 12:50 PM

    Hello luisgoca,

    The only time I've seen this behavior across the board for all updates failing to install is when they were updating the same product (e.g. .NET or something like that) and the product itself was not installed correctly or had a corrupt install. However, it doesn't appear that these updates are related, for they do not update the same products. This could be a problem with the targeting rules for the updates themselves.

    Additional checks: 

    1. The 'Pending' status leads to something that has not synced up between the client and the SMP server; please view KM: TECH127676, for it provides some direction with troubleshooting this issue.

    2. View KM: TECH141928, for it outlines updates stuck in scheduled status following install attempts.

    3. View the Known Issue outlined on KM: TECH204204, for if the Patch Filters are not updating properly on the SMP it may be inappropriately targeted.

    4. Review Client logs during Windows System Assessment Scan and ensure inventories are processing as outlined on KM: HOWTO60750

    If these checks are in order and the product is still behaving this way; ensure a recent PMImport has ran, for that will replicate to the client and ensure the needed IsApplicable/IsInstalled Updates data is in order (Note: you can utilize the parameters on the Compliance Reports to exclude the new release of updates to ensure your environment is Compliant up to last month as you outlined).

    With it affecting multiple non-associated updates; it appears like it is a problem with the client software installation, or the client communications to the SMP, or even the SMP communications with the Database for that client inventories; however, if the current PMImport and these checks do not resolve; please open a support case to review the rules for those updates. The KM: HOWTO60789 assists with data needed to be gathered in full to help us review the rules for IsApplicable / IsInstalled.