Issues with the Database

If you have problems with the SQL Server database or Windows Internal Database, make sure that the WSUS database in question is in the correct SQL instance before starting to troubleshoot SQL issues.

noteNote
You will need to use the sqlcmd utility, which can be downloaded from Feature Pack for Microsoft SQL Server 2005 (http://go.microsoft.com/fwlink/?LinkId=81081). For more information about the sqlcmd utility, see sqlcmd Utility (http://go.microsoft.com/fwlink/?LinkId=81183).

Troubleshooting database issues

Ensure that the WSUS database is in the correct SQL instance

To ensure that the WSUS database is in the correct SQL instance

  1. Verify the SQL server name by opening a command window and typing the following:

    Reg query "HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup" /v SqlServerName

    The output contains the SQL server name to be used in the next step.

  2. Type the following:

    sqlcmd -S SqlServerName -E -d SUSDB

    Review any error messages and correct the problems.

If you are using Windows Internal Database as the WSUS database, use the following string in place of SqlServerName in the above command:

np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Tags :


Community Content

Vadims Zenins
WSUS 3 SP1 and remote MS SQL Database with non standard IP port

Type the following:

sqlcmd -S SqlServerName,IPport -E -d SUSDB

If you connected successful change value of registry "HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\SqlServerName" to YourSqlServerName,IPport

Tags : mssql wsus

Page view tracker