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 > Patch Manager error: Primary Filegroup is full

Patch Manager error: Primary Filegroup is full

Created by Erica Gill, last modified by MindTouch on Jun 23, 2016

Views: 22 Votes: 0 Revisions: 9

Overview

The following error reporting that the Primary Filegroup is full, or similar, appears when using Patch Manager:

Could not allocate space for object 'dbo.eqtasks' 'pk_ewtasks_taskid' in datbase '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 filegroup. DataPortal_Insert method call failed dataportal. Update failed dataportal_execute method call failed DataPortal. Update failed.

 

This indicates the Patch Manager database is full.

Environment

All Patch Manager versions

Cause 

The database that Patch Manager is using has encountered one or more of the below scenarios:

  • A SQL server database size limit has been reached.
  • A database size limit has been reached.
  • The partition hosting the Primary Filegroup has run out of space.

Resolution

Confirm the database size and limits

  1. Open SQL Management Studio and log in with full permissions (SA account).
  2. Right-click your Patch Manager database
  3. Select Properties.
  4. In the Database Properties window, click Files.
  5. Review the Filegroup, Initial Size (MB) and the Autogrowth settings along with the Path on the PRIMARY Filegroup:
    • The Filegroup indicates which entry is for the Primary Filegroup.
    • The Initial Size (MB) indicates the current size of the file. 
    • The Autogrowth settings indicates if an artificial limit has been manually applied to the filegroup. 
      • If there is a limit set on the maximum size which is the same as the Initial Size (MB), consult the DBA who configured the limit.
    • Use the Path option to determine which partition the database's Primary Filegroup is stored on.
      • Verify the partition has free space for the file to grow. If not, space will have to be created or the database moved.
  6. Compare you SQL server version and license type and the maximum database size it allows, with the database size. Some versions of SQL have differing limits on database size. 
    Note: Older versions of SQL in SQL Express are most likely to have database size limitations.

 

If the issue is down to the size of the database and the database has free space it is possible to shrink the database to make the free space available.

Determine the amount of free space in the Patch Manager Database

  1. Open SQL Management Studio and log in with full permissions (SA account).
  2. Right-click your Patch Manager database.
  3. Select Properties.
  4. In the General page, the size of the database and the Space Available will be shown.

If the space available is significant, then shrinking may release enough space to clear the error. See the following steps which describe how to shrink the database.

Shrink the Patch Manager database

IMPORTANT:  Stop the EmintentWare DataGrid Server service on the Patch Manager server(s).

  1. Open SQL Management Studio and log in with full permissions (SA account).
  2. Right-click your Patch Manager database.
  3. Go to All Task > SHRINK > Files.
  4. Verify that the File Type is set to Data, Filegroup "Primary".
  5. For the Shrink Action, select Reorganise pages before releasing unused space.
  6. Change the Shrink File to setting to just above the minimum setting shown on the right.
  7. Click OK.
    Note: This can take a while - usually a few minutes per GB..
  8. Restart the EmintentWare DataGrid Server service on the Patch Manager server(s).

 

Last modified
01:15, 23 Jun 2016

Tags

Classifications

Public