English Community

Software and Operating SystemLenovo Patch for SCCM
All Forum Topics
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 1 of 11

ADR Sync Error 0x87d20417

2020-04-10, 19:26 PM

For sometime now, I am getting ADR Sync Error 0x87d20417.    The ADR fails to execute.   If i manually run the rule ad-hoc, the software update group and deployments are created but still reports error.  

 

I have recreated the ADR and same error occurs.     I have removed all but just a handful of known good products (i.e. 7-Zip and Adobe) and the errors still occur.   I upgraded to the latest version of Lenovo Patch on 3/4/2020.   The Lenovo Patch settings have been verified to have the latest internal cod-signing cert and it is valid cert and not expired.

 

SMS Rules Engine reports failure:    Content download failed.  Message: Failed to download one or more content files.  Source: SMS Rule Engine.

 

Additionally, AutoPublish.log appears to be downloading everything in the catalog instead of just the items we have approved for download/deployment (sample attached).   

 

Reply
Options

1576 Posts

03-03-2016

US

3790 Signins

45343 Page Views

  • Posts: 1576
  • Registered: ‎03-03-2016
  • Location: US
  • Views: 45343
  • Message 2 of 11

Re:ADR Sync Error 0x87d20417

2020-04-14, 12:25 PM

@skg_002 ,

 

In regards to the ADR, does the rulesengine.log give further information about what did not download, in terms of content source?  Also, can you confirm you are seeing the published Third Party Updates in the All Software Updates node?

 

In the Autopublish.log, I just see that it is downloading and publishing BlueJeans.  Lenovo Patch will only download and publish updates that meet your criteria in either a Smart Filter or Composite Filter, or updates selected manually.

 

TLawson

 

Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 3 of 11

Re:ADR Sync Error 0x87d20417

2020-04-14, 22:44 PM

The RuleEngine.log does indeed have references to specific UpdateID's that are failing download from internet, Greenshot and multiple Adobe products to name a few.   I removed all Adobe products and Greenshot from the ADR and the rule completes successfully.   

 

I am using an internal code-signing cert issued by our internal CA, that expires annually.  It expires annually.

 

It appears that the issue with Greenshot is an old digital certificate that did not get re-signed and published.   The Adobe updates appear to have the new digital certificate.  I am creating a new ADR with just Adobe and will see if I can replicate the issue.
 

 

 

 

 

Reply
Options

1576 Posts

03-03-2016

US

3790 Signins

45343 Page Views

  • Posts: 1576
  • Registered: ‎03-03-2016
  • Location: US
  • Views: 45343
  • Message 4 of 11

Re:ADR Sync Error 0x87d20417

2020-04-16, 13:40 PM

@skg_002 

 

OK, lets see what happens.

 

TLawson

Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 5 of 11

Re:ADR Sync Error 0x87d20417

2020-04-29, 20:39 PM

To follow-up, I was able to track down all of the errors in the RuleEngine.log to re-sign and re-publish these updates within the Lenovo Published Third-Party Updates node.   The ADR now completes with success.

 

  1.   In tracing the updates, I noticed that the older cab files, with the old digital signature, stored under the WsusContent\xx\ directory does not get deleted.   Do you know if this will eventually get deleted and if so when/how?

 

2.  The last update that I have under the Lenovo Patch view is from  4/14, for example, I have not gotten the last 2 Google Chrome Updates.   Is there way to force a check for latest updates?   In the past, this corrects itself after a server reboot.    I've run manual syncs without any change.

 

 

 

Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 6 of 11

Re:ADR Sync Error 0x87d20417

2020-04-29, 21:19 PM
Additional info... there are 2 updates with failures in the autoPublish.log (Adobe Reader X and Adobe Digital Editions). Warning: Skipping update 82340531-fc24-45e1-855c-570b6f8943bd because it is not in the current catalog AutoPublish 4/29/2020 4:12:07 PM 7 (0x0007) Warning: Skipping update a13607b5-b1f5-44a3-8a06-7c3130b01668 because it is not in the current catalog AutoPublish 4/29/2020 4:12:07 PM 7 (0x0007)
Reply
Options

1576 Posts

03-03-2016

US

3790 Signins

45343 Page Views

  • Posts: 1576
  • Registered: ‎03-03-2016
  • Location: US
  • Views: 45343
  • Message 7 of 11

Re:ADR Sync Error 0x87d20417

