Patch Management Solution

 View Only
  • 1.  PM 7.1 error

    Posted Jan 05, 2012 04:47 PM

    Hi all

     

    I have a problem with Patch Management 7.1c. I keep getting the following error:

    Log File Name: C:\ProgramData\Symantec\SMP\Logs\a.log
    Priority: 1
    Help and Support:
    Date: 05/01/2012 22:31:46
    Tick Count: -1582054281
    Host Name: xxxxxxxx
    Process: w3wp (35344)
    Thread ID: 17
    Module: w3wp.exe
    Source: Altiris.PatchManagement.Policies.VendorPolicyWindows.BuildClientConfigXml
    Description: No rows returned by spPMWin_GetConfigInfoForSoftwareUpdate for Software Update WindowsXP-KB2544893-v2-ENU.exe (02f46416-b13f-4491-9a07-ea8b2689214c)

    I have tried to do a new import and revise, still same error.  
     



  • 2.  RE: PM 7.1 error

    Posted Jan 14, 2012 08:32 AM
      |   view attached

    Hi there, we have the same problem, with 7.1 sp2

    I've try to recreate bulletin and remove policy  but in logs we have this error 

    Log File Name: C:\ProgramData\Symantec\SMP\Logs\a.log
    Priority: 1
    Help and Support:
    Date: 14/01/2012 13:57:00
    Tick Count: 72755062
    Host Name: xxx
    Process: w3wp (3468)
    Thread ID: 120
    Module: w3wp.exe
    Source: Altiris.PatchManagement.Policies.VendorPolicyWindows.BuildClientConfigXml
    Description: No rows returned by spPMWin_GetConfigInfoForSoftwareUpdate for Software Update Windows6.1-KB2572076-x86.msu (ae7d1137-21d7-43bc-b3f8-b264ca72294f)

     

    on the machine i've this situation

    bulletin name is blanc

     


     


     



  • 3.  RE: PM 7.1 error

    Posted Jan 18, 2012 05:34 PM

    Seems this issue is spawning from the spPMWin_GetConfigInfoForSoftwareUpdate   stored procedure. I have an open case with Symantec support right now. If I have or don't have a solution to this problem I will let you know In the mean time I plan on digging into the profiler and manually kicking of this stored procedure so I can see firsthand what is happening.



  • 4.  RE: PM 7.1 error

    Posted Jan 20, 2012 01:04 PM

    The root cause is a bug in two Patch Management .dll files, as well as a stored procedure.  Patch Management, in its wisdom, may delete superseded bulletins from the database whether you tell it to - or not.  Symantec gave us a new spPMWin_GetConfigInfoForSoftwareUpdate stored procedure.  The fixed .dll files are included in SP2, but I'm not sure about the stored procedure.  This is defintely due to a bug in the product that you will have to work with Symantec support to fix.



  • 5.  RE: PM 7.1 error

    Posted Jan 24, 2012 05:42 PM

    Patch Management 7.1 SP2

    Crossing my fingers but it seems like my issue has been resolved with the help of Symantec's support team. We did the following:

    • Repaired the Patch Management Solution
    • Re-Imported all patches but unchecked Incremental Import

    I really think re-importing the patches with Incremental Import unchecked cleared up any issues I was having. This includes the issues with the compliance bulletins having incorrect data or no data at all.



  • 6.  RE: PM 7.1 error

    Posted Feb 06, 2012 06:55 AM

    The solution from Delmore works for me. But in my case it was not necessary to repair the patch management solution. The only step was to "Re-Import all patches but unchecked incremental import".



  • 7.  RE: PM 7.1 error

    Posted Apr 25, 2012 02:22 PM

    For a client today, Microsoft was missing as a product.  7.1 SP2.  We clicked 'Update' so that Microsoft appeared as a product; unchecked Incremental; ran PMImport immediately.  3-4 hours later, PMImport completed a full import and successfully imported the bulletins and updates for Microsoft, thus resolving this issue.