Could not allocate space for object
Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=29378
Printed Date: 01 April 2026 at 8:47am
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: Could not allocate space for object
Posted By: yandr
Subject: Could not allocate space for object
Date Posted: 26 May 2011 at 8:39pm
|
Dear Bruce, Do you have any idea what might be causing this? Microsoft OLE DB Provider for SQL Server Could not allocate space for object 'tblThread'.'PK__tblThread__0EA330E9' in database 'forum' 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. I am unable to post new messages, or even update existing ones. The forum works fine on my local pc, but breaks on the web hosting company, so I guess it has to do with a server configuration. Your input is very much appreciated. |
Replies:
Posted By: WebWiz-Bruce
Date Posted: 27 May 2011 at 8:04am
The part of the error message that tells you what is wrong is:-
The error means that the SQL Server Database is full. You need to contact your hosting company and ask if you can purchase additional space for your SQL Server database from them. ------------- https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting |
'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.Posted By: yandr
Date Posted: 27 May 2011 at 3:40pm
| Thank you for your answer. They truncated the log files to correct this. |
Posted By: Jagoop
Date Posted: 28 May 2011 at 6:04pm
|
If the problem was a full logfile (transaction log file on MS SQL Server), it would indicate that either: The your provider is either running the database in full recovery model and not making regular transaction log backups. -or- A long running transaction is blocking the reuse of the transaction log fil (vlogs), and that the database is running in simple recovery model. Both of the above could be a problem. |