Submit a ticketCall us

AnnouncementsWeb Help Desk Integrations eCourse

Looking to reduce response times? Sign up for our eCourse to learn how integrating Web Help Desk with Dameware Remote Support, Network Configuration Manager, Network Performance Monitor, and Server & Application Monitor can improve communication efficiencies.

Register here.

Home > Success Center > Patch Manager > Patch Manager error: Primary Filegroup is full

Patch Manager error: Primary Filegroup is full

Overview

The following error displays in Patch Manager, indicating that the Patch Manager database is full:

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.

Environment

All Patch Manager versions

Cause 

The Patch Manager database encountered one or more of the following issues: 

  • The SQL Server database reached its size limit.
  • The database reached its size limit. 
  • The partition hosting the Primary Filegroup ran 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 and select Properties. 
  3. In the Database Properties window, click Files.
  4. Review the Filegroup, Initial Size (MB) and Autogrowth settings, and 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.
  5. Compare your SQL Server version, license type and maximum database size with the database size. Some SQL Server versions have varying database size limits. Older SQL Express versions are most likely to have database size limitations.

If the issue is database size and the database has free space, consider shrinking the database to create free space.

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 and select Properties.
  3. In the General page, the size of the database and the Space Available will be shown.

If significant space available, shrinking the database may release enough space to clear the error.

Shrink the Patch Manager database

  1. Stop the EminentWare Database Server service on the patch Manager servers.
  2. Open SQL Management Studio and log in with full permissions (SA account).
  3. Right-click your Patch Manager database.
  4. Go to All Task > SHRINK > Files.
  5. Verify that the File Type is set to Data, Filegroup "Primary".
  6. For the Shrink Action, select Reorganize pages before releasing unused space.
  7. Change the Shrink File to setting to just above the minimum setting shown on the right.
  8. Click OK.
    This process may require several minutes to complete.
  9. Restart the EmintentWare DataGrid Server service on the Patch Manager server(s).

 

Last modified

Tags

Classifications

Public