Hello PatchMyPC team 
Working with the Enterprise catalog and trying to do an initial sync and publish to WSUS. I'm getting the following error for every package that is processed:
"An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2149122455"
Googling had similar issues that pointed to a mismatch of WSUS shares and file paths. I have confirmed that those exist and are correct on my server.
Looking for the specific error code - 2149122455 - brought up even less information, save for one reference to a proxy error. My server is behind a web proxy and I've set the proxy settings - downloads for the packages work just fine so I believe that's setup properly.
This was tried with a WSUS-generated certificate, and a Publishing Service-generated self-signed certificate - no change in errors either way.
I also tried assigning the service to run as my SCCM service account in case it was something permission based - no change in errors there either.
Issue existed with 1.2.5.0 build, 1.2.5.4 preview build, and still exists as of the 1.3.0.0 builds (Just updated yesterday).
Logging level is set to Debug and I'm happy to provide them via email/private message if that would help
Thanks in advance!
-Will
Working with the Enterprise catalog and trying to do an initial sync and publish to WSUS. I'm getting the following error for every package that is processed:
"An error occurred while publishing an update to WSUS: Failed to sign package; error was: 2149122455"
Googling had similar issues that pointed to a mismatch of WSUS shares and file paths. I have confirmed that those exist and are correct on my server.
Looking for the specific error code - 2149122455 - brought up even less information, save for one reference to a proxy error. My server is behind a web proxy and I've set the proxy settings - downloads for the packages work just fine so I believe that's setup properly.
This was tried with a WSUS-generated certificate, and a Publishing Service-generated self-signed certificate - no change in errors either way.
I also tried assigning the service to run as my SCCM service account in case it was something permission based - no change in errors there either.
Issue existed with 1.2.5.0 build, 1.2.5.4 preview build, and still exists as of the 1.3.0.0 builds (Just updated yesterday).
Logging level is set to Debug and I'm happy to provide them via email/private message if that would help
Thanks in advance!
-Will