2020-04-30, 18:37 PM
@skg_002 To clarify, did you click Re-sign then Republish, or just Re-sign? 1.) If you Re-signed then Republished, then that creates a new revision of the update. Those will eventually clear out based on SCCM following its expire, tombstone, cleanup, and delete routine. It could be around a month or so. When using the Re-sign button, the plugin will find the selected updates and Re-sign them without the need of a republish action. Once the Re-sign is complete, WSUS will need to complete a synchronization with SCCM, which will need to be initiated by the administrator. Here is a link to the KB which contains the User Guide. Page 161 will help guide an administrator through Re-signing updates and other steps needed to deploy the Re-signed updates. 2.) In regards to obtaining the latest catalog for the Third Party Updates, this should be occurring when closing and opening the console or clicking the Refresh button on the Lenovo Patch view. 3.) I will try to find out more information about the 2 missing updates in the AutoPublish.log file, but I would guess that they were removed and replaced by a newer version, as I cannot find them in my catalog. Can you provide any other information regarding the updates, like the version from the title or the bulletin? TLawson
Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 8 of 11

Re:ADR Sync Error 0x87d20417

2020-05-01, 19:28 PM

Yes, i re-signed and re-published because I did not see the stored cab file update.  I see now that extra step was not required.

 

I am continuing to see errors with the catalog sync in the AutoPublish.log.  Restarting the server did not resolve. 

 

It looks like it is trying to auto-publish 199 updates but failing with error 2147942405 (Access Denied). Here is a sample of one of the errors:

 

Wireshark-win64-2.6.16.exe - CreateCab 100% AutoPublish 5/1/2020 12:31:26 PM 20 (0x0014)

Publishing 'Wireshark 2.6.16 x64' 9b7a2693-4f9f-40b6-886b-eeacebb3505e. AutoPublish 5/1/2020 12:31:26 PM 20 (0x0014)

Error Publishing ''Wireshark 2.6.16 x64' 9b7a2693-4f9f-40b6-886b-eeacebb3505e' : Failed to sign package; error was: 2147942405   1/1/1601 12:00:00 AM 2956135264 (0xB0330B60)

Failed to sign package; error was: 2147942405 AutoPublish 5/1/2020 12:31:26 PM 20 (0x0014)

Failed to publish 'Wireshark 2.6.16 x64'   revision 0 AutoPublish 5/1/2020 12:31:26 PM 20 (0x0014)

 

 

Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 9 of 11

Re:ADR Sync Error 0x87d20417

2020-05-01, 19:31 PM
The end of the log results show this: Publishing complete. 0 of 199 updates were successfully published. AutoPublish 5/1/2020 12:43:53 PM 36 (0x0024) Error - AutoPublish returned code 8: Failed to publish all packages AutoPublish 5/1/2020 12:43:53 PM 36 (0x0024)
Reply
Options

40 Posts

07-28-2018

US

66 Signins

558 Page Views

  • Posts: 40
  • Registered: ‎07-28-2018
  • Location: US
  • Views: 558
  • Message 10 of 11

Re:ADR Sync Error 0x87d20417

2020-05-04, 21:16 PM

Still struggling with this...  The good news is that the newer patches are now visible in the Lenovo Patch view since the weekend.... they were not there last week.   A large number have "Failed" status in the "Latest not-published" filter.    When I manually publish selected updates, some updates now publish as expected and folders are created in the E:\WSUS\UpdateServicesPackages folder but not all of them. Others, fail with a "could not find [...\UpdateServicesPackages\cabfile]."   The failures appears to be arbitrary... even within the same vendor.  I checked with permission for service account and everything appears to be in order.    Suggestions?  

 

Sample:  

Beginning publication of 'Nitro Pro 10.5.9.9 x64' a6ebd653-d167-4319-8876-a2c53f4cff85 en (1 of 1) AutoPublish 5/4/2020 8:23:16 AM 5 (0x0005)

SCCM Server: MYSERVER.MYDOMAIN.COM AutoPublish 5/4/2020 8:23:17 AM 1 (0x0001)

Known revisions:  WSUS=3  SMS=3 AutoPublish 5/4/2020 8:23:17 AM 5 (0x0005)

Error Publishing ''Nitro Pro 10.5.9.9 x64' a6ebd653-d167-4319-8876-a2c53f4cff85' :   1/1/1601 12:00:00 AM 3509722416 (0xD1321D30)

Could not find file '\\MYSERVER.MYDOMAIN.com\UpdateServicesPackages\a6ebd653-d167-4319-8876-a2c53f4cff85\70615605-b84d-4826-a34a-21c5f83d065f_1.cab'. AutoPublish 5/4/2020 8:23:17 AM 5 (0x0005)

Failed to publish 'Nitro Pro 10.5.9.9 x64' en revision 3 AutoPublish 5/4/2020 8:23:18 AM 5 (0x0005)

Publishing complete.  0 of 1 updates were successfully published. AutoPublish 5/4/2020 8:23:18 AM 5 (0x0005)

Error - AutoPublish returned code 8:  Failed to publish all packages AutoPublish 5/4/2020 8:23:18 AM 5 (0x0005)

 

 

 

Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete