SUP Server (Software Update Point) Configuration Manager actually uses the WSUS service. WSUS Of course, it needs a database, which can be hosted on a "real SQL Server" or on Windows Internal Database. However, there are times when the SUP cannot contact the database and leaves ugly-looking entries in the Configuration Manager log:
In such a situation, it is natural to check whether the database exists and is accessible via the network. It turns out that although the database exists and is accessible (to the checking administrator), from the point of view of the SMS_WSUS_CONTROL_MANAGER service it is no longer so. Further tracing reveals a notation in the log:
"System.Data.SqlClient.SqlException (0x80131904): Cannot open database "SUSDB" requested by the login. The login failed."
Since the computer account (the WSUS server account) should be authorized for the WSUSDB database, so further exploration on the SQL server side revealed that, relative to the SUSDB database, this account actually had too few permissions:
Marking the role of webService very quickly healed the SUP server, which after a short time began to work properly.
In this case, the firewall (firewall) and antivirus program traditionally accused of all kinds of malfunctions were completely innocent, and the whole malfunction was due to an incorrect setting (configuration) on the SQL database side.