[Webinar] Streamline your web hosting managementRegister Today

x
?
Solved

Windows Server Update Services Error - Webpage Dialog

Posted on 2008-10-28
13
Medium Priority
?
1,731 Views
Last Modified: 2013-11-16
I have received this error when I try to approve any more updates....
Windows Server Update Services encounted an error.
Could not allocate space for object 'tbDeadDeployment' in database 'SUSDB' because the 'PRIMARY' filegroup is full.

There is plenty of room on this server.  I do not have the full version of SQL on this server, other than the included version with WSUS.  Any ideas?
(I have attached the screen shot of the error.)
WSUSError.jpg
0
Comment
Question by:shrimpfork
  • 7
  • 6
13 Comments
 
LVL 14

Accepted Solution

by:
Hedley Phillips earned 2000 total points
ID: 22821477
Has your database reached the 2gb limit?
0
 
LVL 14

Expert Comment

by:Hedley Phillips
ID: 22821505
Also,

what are the event ID's you are receiving?


0
 

Author Comment

by:shrimpfork
ID: 22821513
I'm not sure where to look for that.  Where does the WSUS store the database?
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 

Author Comment

by:shrimpfork
ID: 22821547
When the error occurs, it logs Event ID 386.  Here is what the description states....

Synchronization failed. Reason: System.Data.SqlClient.SqlException: Could not allocate space for object 'tbXml' in database 'SUSDB' because the 'PRIMARY' filegroup is full.
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.DrainObsoleteConnections(SqlException e)
   at Microsoft.UpdateServices.DatabaseAccess.DBConnection.ExecuteCommandNoResult()
   at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPImportUpdate(Int32 upstreamServerLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32& localRevisionId)
   at Microsoft.UpdateServices.Internal.DataAccess.ImportUpdate(Int32 ussRevLocalId, String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, Int32& localRevisionId)
   at Microsoft.UpdateServices.Internal.DataAccess.ImportUpdateForCatalogSync(String xmlUpdateBlob, Byte[] xmlUpdateBlobCompressed, ServerSyncUrlData[] fileUrls)
   at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ProcessNewUpdate(ServerSyncUpdateData updateData)
   at Microsoft.UpdateServices.ServerSync.CatalogS.
0
 

Author Comment

by:shrimpfork
ID: 22821569
I found what I think is the database location....the file "SUSDB.mdf" is at the 2 GB limit.  Now how do I clean this up.  My ultimate goal is to install WSUS 3.0.
0
 
LVL 14

Expert Comment

by:Hedley Phillips
ID: 22821612
Somewhere there are some steps to backup your database, reinstall WSUS using some switches to force it to use the english unthrottled WMSDE instance and then restore the database.

How to backup and restore:
http://technet.microsoft.com/en-us/library/cc708546.aspx

Read here for making space by managing WSUS DB from the command line:
http://technet.microsoft.com/en-us/library/cc720466.aspx
0
 
LVL 14

Expert Comment

by:Hedley Phillips
ID: 22821644
Here is some more info:

"The downloadable MSDE only supports a database up to 2GB in size. You need to maintain it to keep it under that limit. Your HOME page in the WSUS administration console should instruct you to run the following command:"

WSUSutil.exe deleteunneededrevisions

So, if you run that command and then you should be able to upgrade from 2.0 to 3.0
0
 

Author Comment

by:shrimpfork
ID: 22821669
I am running the WSUSUTIL.EXE utility to delete unneeded revisions to see if this reduces the size at all.
0
 
LVL 14

Expert Comment

by:Hedley Phillips
ID: 22821704
I am not sure if you can upgrade over the top of 2.0 with a db that has reached the 2gb limit. You might be able to, I just don't know.

Try reducing the size first and then if that doesn't work try updating anyway. I am sure it will moan if it can't manage it. It is Microsoft after all.
0
 

Author Comment

by:shrimpfork
ID: 22822136
While running the WSUSutil.exe deleteunneededrevisions, it encountered the same error:

Database cleanup encountered an error, please check your server and try again
Fatal Error: Could not allocate space for object 'tbDeadDeployment' in database
'SUSDB' because the 'PRIMARY' filegroup is full.

The size was not reduced.  I would like to fix this before I upgrade to 3.0.
0
 

Author Comment

by:shrimpfork
ID: 22825529
I am at a loss here.  I'm thinking about removing WSUS 2.0 and installing 3.0.  Your thoughts?
0
 
LVL 14

Assisted Solution

by:Hedley Phillips
Hedley Phillips earned 2000 total points
ID: 22865677
Hi,

sorry for the delay in replying.

Uninstalling 2.0 is certainly an option. It won't take too long for 3.0 to download all the updates either. Esp if you make BITS run in the foreground.

WsusDebugTool /Tool:SetForegroundDownload
0
 

Author Comment

by:shrimpfork
ID: 22867295
I have already proceeded on this and have installed 3.0.  Thanks for your help.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, we’ll look at how to deploy ProxySQL.
Creating a Cordova application which allow user to save to/load from his Dropbox account the application database.
SQL Database Recovery Software repairs the MDF & NDF Files, corrupted due to hardware related issues or software related errors. Provides preview of recovered database objects and allows saving in either MSSQL, CSV, HTML or XLS format. Ensures recov…
Stellar Phoenix SQL Database Repair software easily fixes the suspect mode issue of SQL Server database. It is a simple process to bring the database from suspect mode to normal mode. Check out the video and fix the SQL database suspect mode problem.

591 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question