search cancel

Import Patch Data Replication for Windows completes; Child SMP unable to manage Software Update deployment

book

Article ID: 163870

calendar_today

Updated On:

Products

Patch Management Solution for Windows

Issue/Introduction

Reviewed the Software Update Policies/Packages are managed and deployed on the Parent Symantec Management Platform (SMP) Server.

Confirmed the Import Patch Data Replication for Windows is configured correctly on the Parent SMP per HOWTO95152 and completes successfully; however, the Child SMP Server is unable to manage Software Update deployment, the Child SMP Log Viewer is full of errors, and the Client's are not receiving the policies/packages.

 

Unable to generate policy XML for item: 'Lync2010-x64-KB3188397.msp for MS16-120' (652bc9d7-4b90-478a-ba19-7574d20ac6c2), resource: 04c6ee7c-0ee8-440a-a5f2-2ac1013fb6ab

Unable to build the client configuration XML for advertisement with guid {652bc9d7-4b90-478a-ba19-7574d20ac6c2}. Reason: Did not get a row for Software Delivery Advertisement "Lync2010-x64-KB3188397.msp for MS16-120", Guid = {652bc9d7-4b90-478a-ba19-7574d20ac6c2} from the SWD tables

SoftwareUpdateAdvertisement::base.OnBuildClientConfigXml2() Unable to build the client configuration XML for advertisement with guid {652bc9d7-4b90-478a-ba19-7574d20ac6c2}. Reason: Did not get a row for Software Delivery Advertisement "Lync2010-x64-KB3188397.msp for MS16-120", Guid = {652bc9d7-4b90-478a-ba19-7574d20ac6c2}

Environment

Patch Management 7.5.x & 7.6.x

Cause

Sometimes a timing issue can cause patch packages to replicate before their policy items and break their association. By design patch packages only replicate once and thus the situation does not fix itself on future replications.

Resolution

Work through the following resolution:

  1. Manually flag the recent patches to be replicated again on the next replication by running the following SQL query, and set the number by the comment to specify within how many days old the patch packages can be to be flagged for replication:

begin tran
select * from replicationitem
update replicationitem
set isreplicable =1
where guid
in (
select guid from vitem where classguid ='0CEC577A-0319-401E-A0A4-36ADABD0BE05' and CreatedDate > getdate () -30)
--Set this number of days

  1. Run the following SQL Script to execute the above script when confirmed successfully ran:

​​commit

After running the query wait for replication to run overnight then confirm that the patches start deploying and the errors stop.

Review the following articles if further troubleshooting is required: