On server which I'm using for WSUS 3, one day i found this:
The WSUS administration console was unable to connect to the WSUS Server Database.
Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
System.Data.SqlClient.SqlException — Cannot open database "SUSDB" requested by the login. The login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
Source
.Net SqlClient Data Provider
Stack Trace:
at Microsoft.UpdateServices.Internal.BaseApi.SoapExceptionProcessor.DeserializeAndT
hrow(SoapException soapException)
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccessProxy.ExecuteSPG
etTargetGroupById(Guid id)
at Microsoft.UpdateServices.Internal.BaseApi.ComputerTargetGroup.GetById(Guid id, UpdateServer updateServer)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetComputerTargetGroup(Guid id)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.TestSqlConnection(IUpdateServer server)
at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.GetUpdateServer(PersistedServerSettings settings)
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.ConnectToServer()
at Microsoft.UpdateServices.UI.SnapIn.Scope.ServerSummaryScopeNode.get_ServerTools()
I have no idea what the problem might be, 'cause my knowledge about DB's are minimal.
OS is Windows 2003 Server SP2, and nothing was changed or touched in server or system itself. Just one day, it didn't work anymore. Database is Microsoft SQL 2005
Any ideas?
Best Answer
Log onto the WSUS server, and find the folder that SQL is installed in C:\Program Files\Microsoft SQL Server\MSSQL.1\ by default. Under that find the Log folder (should be under .\MSSQL\Log) and find the ERRORLOG file with no extension. That should give you a better idea as to what's going on, if there's a database problem to deal with.
Failing that you may need to install the SQL Express Management Studio on the machine and connect to the database to see what's going on / correct the problem.