Awesome piece of detective work.
On Monday, September 21, 2015 8:47 AM, Jimmy Martin
<[email protected]> wrote:
<!--#yiv6918456771 _filtered #yiv6918456771 {font-family:"Cambria
Math";panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv6918456771
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv6918456771
{font-family:"Segoe UI";panose-1:2 11 5 2 4 2 4 2 2 3;}#yiv6918456771
#yiv6918456771 p.yiv6918456771MsoNormal, #yiv6918456771
li.yiv6918456771MsoNormal, #yiv6918456771 div.yiv6918456771MsoNormal
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri",
sans-serif;}#yiv6918456771 a:link, #yiv6918456771
span.yiv6918456771MsoHyperlink
{color:#0563C1;text-decoration:underline;}#yiv6918456771 a:visited,
#yiv6918456771 span.yiv6918456771MsoHyperlinkFollowed
{color:#954F72;text-decoration:underline;}#yiv6918456771 p
{margin-right:0in;margin-left:0in;font-size:12.0pt;font-family:"Times New
Roman", serif;}#yiv6918456771 span.yiv6918456771EmailStyle18
{font-family:"Calibri", sans-serif;color:windowtext;}#yiv6918456771
span.yiv6918456771EmailStyle19 {font-family:"Calibri",
sans-serif;color:#1F497D;}#yiv6918456771 span.yiv6918456771EmailStyle20
{font-family:"Calibri", sans-serif;color:#1F497D;}#yiv6918456771
.yiv6918456771MsoChpDefault {font-size:10.0pt;} _filtered #yiv6918456771
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv6918456771 div.yiv6918456771WordSection1
{}-->Solved, found the issue in case anyone else runs into it…Wsus was freaking
out on the size of the update, it wasn’t a cert thing.
http://robinvervoort.be/?p=22 From: Jimmy Martin
Sent: Thursday, September 10, 2015 10:05 AM
To: [email protected]
Subject: RE: scup has trouble publishing single update Anyone with guidance on
this? It appears to be ONLY this one HP update that has issues, all the other
3rd party applications including other HP updates are publishable without
error. I was able to publish the proliant 2015 june SOFTWARE bundle without
error. I have tried to manually download the file both through my proxy and
around my proxy and the results are the same. I have tried to use local source
instead of ftp... But still, I get these errors when I try to publish. It
seems like this is a HP specific issue to me since all the other updates will
publish… does anyone else out there use scup to make psp/spp updates available
to be installed via sccm? If so, does the june 2015 firmware update work for
you? PublishItem: Update ''HP ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')'' has no dependencies. Updates Publisher
9/10/2015 8:58:02 AM 24 (0x0018)PublishItem: Publishing update
'HP ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')'. Updates Publisher 9/10/2015
8:58:02 AM 24 (0x0018)PublishItem: --- Evaluating software update 'HP
ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')' for publishing as FullContent.
Updates Publisher 9/10/2015 8:58:02 AM 24 (0x0018)PublishItem: ---
Software update 'HP ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')' needs to be published with full content.
Updates Publisher 9/10/2015 8:58:02 AM 24
(0x0018)PublishItem: Retrieving content for update 'HP ProLiant Server Firmware
2015.06.0 (UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant
Updates' Product:'Firmware Bundles')'. Updates Publisher
9/10/2015 8:58:02 AM 24 (0x0018)PublishItem: --- Content will be saved
to
C:\Users\bigdummy\AppData\Local\Temp\2\\itcznyku.heh\hppucb-proliantfw-2015.06.0.106.exe.
Updates Publisher 9/10/2015 8:58:02 AM 24 (0x0018)PublishItem:
--- Update 'HP ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')' specifies local source publishing, checking for
local content. Updates Publisher 9/10/2015 8:58:02 AM
24 (0x0018)PublishItem: Local content for update 'HP ProLiant Server Firmware
2015.06.0 (UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant
Updates' Product:'Firmware Bundles')' found at
C:\Users\bigdummy\Documents\LocalSourcePublishing\hppucb-proliantfw-2015.06.0.106.exe.
Updates Publisher 9/10/2015 8:58:02 AM 24
(0x0018)PublishItem: Successfully retrieved content for software update 'HP
ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')' to local file:
C:\Users\bigdummy\AppData\Local\Temp\2\\itcznyku.heh\hppucb-proliantfw-2015.06.0.106.exe
Updates Publisher 9/10/2015 8:58:04 AM 24
(0x0018)File
C:\Users\bigdummy\AppData\Local\Temp\2\\itcznyku.heh\hppucb-proliantfw-2015.06.0.106.exe
appears to be signed, retrieved certificate, checking signature...
Updates Publisher 9/10/2015 8:58:09 AM 24 (0x0018)PublishItem: ---
SDP XML file for publishing created at
C:\Users\bigdummy\AppData\Local\Temp\2\tmp3497.tmp Updates
Publisher 9/10/2015 8:58:12 AM 24 (0x0018)PublishItem: --- Calling
update server API for publishing update 'HP ProLiant Server Firmware 2015.06.0
(UpdateId:'c92873a5-22ff-4c40-92bb-e1f8230196b5' Vendor:'HP ProLiant Updates'
Product:'Firmware Bundles')' Updates Publisher
9/10/2015 8:58:12 AM 24 (0x0018)2015-09-10 14:13:05.287 UTC Info
Scup2011.24 CabUtilities.CheckCertificateSignature File cert
verification failed for
\\SERVER\UpdateServicesPackages\c92873a5-22ff-4c40-92bb-e1f8230196b5\54bb2a84-b2fd-4668-bdfc-70b8d8f8004f_2.cab
with 2147943792 Updates Publisher 9/10/2015 9:13:05 AM 24
(0x0018)2015-09-10 14:13:05.289 UTC Error Scup2011.24
Publisher.VerifyAndPublishPackage VerifyAndPublishPackage():
Failed to Verify Signature for file:
\\server\UpdateServicesPackages\c92873a5-22ff-4c40-92bb-e1f8230196b5\54bb2a84-b2fd-4668-bdfc-70b8d8f8004f_2.cab
1/1/1601 12:00:00 AM 1998213131 (0x771A500B)
at
Microsoft.UpdateServices.Internal.BaseApi.Publisher.VerifyAndPublishPackage()
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String
sourcePath, String additionalSourcePath, String packageDirectoryName)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem,
IPublisher publisher, String contentFolder) 1/1/1601 12:00:00 AM
1998213131 (0x771A500B) at
Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishOperation.Start() 1/1/1601 12:00:00
AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Object[]& outArgs)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage
msg, IMessageSink replySink) 1/1/1601 12:00:00 AM
1998213131 (0x771A500B) at
System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx) 1/1/1601 12:00:00 AM 1998213131
(0x771A500B) at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx) 1/1/1601 12:00:00 AM 1998213131
(0x771A500B) at
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
1/1/1601 12:00:00 AM 1998213131 (0x771A500B)
at System.Threading.ThreadPoolWorkQueue.Dispatch() Updates
Publisher 9/10/2015 9:13:05 AM 24 (0x0018)2015-09-10 14:13:05.292
UTC Error Scup2011.24 Publisher.PublishPackage
PublishPackage(): Operation Failed with Error: Verification of file signature
failed for file:
\\SERVER\UpdateServicesPackages\c92873a5-22ff-4c40-92bb-e1f8230196b5\54bb2a84-b2fd-4668-bdfc-70b8d8f8004f_2.cab
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String
sourcePath, String additionalSourcePath, String packageDirectoryName)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishItem.PublishPackage(PublishReportItem reportItem,
IPublisher publisher, String contentFolder) 1/1/1601 12:00:00 AM
1998213131 (0x771A500B) at
Scup.Wizards.NormalPublishItem.Publish(PublishReportItem reportItem)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishItem.PublishUpdateAndDependencies(PublishReport report)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishOperation.Start() 1/1/1601 12:00:00
AM 1998213131 (0x771A500B) at
Scup.Wizards.PublishProgressPage.DoWork(Object sender, DoWorkEventArgs e)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr
md, Object[] args, Object server, Object[]& outArgs)
1/1/1601 12:00:00 AM 1998213131 (0x771A500B) at
System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage
msg, IMessageSink replySink) 1/1/1601 12:00:00 AM
1998213131 (0x771A500B) at
System.Threading.ExecutionContext.RunInternal(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx) 1/1/1601 12:00:00 AM 1998213131
(0x771A500B) at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state, Boolean
preserveSyncCtx) 1/1/1601 12:00:00 AM 1998213131
(0x771A500B) at
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
1/1/1601 12:00:00 AM 1998213131 (0x771A500B)
at System.Threading.ThreadPoolWorkQueue.Dispatch() Updates
Publisher 9/10/2015 9:13:05 AM 24 (0x0018)PublishItem:
InvalidException occurred during publishing: Verification of file signature
failed for file:
\\SERVER\UpdateServicesPackages\c92873a5-22ff-4c40-92bb-e1f8230196b5\54bb2a84-b2fd-4668-bdfc-70b8d8f8004f_2.cab
Updates Publisher 9/10/2015 9:13:05 AM 24 (0x0018)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 9/10/2015 9:13:05 AM
24 (0x0018) The self signed cert is good, deployed… and works for all
the other 3rd party apps Jimmy Martin
(901) 227-8209 From: Jimmy Martin
Sent: Monday, August 31, 2015 2:45 PM
To: [email protected]
Subject: scup has trouble publishing single update Having a little trouble
publishing a single update from the HP proliant server updates… The HP June
2015 firmware update. When I try to do publish it, it is saying I have a
certificate issue. *BUT* on all the other updates I do through scup, no issues
with publishing updates. I have published the June 2015 proliant software
updates without issue and that is from the same catalog. Anyone else seen a
similar issue? Here’s the relevant log errors 2015-08-31 19:02:48.876 UTC
Error Scup2011.14 Publisher.PublishPackage
PublishPackage(): Operation Failed with Error: Failed to sign package; error
was: 2147942401PublishItem: InvalidException occurred during publishing: Failed
to sign package; error was: 2147942401Publish: A fatal error occurred during
publishing :Signature verification exception during publish, verify the WSUS
certificates and advanced timestamp setting are properly configured. Thank
You! Jimmy Martin | Engineer | Information Technology | BMHCC - CORPORATE
Phone: (901) 227-8209 | [email protected]
Opinions expressed above are not necessarily those of Baptist. This message
and any files transmitted with it may contain legally privileged, confidential,
or proprietary information. If you are not the intended recipient of this
message, you are not permitted to use, copy, or forward it, in whole or in part
without the express consent of the sender. Please notify the sender of the
error by reply email, disregard the foregoing messages, and delete it
immediately.
P Please consider the environment before printing this email...
