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 > Network Performance Monitor (NPM) > Insufficient disk space in filegroup 'Primary' error

Insufficient disk space in filegroup 'Primary' error

Updated on August 10, 2016

Overview

The following error is seen in the logs or when running the configuration wizard:

 

Insufficient disk space in filegroup 'Primary'

Environment

All Orion versions

Cause 

 

The database being used 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.

 

The error is caused by the database being full such that the Orion is no longer able to write on it. This issue is most commonly seen with SQL express, as it has a 10 gig limit. It can also be seen on other SQL versions if the drive the database is on is full or it has a size limit.

 

 

Resolution

 

To resolve the issue, you can find why the size is restricted and make space in the database. For example, if you are using SQL express, you can move the database to a full version of SQL. You can also clear out data using Clear Orion NPM database space.

 

Confirm the database size and limits:

  1. Open SQL Management Studio and login with full permissions (SA account).
  2. Right click your Orion database
  3. Select Properties
  4. In the Database Properties window click on Files.
  5. There review the Filegroup, Initial Size (MB) and the Autogrowth settings along with the Path on the PRIMARY Filegroup.
    • The Filegroup tells us which entry is for the Primary Filegroup
    • The Initial Size (MB) tells us the current size of the file. 
    • The Autogrowth settings tell us 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) please consult your 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 allow, 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 that would be a concern. 

 

 

 


 

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.

 

Steps to determine the amount of free space in the Database:

  1. Open SQL Management Studio and login with full permissions (SA account).
  2. Right click your 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 below steps which describe how to shrink the database.

 

 


 

Steps to shrink the database:

 

IMPORTANT:  Stop the Orion services through the "Orion Service Manager" ("Start->All Programs->SolarWinds Orion->Advanced Features-> Orion Service Manager"). The Orion services on all Orion servers should be stopped.

 

  1. Open SQL Management Studio and login with full permissions (SA account).
  2. Right click your Orion database
  3. Choose "All Task > SHRINK > Files
  4. Ensure the File Type is set to Data, Filegroup "Primary".
  5. For the Shrink Action, select "Reorganize pages before releasing unused space. Change the "Shrink File to" setting to just above the minimum setting shown on the right.
  6. Click OK.
    • Note: This can take a while - usually a few minutes per GB..
  7. Restart the Orion services through the "Orion Service Manager" ("Start->All Programs->SolarWinds Orion->Advanced Features-> Orion Service Manager"). The Orion services on the Primary Poller should be started first and after any additional pollers and additional web servers.

 

 

 

Last modified
14:02, 10 Oct 2016

Tags

Classifications

Public