Good Afternoon -
The 3rd Wednesday of each month is when I release 3rd party updates so again reimported and published new updates this morning - however - Google Picasa still was the only one to fail. The error I had was different, though. I tried publishing it to SCCM (2012 R2 - located locally) using "Full Content" with and without resigning the cert; but both failed. below are the lines from the log...
PublishItem: Update ''Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'' has no dependencies. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: Publishing update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: --- Evaluating software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' for publishing as FullContent. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: --- Software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' needs to be published with full content. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: Retrieving content for update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:27 PM 16 (0x0010)
PublishItem: --- Content will be saved to C:\Users\bdkeller\AppData\Local\Temp\2\\mxueuhrm.2u3\picasa39-setup.exe. Updates Publisher 10/20/2015 1:26:27 PM 16 (0x0010)
PublishItem: Download Content: file was downloaded successfully. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: Successfully retrieved content for software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' to local file: C:\Users\bdkeller\AppData\Local\Temp\2\\mxueuhrm.2u3\picasa39-setup.exe Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: --- Digest verification failed on content for software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: --- Publish of software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' has FAILED. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
When importing catalogs, I usually choose "No to All" for duplicates as I have custom Supersedence set - but - for Picasa I overwrote the old one with the latest version. Also, if it makes a difference, it appears as Expired in SCCM even though it does not appear as such in SCUP. Weird.
Thanks!
The 3rd Wednesday of each month is when I release 3rd party updates so again reimported and published new updates this morning - however - Google Picasa still was the only one to fail. The error I had was different, though. I tried publishing it to SCCM (2012 R2 - located locally) using "Full Content" with and without resigning the cert; but both failed. below are the lines from the log...
PublishItem: Update ''Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'' has no dependencies. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: Publishing update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: --- Evaluating software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' for publishing as FullContent. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: --- Software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' needs to be published with full content. Updates Publisher 10/20/2015 1:26:26 PM 16 (0x0010)
PublishItem: Retrieving content for update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:27 PM 16 (0x0010)
PublishItem: --- Content will be saved to C:\Users\bdkeller\AppData\Local\Temp\2\\mxueuhrm.2u3\picasa39-setup.exe. Updates Publisher 10/20/2015 1:26:27 PM 16 (0x0010)
PublishItem: Download Content: file was downloaded successfully. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: Successfully retrieved content for software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' to local file: C:\Users\bdkeller\AppData\Local\Temp\2\\mxueuhrm.2u3\picasa39-setup.exe Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: --- Digest verification failed on content for software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')'. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
PublishItem: --- Publish of software update 'Google Picasa 3.9.141.255 (UpdateId:'4c66f9c3-a164-4c9b-ab7b-a7a014dbe17e' Vendor:'Google' Product:'Picasa')' has FAILED. Updates Publisher 10/20/2015 1:26:31 PM 16 (0x0010)
When importing catalogs, I usually choose "No to All" for duplicates as I have custom Supersedence set - but - for Picasa I overwrote the old one with the latest version. Also, if it makes a difference, it appears as Expired in SCCM even though it does not appear as such in SCUP. Weird.
Thanks!