publishing SCUP 2011 updates to WSUS/SCCM are failing

Hi, i'm using SCUP 2011 to publish some Dell driver updates to my ConfigMgr server. However, after creating a self signed certificate based on the installation instructions publishing updates keeps failing. I'm testing it all on 1 VM with all roles installed locally: SCCM, WSUS and SCUP. Importing catalogs and assigning them is not an issue. Just when i want to publish a group of assigned updates i keep getting the error stating that publishing has failed. I tried creating a new self signed certificate, tried to import it in Trusted Publishers and Trusted Root Certification Authorities. Tried using the WSUS self signed certificate to be used in SCUP. However no succes. Below is a snippet of the SCUP logfile. Can anyone point me in the right direction?

Thanks in advance!

 

Log file snippet:

=============================================================================================

 

TestConnection: Verifying current update server settings...$$<Updates Publisher><Thu May 26 6:23:35.122 2011.1><thread=1>

Connecting to a local update server with locally detected settings.$$<Updates Publisher><Thu May 26 6:23:35.124 2011.1><thread=1>

TestConnection: Verification succeeded.$$<Updates Publisher><Thu May 26 6:23:35.187 2011.1><thread=1>

Settings: Applying settings changes.$$<Updates Publisher><Thu May 26 6:23:37.660 2011.1><thread=1>

Current settings:$$<Updates Publisher><Thu May 26 6:23:37.809 2011.1><thread=1>

    Setting: SCUP Database File: <default> C:\Users\Administrator\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000\scupdb.sdf$$<Updates Publisher><Thu May 26 6:23:37.812 2011.1><thread=1>

    Setting: WSUS Publishing Enabled: True$$<Updates Publisher><Thu May 26 6:23:37.814 2011.1><thread=1>

    Setting: WSUS Publishing is configured to use local server.$$<Updates Publisher><Thu May 26 6:23:37.815 2011.1><thread=1>

    Setting: ConfigMgr Integration Enabled: True$$<Updates Publisher><Thu May 26 6:23:37.817 2011.1><thread=1>

    Setting: Configuration Manager integration is configured to use local server.$$<Updates Publisher><Thu May 26 6:23:37.819 2011.1><thread=1>

    Setting: Configuration Manager client threshold is 1$$<Updates Publisher><Thu May 26 6:23:37.820 2011.1><thread=1>

    Setting: Configuration Manager client threshold is disabled (0).$$<Updates Publisher><Thu May 26 6:23:37.822 2011.1><thread=1>

    Setting: Proxy Server settings used: False$$<Updates Publisher><Thu May 26 6:23:37.823 2011.1><thread=1>

    Setting: CRL Checking Enabled: False$$<Updates Publisher><Thu May 26 6:23:37.824 2011.1><thread=1>

    Setting: CheckCatalogSubscriptionsOnStartup: True$$<Updates Publisher><Thu May 26 6:23:37.825 2011.1><thread=1>

    Setting: Always check for local update content before downloading : False$$<Updates Publisher><Thu May 26 6:23:37.827 2011.1><thread=1>

Settings: user closed dialog.$$<Updates Publisher><Thu May 26 6:23:37.828 2011.1><thread=1>

Workspace: Settings dialog has completed.$$<Updates Publisher><Thu May 26 6:23:37.849 2011.1><thread=1>

Publications workspace: Starting publish wizard for publication 'Dell Updates'.$$<Updates Publisher><Thu May 26 6:23:40.277 2011.1><thread=1>

    Publish: Preparing list of selected updates for publishing.$$<Updates Publisher><Thu May 26 15:23:42.878 2011.9><thread=9>

    Connecting to a local update server with locally detected settings.$$<Updates Publisher><Thu May 26 15:23:42.879 2011.9><thread=9>

    Publish: Update server name: SCOM$$<Updates Publisher><Thu May 26 15:23:42.908 2011.9><thread=9>

    Publish: Publish operation starting for 1 updates.$$<Updates Publisher><Thu May 26 15:23:42.909 2011.9><thread=9>

    Publish: Publish: Verifying update server is configured with a certificate prior to publishing.$$<Updates Publisher><Thu May 26 15:23:42.910 2011.9><thread=9>

    Publish: Publish: Update server appears to be configured with a certificate.$$<Updates Publisher><Thu May 26 15:23:43.44 2011.9><thread=9>

    Building dependency graph for update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')'$$<Updates Publisher><Thu May 26 15:23:43.157 2011.9><thread=9>

    No dependencies found for update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')'$$<Updates Publisher><Thu May 26 15:23:43.224 2011.9><thread=9>

Found total of 0 dependencies (may include duplicates).$$<Updates Publisher><Thu May 26 15:23:43.225 2011.9><thread=9>

PublishItem: Update ''AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')'' has no dependencies.$$<Updates Publisher><Thu May 26 15:23:43.225 2011.9><thread=9>

PublishItem: Publishing update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')'.$$<Updates Publisher><Thu May 26 15:23:43.225 2011.9><thread=9>

PublishItem: --- Evaluating software update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')' for publishing as MetadataOnly.$$<Updates Publisher><Thu May 26 15:23:43.226 2011.9><thread=9>

PublishItem: --- Software update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')' needs to be published (no content).$$<Updates Publisher><Thu May 26 15:23:43.505 2011.9><thread=9>

PublishItem: --- Metadata only SDP XML file for publishing created at C:\Users\Administrator\AppData\Local\Temp\tmp5B2C.tmp$$<Updates Publisher><Thu May 26 15:23:44.517 2011.9><thread=9>

PublishItem: --- Calling update server API for publishing update 'AMD RADEON HD3470 256M, V.8.701.0.0000, A09 XP/VISTA/WIN7_8.701 WITH DUP (UpdateId:'f25a7d05-8d1b-4e7b-992f-33b6d5958b7b' Vendor:'Dell' Product:'Drivers and Applications')'$$<Updates Publisher><Thu May 26 15:23:44.648 2011.9><thread=9>

2011-05-26 13:23:47.071 UTC Error Scup2011.9 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Cannot access a closed Stream.

   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)

   at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)

   at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)

   at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)

   at Scup.Wizards.PublishOperation.Start()

   at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)

   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()$$<Updates Publisher><Thu May 26 15:23:47.71 2011.9><thread=9>

PublishItem: InvalidException occurred during publishing: Cannot access a closed Stream.$$<Updates Publisher><Thu May 26 15:23:47.258 2011.9><thread=9>

Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.$$<Updates Publisher><Thu May 26 15:23:47.259 2011.9><thread=9>

Publish: Background processing completed.$$<Updates Publisher><Thu May 26 6:23:47.260 2011.1><thread=1>

 

May 26th, 2011 4:38pm

I seem to remember having the same issue (not 100%), if all the certificates are in the correct stores on the site server and you have enable the self signing GPO then try a restart. The restart was the working part for my problem. Not the most technical correct answer (I know), but it worked.
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 4:54pm

I am in the same position as above, however the Win08 Svr R2 (x64) that I have SCUP 2011 installed is in the correct OU where the Self signed cert is applied

this is what I get from the SCUP2011 Publish Software Updates Wizard

Publishing Summary
Fatal errors occurred during publish operation. View log For more details.
1 updates were selected for publish.
1 updates failed to be published. View log  for more details.
1 updates (includes dependencies) failed to due to general error.
Anything further on this would be greatly appreciated

May 26th, 2011 7:08pm

Hello,

You must install the required WSUS 3.0 SP2 hotfix on both your SCUP and WSUS computers (as well as all WSUS servers in your environment) from: http://support.microsoft.com/?kbid=2530678

I have a quick getting started guide here as well: http://blogs.technet.com/b/jasonlewis/archive/2011/05/24/getting-started-with-updates-publisher-2011.aspx 

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2011 7:20pm

Well, i installed the hotfix, enabled the GPO, re-created the certificates and re-imported them and rebooted but still no luck:

Logfile snippet:

===================================================================

PublishItem: Update ''Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'' has no dependencies.$$<Updates Publisher><Fri May 27 10:45:33.973 2011.15><thread=15>

PublishItem: Publishing update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'.$$<Updates Publisher><Fri May 27 10:45:33.974 2011.15><thread=15>

PublishItem: --- Evaluating software update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' for publishing as FullContent.$$<Updates Publisher><Fri May 27 10:45:33.974 2011.15><thread=15>

PublishItem: --- Software update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' needs to be published with full content.$$<Updates Publisher><Fri May 27 10:45:33.985 2011.15><thread=15>

PublishItem: Retrieving content for update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'.$$<Updates Publisher><Fri May 27 10:45:34.219 2011.15><thread=15>

PublishItem: --- Content will be saved to C:\Users\Administrator\AppData\Local\Temp\\esn0ygyn.qjb\install_flash_player_10_active_x.msi.$$<Updates Publisher><Fri May 27 10:45:34.220 2011.15><thread=15>

PublishItem: Download Content: file was downloaded successfully.$$<Updates Publisher><Fri May 27 10:45:38.357 2011.15><thread=15>

PublishItem: Successfully retrieved content for software update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')' to local file: C:\Users\Administrator\AppData\Local\Temp\\esn0ygyn.qjb\install_flash_player_10_active_x.msi$$<Updates Publisher><Fri May 27 10:45:38.358 2011.15><thread=15>

File C:\Users\Administrator\AppData\Local\Temp\\esn0ygyn.qjb\install_flash_player_10_active_x.msi appears to be signed, retrieved certificate, checking signature...$$<Updates Publisher><Fri May 27 10:45:40.992 2011.15><thread=15>

TrustChecker: User trusts file.$$<Updates Publisher><Fri May 27 10:45:47.302 2011.1><thread=1>

Adding certificate to trusted publishers.$$<Updates Publisher><Fri May 27 10:45:47.342 2011.1><thread=1>

PublishItem: --- SDP XML file for publishing created at C:\Users\Administrator\AppData\Local\Temp\tmp9148.tmp$$<Updates Publisher><Fri May 27 10:45:49.470 2011.15><thread=15>

PublishItem: --- Calling update server API for publishing update 'Adobe Flash Player 10.3.181.14 (UpdateId:'59cd0358-0d28-477f-a546-89ea84cbb6c8' Vendor:'Adobe Systems, Inc.' Product:'Adobe Flash Player')'$$<Updates Publisher><Fri May 27 10:45:49.610 2011.15><thread=15>

2011-05-27 08:46:01.546 UTC Info Scup2011.15 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback$$<Updates Publisher><Fri May 27 10:46:1.546 2011.15><thread=15>

2011-05-27 08:46:01.547 UTC Info Scup2011.15 CabUtilities.CheckCertificateSignature File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402$$<Updates Publisher><Fri May 27 10:46:1.547 2011.15><thread=15>

2011-05-27 08:46:01.548 UTC Info Scup2011.15 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed$$<Updates Publisher><Fri May 27 10:46:1.548 2011.15><thread=15>

2011-05-27 08:46:06.789 UTC Error Scup2011.15 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Cannot access a closed Stream.

   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)

   at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)

   at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)

   at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)

   at Scup.Wizards.PublishOperation.Start()

   at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)

   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)

   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)

   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()

   at System.Threading.ThreadPoolWorkQueue.Dispatch()

   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()$$<Updates Publisher><Fri May 27 10:46:6.789 2011.15><thread=15>

PublishItem: InvalidException occurred during publishing: Cannot access a closed Stream.$$<Updates Publisher><Fri May 27 10:46:7.336 2011.15><thread=15>

Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.$$<Updates Publisher><Fri May 27 10:46:7.338 2011.15><thread=15>

Publish: Background processing completed.$$<Updates Publisher><Fri May 27 10:46:7.339 2011.1><thread=1>

May 27th, 2011 11:49am

forget my previous reply :-), it finally works after i installed the hotfix!

It's important to know that the hotfix changes the way the self signed certificate is created. I found out that the self signed certificate that are created must be configured with "Code Signing" as a property "Intended Purposes". The hotfix will take care of that. Without the hotfix the purpose property is configured as "All". So keep in mind that re-creation, re-importing of the self signed certificate and at last a reboot is needed before you can publish updates. 

@ Jason, thanks!

note: i will mark this reply as an answer because it also contains instructions about the certificate recreation. 


  • Marked as answer by Dutch guy Friday, May 27, 2011 9:14 AM
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2011 12:12pm

forget my previous reply :-), it finally works after i installed the hotfix!

