Issues with Update Storage
Updated: July 19, 2011
Applies To: Windows Server 2003 with SP2, Windows Server 2008 R2, Windows Server 2008 R2 with SP1, Windows Server Update Services, Windows Small Business Server 2011 Standard
Updates can be stored on the local WSUS server or on Microsoft Update. Use this section to troubleshoot problems with update storage.
Troubleshooting update storage
The updates listed in the WSUS administrative console do not match the updates listed in your local folder
This can happen under different circumstances. For example, if updates are stored on a disk separate from the one on which WSUS is installed, and that disk fails, when you replace the failed disk with a new (empty) disk, the WSUS application will still show all of the updates as downloaded.
To have WSUS resynchronize the updates in local storage with the updates in the database, you must run the wsusutil reset command. For more information about the wsusutil tool, see Manage WSUS 3.0 SP2 from the Command Line.
Resetting the WSUS server causes it to be unresponsive for up to five minutes.
To have WSUS verify locally stored updates
Open a Command Prompt window.
The wsusutil tool is located in the WSUSInstallDrive:\WSUSInstallDirectory\Tools folder on WSUS servers.
Type wsusutil reset.
Downloads from a WSUS server are failing
There may be problems with the permissions on the WSUS server's local content directory. Permissions are set correctly by WSUS setup when the directory is created, but subsequent changes may have reset these permissions. One indication of this problem may be event ID 10012 in the Application log file.
The following permissions are necessary:
The root folder of the local content directory must have at least Read permissions for the Users security group and the NT Authority\Network Service account. For example, if the WSUS content directory is C:\Updates\WSUSContent, the Updates directory must have the correct permissions. The BITS service will fail if these permissions are not set.
The content directory (in the above example, the WSUSContent directory) must have Full Control permissions for the NT Authority\Network Service account.
The temporary ASP.NET directory (%windir%\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files) must have Full Control permissions for the NT Authority\Network Service account.
The %TEMP% directory (usually %windir%\TEMP) must have Full Control permissions for the NT Authority\Network Service account.
The local content directory is running out of disk space
Synchronization may fail if the local WSUS content directory does not have sufficient disk space. It is recommended that you monitor disk space carefully to keep this problem from arising. Low disk space is indicated by event ID 10041 and event ID 10042.
The following procedures will help you overcome low disk space problems:
Using Disk Cleanup to remove unneeded files on the hard drive.
Using the Server Cleanup Wizard to remove unneeded content. For more information about this wizard, see Use the Server Cleanup Wizard.
Moving the content directory to another hard drive.
Moving the SQL Server database to another hard drive.
To use Disk Cleanup to remove unneeded files on the hard drive
Click Start, click All Programs, click Accessories, click System Tools, and then click Disk Cleanup.
Select the Windows components, applications, and files that can be removed, and then click OK.
To move the content directory to another hard drive
Create a new content directory on another hard drive.
Locate the WSUSUtil.exe utility in the Tools directory of your WSUS installation (typically C:\Program Files\Update Services\Tools).
Open a Command Prompt window, navigate to the Tools directory, and type the following:
wsusutil movecontent NewContentPath MoveLog
where NewContentPath is the new content directory, and MoveLog is the path and filename of the log for this operation.
For more information about using the wsusutil tool, see Manage WSUS 3.0 SP2 from the Command Line.
Before you move the SQL Server installation to another hard drive, you should make sure that the WSUS administration console is not open. If you have problems with the move, make sure that the WSUS web services have been stopped. Occasionally, a move will fail if the client computers are communicating with the server.
To move the SQL Server installation to another hard drive
Open a Command Prompt window.
Type net stop wsusservice.
Detach the SUSDB database.
Copy SUSDB.mdf and SUSDB_log.ldf to the new location.
Attach the SUSDB database from the new location.
Consult your SQL Server documentation to find out how to detach and attach databases.
Type net start wsusservice.
When the system is working properly, delete SUSDB.mdf and SUSDB_log.ldf from the old location.