(skip to the next post for a solution without explaination)
So here is the error in question.
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
For some reason, when my WSUS server applied patches to itself, that is the error I got when I tried to open the WSUS admin console.
So after I did some research I found that I had some errors in my Event Viewer related to Microsoft SQL Server Desktop Environment 2000(MSDE 2000).
(To open Event Viewer go to Start --> Adminstrative Tools --> Event Viewer) This is the Error.
Connection to database failed. Reason=Cannot open database requested in login 'SUSDB'. Login fails.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.. Connection string: Data Source=GTCMPM;Initial Catalog=SUSDB;Connection Timeout=60;Application Name=WSUS SQL Connection;Trusted_Connection=Yes;Pooling='true'; Max Pool Size = 100
For more information, see Help and Support Center at http://go.microsoft....link/events.asp.
So I checked to see if the MSSQLSERVER Service was running, not only was it NOT running, but it was gone altogether.
(To open Services go to Start --> Adminstrative Tools --> Services).
I ran a search for MSDE on the C: to see if I can locate the database, an instance, or anything MSDE related. The search results pulled up a log file in C:\Program Files\Update Services\LogFiles. I reviewed a few of the log files (not really knowing what I was looking at), when I came across a relatively recent log file named WSUSSetup_070629_0403.log The portion of the filename "070629_0403" is just a date stamp, so you want to look for "WSUSSetup" in the directory C:\Program Files\Update Services\LogFiles.
This is what the file said.
2007-06-29 04:03:24 Success MWUSSetup Parsing command line arguments
2007-06-29 04:03:24 Success MWUSSetup WSUS Setup: Performing maintainance
2007-06-29 04:03:40 Success MWUSSetup Determing the installation details
2007-06-29 04:03:50 Error MWUSSetup Failed to delete path C:\Program Files\Update Services\Selfupdate2, error code 1026 (Error 0x00000000: The operation completed successfully.)
2007-06-29 04:07:33 Success MWUSSetup Database backup has beenn created at E:\WSUS\SUSDB.Dat. You can use this file to restore the database, if there is an upgrade failure
2007-06-29 04:08:35 Success MWUSSetup WMSDE Uninstall Succeeded
2007-06-29 04:08:35 Success MWUSSetup WMSDE SP3 Uninstalled successfully
2007-06-29 04:08:35 Success MWUSSetup Installing WMSDE
2007-06-29 04:09:19 Error MWUSSetup WMSDE Installation Failed (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:19 Error MWUSSetup InstallWMSDE Failed (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:19 Error MWUSSetup Failed to install WMSDE (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:21 Error MWUSSetup PerformUpgrade failed (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:21 Error MWUSSetup Failed to upgrade Windows Server Update Services from RTM to SP1 (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:21 Error MWUSSetup WSUS Setup: Performing Maintenance Failed. (Error 0x80070643: Fatal error during installation.)
2007-06-29 04:09:21 Error MWUSSetup WSUS Setup Failed. (Error 0x80070643: Fatal error during installation.)
I have bolded 3 lines. So you can understand what I am talking about. First, the line that caught my eye was "WMSDE SP3 Uninstalled successfully." And then "WMSDE Installation Failed." This tells me WSUS has removed the database probably to install an upgraded version of MSDE, but then has problems installing the new version. So now I know, that WSUS has a console but no database to connect to. The errors in the Event Viewer and the lack of the service MSSQLSERVER confirms this. The 3rd bolded line is what's gonna save you from doing ALOT of extra work when it comes to restoring WSUS. The database is backed up and now we know where.
So now how did I fix this? Go on to the next post.