KB2720211 issues?

Seeing a error code 1603 according to MySetup.log in 2720211 install?


Pete Perry got this and reported the following:


Can you see if you have a MWussetup.txt file and what it says?


He said….



MWusSetup.txt file in the temp folder with the below…



2012-06-10 08:53:26 Success CustomActions.Dll Successfully set propery of WSUS admin groups’ full names

2012-06-10 08:53:31 Error CustomActions.Dll ExecuteQueryGetMultipleResults: GetRows returned error (Error 0x800A0BCD)

2012-06-10 08:53:31 Error CustomActions.Dll GetDatabaseLocation: Failed to execute SQL query EXEC dbo.sp_helpdb ‘%s’ (Error 0x800A0BCD)

2012-06-10 08:53:31 Error CustomActions.Dll SetWyukonInstallDirProperty: Failed to get installed location of SUSDB in WYukon (Error 0x800A0BCD)

2012-06-10 08:53:31 Error CustomActions.Dll SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x800A0BCD)

2012-06-10 10:25:16 Success CustomActions.Dll Successfully set propery of WSUS admin groups’ full names

2012-06-10 10:25:21 Error CustomActions.Dll ExecuteQueryGetMultipleResults: GetRows returned error (Error 0x800A0BCD)

2012-06-10 10:25:21 Error CustomActions.Dll GetDatabaseLocation: Failed to execute SQL query EXEC dbo.sp_helpdb ‘%s’ (Error 0x800A0BCD)

2012-06-10 10:25:21 Error CustomActions.Dll SetWyukonInstallDirProperty: Failed to get installed location of SUSDB in WYukon (Error 0x800A0BCD)

2012-06-10 10:25:21 Error CustomActions.Dll SetUnInstallProperties: Failed to set WYUKON install directory (Error 0x800A0BCD)


I searched on WYUKON and found a posting to change the key under HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\wYukonInstalled to 0 and sure enough the standalone update finally installed. From what I understand changing this key tells the installer to not look for the existing database. I rebooted (which prompted to do so) and the WSUS console came up this time without MMC load errors but WSUS was still offline. I then set the wYukonInstalled key back to 1, ran the WSUS update again which did complete successfully, rebooted and viola…WSUS came up and utilizing the exiting database.


EDIT:  Please also see http://byronwright.blogspot.nl/2012/06/kb-2720211-kills-wsus.html


 

14 Thoughts on “KB2720211 issues?

  1. MarS on June 13, 2012 at 2:08 am said:

    The solution by Pete P solve the problem with KB2720211 error 1603 in our case on Windows Server 2003 + WSUS 3.0 SP2 installed. Thank you very much.

  2. WilliamL on June 13, 2012 at 4:02 pm said:

    This solved the problem with KB2720211 error 1603 in our case on Windows Server 2008R2 (SBS 2011 Std) + WSUS 3.0 SP2. Thanks so much!

  3. El_Loco on June 14, 2012 at 1:53 am said:

    You saved me so many hours of work. Was going mad with thtt error ! Thanks a thousand times !!!

  4. Bill Peavy on June 14, 2012 at 10:04 am said:

    This helps a great deal.

    However, WSUS still cannot connect to its database. There’s chatter about SUSDB being switched to single-user mode during the abortive initial states of trying to install KB2720211 and that it needs to be switched back to multi-user mode to finally get WSUS back on the air.

    I’m running Windows Internal Database on SBS 2003 SP2 (not R2) and there doesn’t seem to be a way to try this. Does anyone know how to do this with WID? Can the SQL 2005 Express Admin tool be used with WID?
    TIA

  5. Bill Peavy on June 14, 2012 at 1:54 pm said:

    I’ve installed SQL 2005 Express Admin but cannot connect to the SUSDB.

    Admin will connect to SBSMonitoring and SHAREPOINT but not to the WSUS database.

    I’m really lost here. (I’m in SO far over my head.)

    AFAIK, KB2720211 really resembles MALWARE!

    My SUSDB.mdf and SUSDB_log.ldf are both there, still where I had put them, but I can’t get connected.

    Really need some help here.

  6. Gabe on June 14, 2012 at 6:05 pm said:

    Changed key to 0, installed successfully (yay!) rebooted, going into WSUS, the MMC displays “Connection Error” just like it did before. Changed the key back to 1 and I’m getting the 1603 when trying to reinstall.

    So I did the change to 0 again and successfully installed again, but WSUS is just not working.

    Event viewer is loaded with event 33002 for source MSSQL$MICROSOFT##SSEE. Description reads “Access to module dbo.xxxxxxxx is blocked because the signature is not valid” (where xxxxxx is any number of different SQL procedures).

    Something else over the last couple of days…my Server Performance Report from the SBS server is being emailed but the body is just an HTML error, “The page cannot be displayed”

    Any thoughts?

  7. RogerS on June 16, 2012 at 2:43 pm said:

    Same here. Using this tip WSUS is partially repaired. Now I cant connect to the DB. Same problem as Bill, anyone any thoughts??

  8. RogerS on June 16, 2012 at 3:04 pm said:

    Update.

    Got it fixed. After the registry trick I followed instructions in http://byronwright.blogspot.nl/2012/06/kb-2720211-kills-wsus.html . I skipped the SQL part since it’s not needed for the internal db.

  9. Stupid update. I looked through this info and the other articles it links to, but decided I was sick of it and just uninstalled / reinstalled WSUS. Yay Microsoft. Quality updates since … never.

  10. Microsuck does it again…and no where are they responding to this issue. I have tried fixes from different people and nothing works, trashing my update server and spinning up a new one…oh well chalk it up to experience, again!

  11. bradley on June 22, 2012 at 12:12 pm said:

    http://blogs.technet.com/b/sus/archive/2012/06/20/wsus-kb272011-common-issues-encountered-and-how-to-fix-them.aspx
    Yes they are. Blogged there.

    Also call 1-800-Microsoft support, it will be a free call.

  12. Kevin on July 11, 2012 at 10:13 am said:

    We beat this problem to death too. finally decided to re-install WSUS Update to original SP2 and leave it that way.
    This was way too much work for a simple Update. There are a lot of other things we could have done with out time.
    Doesn’t anbody test these things?

  13. Atlanta Jack on July 25, 2012 at 8:45 am said:

    This one really broke WSUS. I have attempted reinstall & am having major problems getting it to run a new install which keeps failing. One of the delightful things this update does in my case was to make a graceful uninstall not work. I had done this one before and it worked: http://technet.microsoft.com/en-us/library/gg680316.aspx#BKMK_ToManuallyRecover

    Pretty good article but it fails to tell you to remove WSUS web site and App pool.

    It did not work for me this time

    This KB does not remove WID. I have even removed WID and cannot get the reinstall to work….

  14. Atlanta Jack on August 1, 2012 at 10:58 am said:

    If you choose to reinstall WSUS, DO NOT UNINSTALL Windows Internal Database if it is not broken. Many Bloggers are saying to do this. If you do uninstall WID, rename the C:\Windows\Sysmi to Sysmi.old. Most data out there on the Blogs says to rename C:\Windows\Sysmi\SSEE\MSSQL.2005\Data to Data.old. If you do it like this Windows Internal Database will not reinstall and you will have many new gray hairs. Susan pegged this right…pick up the phone and call Microsoft. they will N/C it if you get someone with sense! I had to call twice!

    SuperGumby & Others…Lighten Up!!! Susan is trying to help folks like us! Have a nice unbroken WSUS day!

Post Navigation