We are setting up WSUS 3.0 SP2 with SCCM and have encountered a problem. On the Wsus server the event log has the following error:
"On 20.05.2010 12:33:12, component SMS_WSUS_CONTROL_MANAGER on computer ADMWSUS001 reported: Failures were reported on WSUS Server "ADMWSUS001" while trying to make WSUS database connection with SQL Exception error code -2146232060.
Possible cause: SQL Database service is not running or cannot be accessed.
Solution: Verify that the SQL Server and SQL Server Agent services are running and can be contacted."
We have set up our WSUS with a remote SQL server and, as the error says, the SQL services are not running on our WSUS server. What I am wondering is if this error is relevant? As far as i can see the patching is working properly, I have patched a couple of test servers. But many updates in the SCCM console have their deployment status set to Unknown.
I found the following error in wsusctrl.log :
System.Data.SqlClient.SqlException: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.~~ at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)~~ at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)~~ at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)~~ at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)~~ at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)~~ at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)~~ at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)~~ at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)~~ at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)~~ at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)~~ at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)~~ at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)~~ at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)~~ at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)~~ at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)~~ at System.Data.SqlClient.SqlConnection.Open()~~ at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect(String connectionString)~~ at Microsoft.UpdateServices.DatabaseAccess.DBConnection.Connect()~~ at Microsoft.UpdateServices.Internal.BaseApi.DatabaseConfigurationTester.ConnectToDatabase()~~ at Microsoft.UpdateServices.Internal.DatabaseConfiguration.ConnectToDatabase()~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.TestDatabaseConnection()
- Edited by Lawrence GarvinMicrosoft community contributor, Moderator Friday, May 21, 2010 4:02 AM marked the actual cause in boldface
- Marked as answer by Lawrence GarvinMicrosoft community contributor, Moderator Friday, May 21, 2010 4:03 AM