• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
Locked
0

Unable to Publish Adobe Flash Updates into SCCM

New Here ,
Apr 16, 2019 Apr 16, 2019

Copy link to clipboard

Copied

I am having problems publishing the Adobe Flash Player updates for this month into SCCM for three clients. When I attempt to publish the updates, the SMS_ISVUPDATES_SYNCAGENT.log file shows the following:

[81, PID:12628][04/17/2019 11:38:03] :PollingWorkMonitor: There are 1 jobs that are pending in the jobs table.         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[81, PID:12628][04/17/2019 11:38:03] :PollingWorkMonitor: Starting job 72057594037927978 for subject ed98bae3-afcc-4bb4-9225-7674acf77f0b.         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[81, PID:12628][04/17/2019 11:38:03] :Creating a new SyncUpdate work item for update ed98bae3-afcc-4bb4-9225-7674acf77f0b, jobid is 72057594037927978         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[81, PID:12628][04/17/2019 11:38:03] :Launcher : About to start work item: SyncUpdate.         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[73, PID:12628][04/17/2019 11:38:03] :SyncUpdate: ed98bae3-afcc-4bb4-9225-7674acf77f0b - No synchronization record for update with id ed98bae3-afcc-4bb4-9225-7674acf77f0b was found, only updates synchronized by Configuration Manager can have update content published to WSUS by Configuration Manager.         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[73, PID:12628][04/17/2019 11:38:03] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_NO_METADATA).         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[73, PID:12628][04/17/2019 11:38:03] :STATMSG: (SRVMSG_SMS_ISVUPDATES_SYNCAGENT_UPDATECONTENT_FAIL).         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[73, PID:12628][04/17/2019 11:38:04] :Launcher : Work item SyncUpdate has completed queued time was 00:00:00.0460115 run time was 00:00:00.0739981         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

[73, PID:12628][04/17/2019 11:38:04] :SyncUpdate: ed98bae3-afcc-4bb4-9225-7674acf77f0b - Completed.         1/01/1601 12:00:00 AM    13432428 (0xCCF66C)

Views

1.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 17, 2019 Apr 17, 2019

Copy link to clipboard

Copied

We're investigating.  Will post back soon.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Apr 18, 2019 Apr 18, 2019

Copy link to clipboard

Copied

LATEST

The behavior you're experiencing isn't an issue with the SCUP catalog.  While Adobe did change the vendor name in the catalog in the most recent release, it's not the cause of the error you're seeing.

The following may be of assistance in your troubleshooting:

https://support.microsoft.com/en-us/help/10680/software-update-management-troubleshooting-in-configu...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines