Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics GP forum / Posting interruption e...
Microsoft Dynamics GP forum
Unanswered

Posting interruption error PRIMARY' filegroup is full (see full error below)

(0) ShareShare
ReportReport
Posted on by Peggy Aitken 88
The following posting interruption was incurred:
 
Initial Error:
Unhandled database exception:
A save operation on table 'IV_Distribution_HIST'  (45).
[Microsoft][SQL Server Native Client 11.0][SQL Server]Could not allocate space for object 'dbo.IV30500' in database 'EMC' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding add
EXCEPTION_CLASS_DB
DB_ERR_SQL_OBJ_NOT_FOUND
 
2nd Error After I pressed OK on the PRIMARY filegroup is full:
Batch INV07 failed to complete posting Use the Batch Recovery window to complet the posting process
MORE INFO:
Transaction not completed at initiating scripts exit, implicitly rolled back.
 
I checked disk space and there is PLENTY of space on the C:// where the database is located and on the D:// where GP is installed.
 
 
I also checked the database properties and everything looks fine there too
 
 
Can someone please help.  I don't know where to go from here.
Categories:
Distribution
  • Suggested answer
    David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,781 Super User on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
    Peggy has upgraded the customer to a full SQL Server version without the 10GB limit introduced by SQL Server Express and the issue is resolved.
     
    This 10GB limit was also the cause of the upgrade failure in the previous thread
     
  • Peggy Aitken Profile Picture
    Peggy Aitken 88 on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
    I'm in a world of hurt here now.  My log file + database size exceeds the 10gig SQL Express Max size. I thought I could shrink the log file but shrink doesn't seem to change the log file size.  I didn't have to change it to simple recovery because it was already on simple.  But, the log file size remains 1425472 and it's supposed to set back to 20mb.  Any suggestions so we can get thru until we move over to the full version of SQL.  HOPING that allow us to not have to spend Thanksgiving moving the data to the full version of SQL.
     
     
  • Peggy Aitken Profile Picture
    Peggy Aitken 88 on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
     
    David,
     
    Thank you SO much for your quick response.
     
    Can I shrink the log file to buy a little time so we don't have to do this over Thanksgiving?  Do you know what the ramifications are of doing so?  I know how to shrink just the log, not the entire database.   Or, if they choose to clear some history, is there a chance it will blow while doing so because of temp files?
     
    Thanks,
  • David Musgrave MVP GPUG All Star Legend Moderator Profile Picture
    David Musgrave MVP ... 13,781 Super User on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
    My quick research says online agrees with your assessment. You have hit the 10GB limit for SQL Server Express. Deleting PJOURNAL granted you a temporary reprieve, but you will hit it again very soon.
     
    Time to go to full SQL Server version.
     
  • Peggy Aitken Profile Picture
    Peggy Aitken 88 on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
    One more point.  I was able to post the batch that blew in posting AFTER I deleted the PJOURNAL.  Now everyone was able to post all batches thru.  With that said, I still think it's a problem with the database size over 10gb.  Meaning it's time to move to the full SQL Version?
     
    Thanks,
  • Peggy Aitken Profile Picture
    Peggy Aitken 88 on at
    Posting interruption error PRIMARY' filegroup is full (see full error below)
    Could this be the cause of my error?  
     
    When we set the value of the MAXSIZE parameter limited to a specific value, we might encounter the Primary filegroup is full error. This error also occurs when we are using the SQL Server express edition. The maximum allowed size of the database in SQL Server Express edition is 10GB. When the database tries to grow beyond 10GB, the user will encounter the Primary filegroup is full error.
     
    Their .mdf & .ldf files together are over 10gb
     
     
     

Helpful resources

Quick Links

Community Spotlight of the Month

Kudos to Mohamed Amine Mahmoudi!

Blog subscriptions now enabled!

Follow your favorite blogs

TechTalk: How Dataverse and Microsoft Fabric powers ...

Explore the latest advancements in data export and integration within ...

more Community News

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 284,876 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,425 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,146

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans