1. Home
  2. Support
Article - CS257488

Error "Could not allocate space for object 'X' in database <DB_Name> because the 'PRIMARY' filegroup is full" with various operations in Windchill PDMLink

Modified: 22-Apr-2025   


Applies To

  • Windchill PDMLink 10.0 to 13.0

Description

  • Upload or download fails with the error message:  
    Could not allocate space for object 'X' in database <DB_Name> because the 'primary' filegroup is full. 
Create disk space by deleting uneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
  • Failed to check in or upload new CAD data from workspace to Windchill server with
    • Conflict message in Conflict Management window 
      • A persistence error occurred. System message follows:
    • Error in Methods Server Logs  
      com.microsoft.sqlserver.jdbc.SQLServerException: Could not allocate space for object '<DB_Name>.QueueEntry'.'QueueEntry$COMPOSITE0' in database '<DB_Name>' because the 'INDX' 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.
  • Add to Workspace window gets frozen or keeps loading, cannot load data from server to workspace
  • Creating a new Workspace failed with the JavaScript Warning below even if the user has all necessary access permissions:  
    You do not have access to this object or it does not exist
  • Reassign Utility is failing with above error
  • Unable to create New Option with Persistence Error
  • Failed to check in any Documents or WTParts in standalone browser with the message below in pop-up window: 
    Attention:
Could not allocate space for object '<DB name>.RawMethodContextStats' in database '<DB name>' 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.
  • Users are not able to open any Creo files
  • Below error occuring in Methodserver.log   
    ERROR [wt.log4j.jmx.AsyncJDBCAppender.worker-2] wt.log4j.jmx.AsyncJDBCAppender  - RawMethodContextStats: execute batch failed
    ERROR [wt.log4j.jmx.AsyncJDBCAppender.worker-2] wt.log4j.jmx.AsyncJDBCAppender  - RawMethodContextStats: flush all failed com.microsoft.sqlserver.jdbc.SQLServerException: The database 'xxxx' has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:262)
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1624)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatementBatch(SQLServerPreparedStatement.java:2800)
This is a printer-friendly version of Article 257488 and may be out of date. For the latest version click CS257488