It's important to know that the hotfix changes the way the self signed certificate is created. I found out that the self signed certificate that are created must be configured with "Code Signing" as a property "Intended Purposes". The hotfix will take care of that. Without the hotfix the purpose property is configured as "All". So keep in mind that re-creation, re-importing of the self signed certificate and at last a reboot is needed before you can publish updates. 

@ Jason, thanks!

note: i will mark this reply as an answer because it also contains instructions about the certificate recreation. 


  • Marked as answer by Dutch guy Friday, May 27, 2011 9:14 AM
May 27th, 2011 12:12pm

forget my previous reply :-), it finally works after i installed the hotfix!

It's important to know that the hotfix changes the way the self signed certificate is created. I found out that the self signed certificate that are created must be configured with "Code Signing" as a property "Intended Purposes". The hotfix will take care of that. Without the hotfix the purpose property is configured as "All". So keep in mind that re-creation, re-importing of the self signed certificate and at last a reboot is needed before you can publish updates. 

@ Jason, thanks!

note: i will mark this reply as an answer because it also contains instructions about the certificate recreation. 


  • Marked as answer by Dutch guy Friday, May 27, 2011 9:14 AM
Free Windows Admin Tool Kit Click here and download it now
May 27th, 2011 12:12pm

This seems to work fine for Metadata but the minute I attempt to do full it fails.  I am not sure what I am missing here.  I even recreated the certs again after the hotfix install, and I cannot publish full content, only metadata.

 

Any thoughts?

June 6th, 2011 8:50pm

Hi, did you solve this issue, (can´t publish updates, fatal error) I am having the same problem, justo like PaulTM
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 6:22pm

This is what i get on the log

 

System Center Update Publisher starting up...$$<Updates Publisher><Thu Jun 9 10:25:15.780 2011.1><thread=1>
Building database connection string.$$<Updates Publisher><Thu Jun 9 10:25:16.467 2011.1><thread=1>
No database file information found in configuration file, using default database file name 'scupdb.sdf' in folder 'C:\Users\administrator.PROTEGO\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000'.$$<Updates Publisher><Thu Jun 9 10:25:16.983 2011.1><thread=1>
Connecting to stored data file at C:\Users\administrator.PROTEGO\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000\scupdb.sdf...$$<Updates Publisher><Thu Jun 9 10:25:17.452 2011.1><thread=1>
Current settings:$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: SCUP Database File: <default> C:\Users\administrator.PROTEGO\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000\scupdb.sdf$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: WSUS Publishing Enabled: True$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: WSUS Publishing is configured to use local server.$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: ConfigMgr Integration Enabled: False$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: Proxy Server settings used: True$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Proxy Server: 172.16.11.12$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Proxy Port: 8080$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Proxy User: <no value>$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: CRL Checking Enabled: False$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: CheckCatalogSubscriptionsOnStartup: True$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
    Setting: Always check for local update content before downloading : False$$<Updates Publisher><Thu Jun 9 10:25:31.811 2011.1><thread=1>
