Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Patch Manager > Failed to sign package; error was: 2148081670

Failed to sign package; error was: 2148081670

Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 53 Votes: 2 Revisions: 12

Overview

The following error appears when trying to publish a package in Patch Manager:

Failed to sign package; error was: 2148081670

 

This is also seen in the worker logs located in C:\ProgramData\Solarwinds\PM\Log\EminentWare.WorkerProcess similar to the following:

2026/01/12 04:31:11:792 PID: 14200 TID:  7618 [ERROR] Failed to publish update: SomePackageName Message: Failed to sign package; error was: 2148081670 Stack Trace:
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.SignPackageCab(Boolean dualSign, String httpTimeStamp)
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName, Boolean dualSign, String httpTimeStamp)
   at Microsoft.UpdateServices.Internal.BaseApi.Publisher.PublishPackage(String sourcePath, String additionalSourcePath, String packageDirectoryName)
   at EminentWare.UpdateServices.Administration.UpdateServer.PublishUpdates()

Environment

All Patch Manager versions

Resolution

  1. In the Patch Manager console, navigate to Administration and Reporting > Software Publishing.
  2. In the Actions pane, click Server Publishing Setup Wizard.
  3. Select the WSUS server.
  4. Select Create self-signed certificate.
  5. Click Next.
  6. Choose Yes to confirm replacing the certificate. All client computers will need to be re-provisioned with the new certificate.
  7. Select the servers to distribute the new certificate and follow the onscreen directions.

 

The new certificate should now only be in the following certificate stores for the local computer account.

  • Trusted Publishers store
  • Trusted Root store 
  • In the WSUS store on the WSUS server only

If the certificate is in other stores or duplicates of the certificate exists, the duplicates should be removed.

 

 

Last modified
01:03, 23 Jun 2016

Tags

Classifications

Public