I have had SCUP 2011 integrated with SCCM 2012R2 since March. I went in on Friday to add some new cab files from Adobe and publish the updates. If I run a "full content" publish it will fail every time with "SignPackageCabError" and "failed to sign package 2147942403."
I know this is related to the self signed certificate so I have recreated that and it still failed. I followed all options at the following sites to no avail.
https://social.technet.microsoft.com/Forums/systemcenter/en-US/d78f31e6-dce0-4746-88a0-b8ca17c3d2f4/scup-failed-to-sign-package?forum=configmgrsum
http://blogs.msdn.com/b/minfangl/archive/2011/05/31/common-errors-and-resolutios-for-system-center-updates-publisher-2011.aspx
http://www.networksteve.com/enterprise/topic.php/SCUP_2011_publishing_fails_with_error:%C2%A0_Failed_to_sign_package;/?TopicId=68758&Posts=1
I then decided to try a certificate from my PKI environment. I followed the steps from this page and still received the same error as above.
https://mikeshellenberger.wordpress.com/2010/09/02/system-center-updates-publisher-microsoft-pki/
http://blogs.technet.com/b/jasonlewis/archive/2011/07/12/system-center-updates-publisher-signing-certificate-requirements-amp-step-by-step-guide.aspx
At this point I am completely lost at what to try. It was working just fine a few weeks ago. No updates were applied to the system between now and then, the configuration didn't change, I am the only person that gets on this server, etc.
I even went through and uninstalled the scup application, deleted all certs, deleted the database, and rebuilt everything.
I feel like my only other option is to install scup on another server and see if it works from there.
Any help would be great.