Creating workspaces...$$<Updates Publisher><Thu Jun 9 10:25:31.827 2011.1><thread=1>
Updates workspace: Refreshing alerts.$$<Updates Publisher><Thu Jun 9 10:25:31.999 2011.4><thread=4>
Refreh Alerts: Checking if catalog "Adobe Acrobat X Updates Catalog" has been updated since last successful import.$$<Updates Publisher><Thu Jun 9 10:25:32.217 2011.4><thread=4>
Downloading file: http://armmf.adobe.com/arm-manifests/win/SCUP/Acrobat10_Catalog.cab to C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\gkha5cbk.amd\Acrobat10_Catalog.cab$$<Updates Publisher><Thu Jun 9 10:25:32.342 2011.4><thread=4>
Downloaded completed for file: http://armmf.adobe.com/arm-manifests/win/SCUP/Acrobat10_Catalog.cab.$$<Updates Publisher><Thu Jun 9 10:25:32.624 2011.4><thread=4>
Refreh Alerts: Catalog "Adobe Acrobat X Updates Catalog" doesn't appear to have changed since last import, no alert generated.$$<Updates Publisher><Thu Jun 9 10:25:32.874 2011.4><thread=4>
Refreh Alerts: Checking if catalog "Adobe Reader X Updates Catalog" has been updated since last successful import.$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Downloading file: http://armmf.adobe.com/arm-manifests/win/SCUP/Reader10_Catalog.cab to C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\pyc0tso5.cze\Reader10_Catalog.cab$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Downloaded completed for file: http://armmf.adobe.com/arm-manifests/win/SCUP/Reader10_Catalog.cab.$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Refreh Alerts: Catalog "Adobe Reader X Updates Catalog" doesn't appear to have changed since last import, no alert generated.$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Refreh Alerts: Checking if catalog "Adobe Flash Player Updates Catalog" has been updated since last successful import.$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Downloading file: http://fpdownload.adobe.com/get/flashplayer/current/licensing/win/AdobeFlashPlayerCatalog_SCUP.cab to C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\pwhqj5zf.g15\AdobeFlashPlayerCatalog_SCUP.cab$$<Updates Publisher><Thu Jun 9 10:25:32.905 2011.4><thread=4>
Downloaded completed for file: http://fpdownload.adobe.com/get/flashplayer/current/licensing/win/AdobeFlashPlayerCatalog_SCUP.cab.$$<Updates Publisher><Thu Jun 9 10:25:33.233 2011.4><thread=4>
Refreh Alerts: Catalog "Adobe Flash Player Updates Catalog" doesn't appear to have changed since last import, no alert generated.$$<Updates Publisher><Thu Jun 9 10:25:33.233 2011.4><thread=4>
Refreh Alerts: Completed refresh of catalog alerts.$$<Updates Publisher><Thu Jun 9 10:25:33.249 2011.4><thread=4>
Restoring window settings from last session$$<Updates Publisher><Thu Jun 9 10:25:35.483 2011.1><thread=1>
Initialization completed, displaying main window.$$<Updates Publisher><Thu Jun 9 10:25:37.858 2011.1><thread=1>
Updates workspace: Starting publish wizard with 1 updates.$$<Updates Publisher><Thu Jun 9 10:26:18.905 2011.1><thread=1>
    Publish: Preparing list of selected updates for publishing.$$<Updates Publisher><Thu Jun 9 10:26:22.839 2011.9><thread=9>
    Connecting to a local update server with locally detected settings.$$<Updates Publisher><Thu Jun 9 10:26:22.865 2011.9><thread=9>
    Publish: Update server name: PASAVMEX$$<Updates Publisher><Thu Jun 9 10:26:23.165 2011.9><thread=9>
    Publish: Publish operation starting for 1 updates.$$<Updates Publisher><Thu Jun 9 10:26:23.167 2011.9><thread=9>
    Publish: Publish: Verifying update server is configured with a certificate prior to publishing.$$<Updates Publisher><Thu Jun 9 10:26:23.170 2011.9><thread=9>
    Publish: Publish: Update server appears to be configured with a certificate.$$<Updates Publisher><Thu Jun 9 10:26:24.509 2011.9><thread=9>
    Building dependency graph for update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'$$<Updates Publisher><Thu Jun 9 10:26:24.664 2011.9><thread=9>
    No dependencies found for update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'$$<Updates Publisher><Thu Jun 9 10:26:24.737 2011.9><thread=9>
Found total of 0 dependencies (may include duplicates).$$<Updates Publisher><Thu Jun 9 10:26:24.739 2011.9><thread=9>
PublishItem: Update ''Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'' has no dependencies.$$<Updates Publisher><Thu Jun 9 10:26:24.761 2011.9><thread=9>
PublishItem: Publishing update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'.$$<Updates Publisher><Thu Jun 9 10:26:24.761 2011.9><thread=9>
PublishItem: --- Evaluating software update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' for publishing as FullContent.$$<Updates Publisher><Thu Jun 9 10:26:24.787 2011.9><thread=9>
PublishItem: --- Software update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' needs to be published with full content.$$<Updates Publisher><Thu Jun 9 10:26:25.170 2011.9><thread=9>
PublishItem: Retrieving content for update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'.$$<Updates Publisher><Thu Jun 9 10:26:25.427 2011.9><thread=9>
PublishItem: --- Content will be saved to C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\o4xcjeui.qt1\AdbeRdrUpd1001_Tier1.msp.$$<Updates Publisher><Thu Jun 9 10:26:25.428 2011.9><thread=9>
PublishItem: Download Content: file was downloaded successfully.$$<Updates Publisher><Thu Jun 9 10:26:26.567 2011.9><thread=9>
PublishItem: Successfully retrieved content for software update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')' to local file: C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\o4xcjeui.qt1\AdbeRdrUpd1001_Tier1.msp$$<Updates Publisher><Thu Jun 9 10:26:26.568 2011.9><thread=9>
File C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\\o4xcjeui.qt1\AdbeRdrUpd1001_Tier1.msp appears to be signed, retrieved certificate, checking signature...$$<Updates Publisher><Thu Jun 9 10:26:26.700 2011.9><thread=9>
PublishItem: --- SDP XML file for publishing created at C:\Users\administrator.PROTEGO\AppData\Local\Temp\2\tmp6396.tmp$$<Updates Publisher><Thu Jun 9 10:26:27.443 2011.9><thread=9>
PublishItem: --- Calling update server API for publishing update 'Reader 10.0.1 (UpdateId:'42cc6726-c3fe-464b-b8ac-38ec00766262' Vendor:'Adobe Systems, Inc.' Product:'Adobe Reader')'$$<Updates Publisher><Thu Jun 9 10:26:27.568 2011.9><thread=9>
2011-06-09 15:26:37.691 UTC Info Scup2011.9 ThreadEntry _ThreadPoolWaitCallback.PerformWaitCallback$$<Updates Publisher><Thu Jun 9 10:26:37.691 2011.9><thread=9>
2011-06-09 15:26:37.699 UTC Info Scup2011.9 CabUtilities.CheckCertificateSignature File cert verification failed for C:\Program Files\Update Services\autest.cab with 2147942402$$<Updates Publisher><Thu Jun 9 10:26:37.699 2011.9><thread=9>
2011-06-09 15:26:37.701 UTC Info Scup2011.9 WsusTestKeys.AreTestKeysAllowed Server test key check: test keys are NOT allowed$$<Updates Publisher><Thu Jun 9 10:26:37.701 2011.9><thread=9>
2011-06-09 15:26:37.974 UTC Info Scup2011.9 CabUtilities.CheckCertificateSignature File cert verification failed for \\PASAVMEX\UpdateServicesPackages\42cc6726-c3fe-464b-b8ac-38ec00766262\e4fc1757-9445-456c-884b-1d437a9d6b97_1.cab with 2148204809$$<Updates Publisher><Thu Jun 9 10:26:37.974 2011.9><thread=9>
2011-06-09 15:26:38.022 UTC Error Scup2011.9 Publisher.VerifyAndPublishPackage VerifyAndPublishPackage(): Failed to Verify Signature for file: \\PASAVMEX\UpdateServicesPackages\42cc6726-c3fe-464b-b8ac-38ec00766262\e4fc1757-9445-456c-884b-1d437a9d6b97_1.cab
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.VerifyAndPublishPackage()
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
   at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)
   at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)
   at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)
   at Scup.Wizards.PublishOperation.Start()
   at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()$$<Updates Publisher><Thu Jun 9 10:26:38.22 2011.9><thread=9>
2011-06-09 15:26:38.024 UTC Error Scup2011.9 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\PASAVMEX\UpdateServicesPackages\42cc6726-c3fe-464b-b8ac-38ec00766262\e4fc1757-9445-456c-884b-1d437a9d6b97_1.cab
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
   at Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem, IPublisher publisher, String contentFolder)
   at Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)
   at Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)
   at Scup.Wizards.PublishOperation.Start()
   at Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()$$<Updates Publisher><Thu Jun 9 10:26:38.24 2011.9><thread=9>
PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\PASAVMEX\UpdateServicesPackages\42cc6726-c3fe-464b-b8ac-38ec00766262\e4fc1757-9445-456c-884b-1d437a9d6b97_1.cab$$<Updates Publisher><Thu Jun 9 10:26:38.41 2011.9><thread=9>
Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.$$<Updates Publisher><Thu Jun 9 10:26:38.50 2011.9><thread=9>
Publish: Background processing completed.$$<Updates Publisher><Thu Jun 9 10:26:38.54 2011.1><thread=1>

June 9th, 2011 6:30pm

Finally I could publish, I did what this link shows

http://blogs.technet.com/b/sus/archive/2009/02/05/unable-to-publish-updates-using-scup-exception-occurred-during-publishing.aspx

