Export (0) Print
Expand All

Issues with Update Storage

Applies To: Windows Server 2003 with SP2, Windows Server Update Services

Updates can be stored on the local WSUS server or on Microsoft Update. Use this section to troubleshoot problems with update storage.

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 utility reset command. For more information about WSUSUtil, see Managing WSUS 3.0 from the Command Line.

noteNote
Performing a reset causes the WSUS server to be unresponsive for up to five minutes.

  1. Open a command window.

  2. Navigate to the directory that contains WSUSutil.exe. (It can be found in the Tools subdirectory of the WSUS installation directory.)

  3. Type wsusutil reset

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. In other words, 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 itself (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.

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 drive.

  • Using the Server Cleanup Wizard to remove unneeded content. For more information about this wizard, see Using the Server Cleanup Wizard.

  • Moving the content directory to another drive.

  • Moving the SQL Server database to another drive.

  1. Click Start, click All Programs, click Accessories, click System Tools, and then click Disk Cleanup.

  2. Select the Windows components, applications, and files that can be removed, and then click OK.

  1. Create a new content directory on another drive.

  2. Locate the WSUSUtil.exe utility in the Tools directory of your WSUS installation (typically C:\Program Files\Update Services\Tools).

  3. Open a command 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.

noteNote
For more information about using the WSUSUtil utility, see Managing WSUS 3.0 from the Command Line.

Before you move the SQL Server installation to another 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 clients are communicating with the server.

  1. Open a command window.

  2. Type net stop wsusservice

  3. Detach the SUSDB database.

  4. Copy SUSDB.mdf and SUSDB_log.ldf to the new location.

  5. Attach the SUSDB database from the new location.

  6. Type net start wsusservice

  7. When the system is working properly, delete SUSDB.mdf and SUSDB_log.ldf from the old location.

noteNote
Consult your SQL Server documentation to find out how to detach and reattach databases.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft