While reviewing my WSUS reports (exported to Excel) I found that I could streamline extracting the KB article from the exported report using a basic formula in Excel.
Here’s the excel formula.
=LEFT(RIGHT(D9,10),LEN(RIGHT(D9,10))-1)
Category: WSUS
Cannot open database "SUSDB" requested by the login.
I’m receiving this error message on my WSUS 3.0 SP2 server. The proposed fix ((http://social.technet.microsoft.com/Forums/windowsserver/en-US/e918a191-ef6d-4c4b-b83a-7a4ae20a5217/wsus-30-sp2-will-not-run-after-installing-update-2720211?forum=winserverwsus)) indicates to perform the following.
- Download the KB2720211 from Microsoft: http://support.microsoft.com/kb/2720211
- Open Regedit, and change the value of this DWORD to 0:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\wYukonInstalled - Install KB2720211
- Change the DWORD value back to
1 - Stop the SQL database service (I used Windows Internal Database, so it is
MSSQL$MICROSOFT##SSEE) - Delete the DB files in
*:\WSUS\UpdateServicesDbFiles(SUSDB.mdf&SUSDB_log.ldf) - Restore the
SUSDB.mdf&SUSDB_log.ldffrom backup - Start the SQL database service
- Start the Update Services service
WSUS3 SP2 Service Problem
I was checking a few systems this morning and came across this glorious error.
Easy enough to fix, right? Just go to Administrative Tools > Services and restart the Windows Server
Update Services service, right?
Of course not!
That service doesn’t exist. I have WSUSCert ((Something cool)) service, but not the server service. So now I’m downloading WSUS 3.0 SP2 again to re-install on top of this to maybe fix the problem.
Stay tuned!
Update 1
Installing WSUS 3.0 SP2 causing removal of Windows Update Service; I left the database and synchronization data and logs in place.
After uninstall, I ran the WSUS 3.0 SP2 executable again and it began an install; I chose the location of my previous Windows Update Service Server install as well as told it to use the existing database and the default IIS website.
Update 2
It’s been a few days but I think I stumbled upon a way to recover from this issue. Things just got real messy but this may be the working solution.
Force client computer to detect and install new updates using WSUS
The time period in which computers will check for updates on WSUS server is 22 hours (default). However, you can have the client computer check manually by using the following command line:
wuauclt /resetauthorization /detectnow
If that doesn’t initially work, you can try a little more advanced option here involving removing some registry entries and running the same command to force it to check for updates.
@echo off net stop wuauserv REG DELETE "HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate" /v PingID /f REG DELETE "HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLMSoftwareMicrosoftWindowsCurrentVersionWindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow wuauclt /reportnow
Force client computer to report to WSUS
You can force your computer to report its status to the WSUS server by issuing the following command:
wuauclt /reportnow
More information is available on the TechNET page: http://technet.microsoft.com/en-us/library/cc720477(v=ws.10).aspx