Error connecting to the Windows Server Update Services database

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

gurvinder.nijjar - 29 Dec 2005 10:34 GMT

Every time I connect to the WSUS admin console I get the following error
message:

Error connecting to the Windows Server Update Services database
There was an error connecting to the Windows Server Update Services
database. Either the database is not available or you do not have the
correct privileges to access the database.

If you believe you have received this message in error, please check with
your system administrator.

In event viewer I also get an error log with event id: 421.

The only thing i did on my server was change the server name and IP of the
server. I have changed the server back to its original server name and IP
address.

I have checked the services the Background intelligent service is running.
The SQLAgent$WSUS service is not running. Should this be running.

Is there anything else I can check.

Reply to this Message

Lawrence Garvin (MVP) - 29 Dec 2005 19:54 GMT

The SQLAgent$WSUS service should not be running on an (W)MSDE installation.
It /might/ be running on an SQL Server 2000 named instance installation if
you have used the Database Maintenance utilities to configure scheduled
maintenance or scheduled backups of the WSUS named instance.

Changing the server name and/or IP Address should not interfere with normal
WSUS operations, unless you have also configured IIS to use Host Headers
and/or specified IP Addresses, in which case they might not be able to
respond to the new name. If there are no host headers configured, and "All
Unassigned" is configured, then IIS should respond to any HTTP GET request
sent to the machine, regardless of the name resolution used to obtain the IP
Address.

However, there is also a registry key that identifies the location of the
database server. The key is located at:

HKLM\SOFTWARE\Microsoft\Update Services\Server\Setup\

and it should contain a value "SQLServerName" with data pointing to your
WSUS instance. If this key has the actual name (or original name) of the
server (rather than (local) or localhost), this would account for the
inability to find the database server after renaming the WSUS server.

My default instance on SBS2003 is set to %computername%, so it's also
possible that an installation on a named instance would be
%computername%\WSUS (I don't have a named instance available to verify
against.) This could also be an issue if the environment variable
%computername% did not get properly redefined after changing the name of the
server.

> Every time I connect to the WSUS admin console I get the following error
> message:
[quoted text clipped - 17 lines]
>
> Is there anything else I can check.

Reply to this Message

gurvinder.nijjar - 30 Dec 2005 10:56 GMT

Thnaks for the feedback.

I am not using any host headers, and have been using unassigned Ip
addresses.

I have checked the registry key and it is set to %computername%\WSUS. So
everything seems normal.

Are there any ideas.

I have changed the server back to its original name.

Is ir worth reinstalling WSUS again.

> The SQLAgent$WSUS service should not be running on an (W)MSDE
> installation. It /might/ be running on an SQL Server 2000 named instance
[quoted text clipped - 49 lines]
>>
>> Is there anything else I can check.

Reply to this Message

Lawrence Garvin (MVP) - 31 Dec 2005 02:10 GMT

The cost of reinstalling WSUS is rather small, as you can retain the
database and content, and the uninstall/reinstall process takes less than 30
minutes.

If something has gotten out of kilter, a reinstall should rectify any such
issue.

> Thnaks for the feedback.
>
[quoted text clipped - 62 lines]
>>>
>>> Is there anything else I can check.

Reply to this Message