thanks !

  • Proposed as answer by Justin Yaple Wednesday, January 07, 2015 8:19 PM
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 6:50pm

Finally I could publish, I did what this link shows

http://blogs.technet.com/b/sus/archive/2009/02/05/unable-to-publish-updates-using-scup-exception-occurred-during-publishing.aspx

thanks !

  • Proposed as answer by Justin Yaple Wednesday, January 07, 2015 8:19 PM
June 9th, 2011 6:50pm

Finally I could publish, I did what this link shows

http://blogs.technet.com/b/sus/archive/2009/02/05/unable-to-publish-updates-using-scup-exception-occurred-during-publishing.aspx

thanks !

  • Proposed as answer by Justin Yaple Wednesday, January 07, 2015 8:19 PM
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 6:50pm

Can you verify that you have installed the required WSUS hotfix?
June 9th, 2011 7:25pm

Hello,

we have the same issue: A fatal error occurred during publishing :The specified item could not be found in the database.

KB2530678 has been installed, certificate has been recreated with code signing only and has been imported. Not full nor metadata only publishing works.

WSUS, SCUP and SCCM are all on the same (virtual) 2008R2 Standard Edition server.

 

Thanks,

Rogier

Free Windows Admin Tool Kit Click here and download it now
June 22nd, 2011 5:57pm

For SCUP to work i did the following:

  1. On the WSUS/SCUP server open MMC > certificates > Computer account > Local Computer. Export the WSUS Publishers Self-Signed certificate to a DER encoded binary x.509 (.cer) file. Do not export private key. If the certificate is not available, create one first with SCUP.
  2. Import the .CER file in the Trusted Root Certification Authorities\Certificates node.
  3. Import the .CER file in the Trusted Publishers\Certificates node.
  4. Create a computer GPO to allow custom updates to be installed on clients. Go to Computer Configuration > Policies > Windows Settings > Public Key Policies. Rightclick Trusted Root Certification Authorities > Import. Import the cert that you created in step 1.
  5. In the same GPO do the same for Trusted Publishers.
  6. In the same GPO go to Computer Configuration > Policies > Administrative Templates > Windows Components. Open the properties of Windows Update. Enable the setting "Allow signed updates from an intranet Microsoft update service location".
  7. Optional: when using the install updates task in SCCM OSD, install the certificate prior to executing the update task. Place 1 reboot between these actions. Additionally, if you would Dell Driver updates to install within OSD then install the openmanage client before de updates task as well (with 1 reboot in between).

regards

July 12th, 2011 11:56am

The Hotfix did get installed and we did get past that particular error ... working on the cert issues currently
Free Windows Admin Tool Kit Click here and download it now
July 12th, 2011 4:23pm

Hi,

I am facing the same problem as you and used yoru solution but to no avail .. Would like to know if there is any possibilities that it is caused by the self-signed certificate itself or anything along the line.

 

Greatly appreciate if anyone could help on this. Thanks!

CabUtilities.CheckCertificateSignature    File cert verification failed for c:\Program Files\Update Services\autest.cab with 2147942402

WsusTestKeys.AreTestKeysAllowed    Server test key check: test keys are NOT allowed

CabUtilities.CheckCertificateSignature    File cert verification failed for \\SG2SCCM\UpdateServicesPackages\421e86ff-37e0

 

Publisher.PublishPackage    PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\SG2SCCM\UpdateServicesPackages\421e86ff-37e0-4199-9a0c-4976332bbcdf\3027bcad-87


PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\SG2SCCM\UpdateServicesPackages\421e86ff-37e0-4199-9a0c-4976332bbcdf\3027bcad-87b9-4906-845e-dcb1077c0167_1.cab
Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured.

July 13th, 2011 9:35am

Hi Guys,

Today i too faced the same publishing issue.

Just i followed the below steps, 

 Delete all the previous WSUS signed certificate from MMC console under WSUS folder and restarted the server. Recreated the WSUS signed certficate once again and the publishing worked fine. 

December 9th, 2011 8:38pm

Please check the Certificate length it should be 1024
Free Windows Admin Tool Kit Click here and download it now
January 20th, 2015 11:29am

My RSA Length is showing 2048...?

February 2nd, 2015 11:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics