Skip to content
  • There are no suggestions because the search field is empty.

Could not allocate a new page for database 'UnifyDB' because of insufficient disk space in file group 'PRIMARY'. Create the necessary space by Dropping objects in the file group, adding additional files to the filegroup

This article helps Webgility Desktop users in resolving the “Could not allocate a new page for database 'UnifyDB' because of insufficient disk space in file group 'PRIMARY'” error in Webgility Desktop. It explains that the issue arises when the SQL Server hosting the Webgility Desktop database lacks sufficient disk space or requires optimization. The article provides step-by-step guidance on running the UnifyDBUtility to optimize the database, freeing up disk space by reviewing and managing SQL Server logs, and relocating or removing unnecessary files to restore normal application performance.

Error Message:

Could not allocate a new page for database 'UnifyDB' because of insufficient disk space in file group 'PRIMARY'. Create the necessary space by Dropping objects in the file group, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

 

Cause of the issue:

This issue is not linked to a specific action in the application but is related to its performance. The error indicates that the SQL Server application hosting your Webgility Desktop database needs optimization or that the drive hosting the SQL Server application is running out of space. To resolve this issue, optimize the Webgility Desktop database and relocate or remove unnecessary files.

 

Steps to fix:

1. Need to optimize Webgility Desktop Database by running “UnifyDBUtility”.

2. Free up disk space

  • Check SQL Server logs - review and delete the SQL logs if they are consuming space on the drive, MSSQL logs can be found at the location C:\Program Files\Microsoft SQL server\MSSQLXX.YY\MSSQL\Log

Note: XX is the SQL Server version & YY is your Webgility Database instance name. Kindly consult with your Sys/Admin OR IT before deleting any SQL logs.

 

Move the unwanted files to another drive to free up space and ensure smooth application performance.