locked
Cannot Free Space on WSUS Drive RRS feed

  • Question

  • I am fairly new to WSUS so if there is an obvious solution to this please forgive me. I happened to be checking the queue on my WSUS server when I recieved a notification that the drive where all of the WSUS data is stored is full. As in 0 bytes of space. I guess I didn't check it enough. Anyway, I try to run the Server Cleanup wizard and it crashes. Is manually deleting the data an option, if I knew what to delete? Thanks in advance for the help.
    Matt Georgetti
    Wednesday, May 13, 2009 7:48 PM

Answers

  • It's likely crashing because the database (also stored on that drive, most likely) is stopped or corrupted.

    If the database, filestore, and OS are all on the C: drive, and you have zero bytes of free space, it's quite likely you're going to need to reinstall WSUS (unless you have a recent backup of the database). To start, though, you should free up space from the typical culprits -- temp folders, IE cache, unneeded $NTInstall$ folders. From there, you might be able to restart the database service (assuming it crashed and is stopped), and the Update Services service and run the Server Cleanup Wizard.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    • Proposed as answer by Yog Li Wednesday, May 27, 2009 2:24 AM
    • Marked as answer by Eric Zhang CHN Wednesday, May 27, 2009 5:41 AM
    Wednesday, May 13, 2009 10:24 PM

All replies

  • It's likely crashing because the database (also stored on that drive, most likely) is stopped or corrupted.

    If the database, filestore, and OS are all on the C: drive, and you have zero bytes of free space, it's quite likely you're going to need to reinstall WSUS (unless you have a recent backup of the database). To start, though, you should free up space from the typical culprits -- temp folders, IE cache, unneeded $NTInstall$ folders. From there, you might be able to restart the database service (assuming it crashed and is stopped), and the Update Services service and run the Server Cleanup Wizard.
    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    • Proposed as answer by Yog Li Wednesday, May 27, 2009 2:24 AM
    • Marked as answer by Eric Zhang CHN Wednesday, May 27, 2009 5:41 AM
    Wednesday, May 13, 2009 10:24 PM
  • Lawrence,

    It is actually on a separate drive. I will try playing around with the services. Is there a way to manually delete some of the data?
    Matt Georgetti
    Thursday, May 14, 2009 12:08 PM
  • apologizes for the delay in responding, i had the same trouble and I resolved it as follows: (Maybe this solution helps others)

    according Terence Liu [MSFT]:

    1. Use "WsusDebugTool.exe /Tool:PurgeUnneededFiles" command to purge unused
    files.

    You can download the tool from
    http://technet.microsoft.com/en-us/wsus/bb466192.aspx

    Note: The Server Diagnostic Tool.

    2. If you need move the content to another hard disk with higher capacity just use WSUSutil command with movecontent option to change the file system
    location where the WSUS Server stores update files. For more info, please
    refer to:

    http://technet2.microsoft.com/WindowsServer/en/library/2686bd2b-910a-479b-96
    1e-cea2a20280241033.mspx?mfr=true




    • Proposed as answer by z0x Tuesday, May 3, 2011 8:23 PM
    Tuesday, May 3, 2011 8:08 PM
  • according Terence Liu [MSFT]:

    1. Use "WsusDebugTool.exe /Tool:PurgeUnneededFiles" command to purge unused
    files.

    You can download the tool from
    http://technet.microsoft.com/en-us/wsus/bb466192.aspx

    I hope this information is coming from an ancient post.

    The correct tool to use to manage the file system contents in a WSUS v3 server is the Server Cleanup Wizard.

    The WSUSDebugTool is a WSUS v2 utility, and specifically the /Tool:PurgeUnneededFiles command is only applicable to WSUS v2 environments.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, May 4, 2011 4:00 PM
  • according Terence Liu [MSFT]:

    2. If you need move the content to another hard disk with higher capacity just use WSUSutil command with movecontent option to change the file system
    location where the WSUS Server stores update files. For more info, please
    refer to:

    http://technet2.microsoft.com/WindowsServer/en/library/2686bd2b-910a-479b-96
    1e-cea2a20280241033.mspx?mfr=true




    If the database and content store are on the same drive, and that drive is not the SYSVOL, then moving the content store to another available volume, using wsusutil movecontent would be the best option (provided that the database has not already been damaged by the out-of-space issue).

    If the database and content store are on the same drive, then the multiple opportunities I suggested in my original reply are still applicable to the SYSVOL, and both the database and content store should be evaluated for being moved somewhere else. Inasmuch as the content store is potentially as much as 3x to 4x the space consumption as the database, and it's much eaiser to move, effort should be placed on moving the content store first.

    The database files, if necessary, can be moved using the standard detach-move-attach procedure described in the SQL Server documentation, as well as in several threads in this forum.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2011)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Wednesday, May 4, 2011 4:04 PM