Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Patch Manager error when publishing updates from a SAS

Patch Manager error when publishing updates from a SAS

Updated 08/29/2018


When you open Patch Manager on a secondary application server (SAS) and publish updates to WSUS, the following error message displays:

The following errors occurred while publishing the packages: <br/> Source: 
Application Server (<ServerName>) Reason: The configuration Management Task 
failed to create the task transactions in the task results table. Reason: 
Could not allocate space for object 'dbo.ewtasksresults','IX_ewtasksresults' in 
database 'EminentWare' because the 'PRIMARY' filegroup is full. Create disk space 
by deleting unneeded files, dropping objects in the filegroup, adding additional 
files to the filegroup, or setting autogrowth on for existing files in the group."

A SAS is a full Patch Manager installation that links back and communicates with the PAS. The SAS is able to independently download third-party packages from the SolarWinds third-party catalog and control separate Windows Server Update Services (WSUS) servers that are not configured to work with the PAS. 


  • All supported Patch Manager versions


The Microsoft SQL Server Express database on the primary application server (PAS) has reached its 10 GB size limit.

The PAS provides the default management group, certificate configuration authority, and communications hub for your Patch Manager deployment.


Perform one of the following procedures:

  • Migrate the PAS SQL Express Database to a remote SQL Server database.
  • Set up a new SQL Server Express database on the PAS. 

See the following KB articles for details about the size limitations in supported SQL Server Express versions:


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified