Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Patch Manager > Error when publishing a package to managed computers

Error when publishing a package to managed computers

Overview

When you publish a package in Patch Manager, the following error displays: 

Failed to sign package; error was: 2148081670

This error also appears in the worker logs at 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. Log in to the Patch Manager Admin Console as an administrator.
  2. In the navigation pane, expand Administration and Reporting and select Software Publishing. 
  3. In the Actions pane, click Server Publishing Setup Wizard.
  4. Click the WSUS Server drop-down menu and select the WSUS server.
    The remaining fields populate automatically.
  5. Select Create self-signed certificate, and click Next.
  6. Click Yes to confirm replacing the certificate.

    All client computers must be re-provisioned with the new certificate.

  7. Select the servers that will receive the new certificate.
  8. Complete the wizard. 

When you are finished, the new certificate is storied 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 copied to other stores or another location, remove the duplicate certificates. 

 

 

Last modified
12:21, 20 Jul 2017

Tags

Classifications

Public