Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

publishing SCUP 2011 updates to WSUS/SCCM are failing

Network Sharing , TCP/IP, Internet, Wireless, Exchange, IIS, ISA and Print

publishing SCUP 2011 updates to WSUS/SCCM are failing

Postby guest » Wed Jul 11, 2012 10:48 am

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 ErrorScup2011.9 Publisher.PublishPackagePublishPackage(): 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>




Report As AbuseSpam/AdvertisingProfanityInappropriate/Adult ContentOff Topic/Irrelevant PostsOther Term of Use or Code of Conduct violation
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9679
Joined: Mon Nov 27, 2006 1:10 pm

Re: publishing SCUP 2011 updates to WSUS/SCCM are failing

Postby guest » Wed Jul 11, 2012 10:49 am

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.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9679
Joined: Mon Nov 27, 2006 1:10 pm


Return to Networking

Your Ad Here

Who is online

Users browsing this forum: No registered users and 4 guests