SBS2003R2 / WSUS3.0 - Client Errors reported in Update Service MMC

Discussion in 'Update Services' started by steve841, Dec 19, 2007.

  1. steve841

    steve841 Guest

    The update services MMC shows "There are updates with installation errors. "

    The client pc's noted with installation errors all have the updates
    installed either manually or previously ..

    How do I clear these erroneous error messages out of the update services MMC??
     
    steve841, Dec 19, 2007
    #1
    1. Advertisements

  2. Odd; I would expect them to clear out automatically. Try

    wuauclt /detectnow

    on the client. It may take up to an hour for changes to be reflected in the
    server reports. If there is still a problem, post the contents of
    WindowsUpdate.log (usually in C:\windows) starting from the time you issued the
    above command. Also we'll need to know which specific updates are reported as
    failing.

    Harry.
     
    Harry Johnston [MVP], Dec 19, 2007
    #2
    1. Advertisements

  3. steve841

    steve841 Guest

    Thanks for the reply ...

    Here is the log from /detect now (I dont seen anything obvious):
    2007-12-19 14:38:13:161 1292 b34 AU Triggering AU detection through
    DetectNow API
    2007-12-19 14:38:13:161 1292 b34 AU Triggering Online detection
    (non-interactive)
    2007-12-19 14:38:13:161 1292 744 AU #############
    2007-12-19 14:38:13:161 1292 744 AU ## START ## AU: Search for updates
    2007-12-19 14:38:13:161 1292 744 AU #########
    2007-12-19 14:38:13:161 1292 744 AU <<## SUBMITTED ## AU: Search for updates
    [CallId = {74CB5837-83E7-429A-878B-49D7106B5EC2}]
    2007-12-19 14:38:13:161 1292 126c Agent *************
    2007-12-19 14:38:13:161 1292 126c Agent ** START ** Agent: Finding updates
    [CallerId = AutomaticUpdates]
    2007-12-19 14:38:13:161 1292 126c Agent *********
    2007-12-19 14:38:13:161 1292 126c Agent * Online = Yes; Ignore download
    priority = No
    2007-12-19 14:38:13:161 1292 126c Agent * Criteria = "IsHidden=0 and
    IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or
    IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and
    IsAssigned=1 or IsHidden=0 and IsInstalled=1 and
    DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or
    IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and
    IsAssigned=1 and RebootRequired=1"
    2007-12-19 14:38:13:161 1292 126c Agent * ServiceID =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
    2007-12-19 14:38:13:161 1292 126c Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2007-12-19 14:38:13:192 1292 126c Misc Microsoft signed: Yes
    2007-12-19 14:38:13:223 1292 126c Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2007-12-19 14:38:13:239 1292 126c Misc Microsoft signed: Yes
    2007-12-19 14:38:13:255 1292 126c Misc Validating signature for
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2007-12-19 14:38:13:270 1292 126c Misc Microsoft signed: Yes
    2007-12-19 14:38:13:286 1292 126c Setup *********** Setup: Checking whether
    self-update is required ***********
    2007-12-19 14:38:13:286 1292 126c Setup * Inf file:
    C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\cdm.dll: target version = 7.0.6000.381, required version
    = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuauclt.exe: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:286 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:301 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:301 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wups.dll: target version = 7.0.6000.381, required version
    = 7.0.6000.374


    And here's the screenshot of my sbs box after completing /detectnow:

    http://www.heritagehomecare.com/ss.bmp

    The pc in question already has the update installed.


    2007-12-19 14:38:13:301 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wups2.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:301 1292 126c Setup Update NOT required for
    C:\WINDOWS\system32\wuweb.dll: target version = 7.0.6000.381, required
    version = 7.0.6000.374
    2007-12-19 14:38:13:301 1292 126c Setup * IsUpdateRequired = No
    2007-12-19 14:38:18:473 1292 126c PT +++++++++++ PT: Synchronizing server
    updates +++++++++++
    2007-12-19 14:38:18:473 1292 126c PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://HERITAGE-SBS:8530/ClientWebService/client.asmx
    2007-12-19 14:38:40:238 1292 126c PT +++++++++++ PT: Synchronizing extended
    update info +++++++++++
    2007-12-19 14:38:40:238 1292 126c PT + ServiceId =
    {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
    http://HERITAGE-SBS:8530/ClientWebService/client.asmx
     
    steve841, Dec 19, 2007
    #3
  4. This is only part of the /detectnow process, please post the entire log starting
    from this line:
    You probably didn't wait long enough. The process takes several minutes.
    Ah. I hadn't noticed this was an SBS box. That particular interface doesn't
    exist in vanilla WSUS, and I've never used SBS so I probably can't be much help.
    Have you tried right-clicking the computer name in the list and seeing if
    there's an option for removing the report?

    Harry.
     
    Harry Johnston [MVP], Dec 19, 2007
    #4
  5. steve841

    steve841 Guest

    That's the real kicker here.

    Using the MMC for WSUS 3.0 ... there are no errors.

    It's only in the MMC in SBS that the install errors show.

    I saw in another forum where it was suggested to edit the updates out of the
    database... but I'm not to keen on that option.
     
    steve841, Dec 20, 2007
    #5
  6. steve841

    steve841 Guest

    Well ... a combination of errorts solved it ... What a pain!

    Maybe this can help someone else. On the CLIENT PC giving the error...

    1. create a batch file
    regsvr32 /s wuapi.dll

    regsvr32 /s wups.dll

    regsvr32 /s wuaueng.dll

    regsvr32 /s wucltui.dll

    regsvr32 /s msxml3.dll

    net start wuauserv

    wuauclt.exe /resetauthorization /detectnow

    2. Download WUA WindowsUpdateAgent20-x86.exe from
    http://go.microsoft.com/fwlink/?LinkId=43264.
    and run the following command: "WindowsUpdateAgent20-x86.exe /wuforce"

    3. Start / Run

    regsvr32 wuapi.dll
    regsvr32 wuaueng.dll
    regsvr32 wuaueng1.dll
    regsvr32 wucltui.dll
    regsvr32 wups.dll
    regsvr32 wups2.dll
    regsvr32 wuweb.dll
    regsvr32 msxml3.dll
     
    steve841, Dec 20, 2007
    #6
  7. steve841

    steve841 Guest

    And don't forget to REBOOT PC.

    Takes about 15 min to show in the WSUS MMC...
     
    steve841, Dec 20, 2007
    #7
  8. This is certainly an interesting combination of activities!



    On the CLIENT PC giving the error...
    So.. you registered five DLLs.


    Then started a service (which was probably already running since you never
    stopped it, and if it wasn't running =THAT= would be your core issue.)

    And executed a detection, abeit this time with the /resetauthorization
    option -- which, at least, ensures that the client is not using defective
    cached targeting information..

    Then reinstalled the WUA v5.8 (WSUS 2.0) client in a system in a WSUS 3.0
    environment.

    And REregistered the same five DLLs, plus a few more; all of which were
    registered, anyway, as a result of the execution of
    WindowsUpdateAgent20-x86.exe.


    So.... the net effect of all of this is simply that you reinstalled the
    WSUS2.0 WUA., which was probably pointless since you're using WSUS 3.0. The
    very first thing that's going to happen is the WUA does a selfupdate from
    the WSUS 3.0 server.

    At a minimum you should have installed WindowsUpdateAgent30-x86.exe -- which
    is the WSUS 3.0 WUA.


    --
    Lawrence Garvin, M.S., MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    MVP - Software Distribution (2005-2007)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 20, 2007
    #8
  9. steve841

    steve841 Guest

    Where were you when the original question was posed?

    Well, I guess your comments are pointless since my steps solved the issue.

    I'm sure your comments will be invaluable to someone.

    Steve
     
    steve841, Dec 21, 2007
    #9
  10. As a matter of fact I was right here, watching Harry do an *excellent* job
    of trying to help you with your issue, and noting you weren't very
    responsive to his requests.

    It was only 18 hours ago that Harry noted you had an SBS box and commented
    that he might not be able to offer much more help, but he did ask you to
    post the COMPLETE log, which, had you done so, I might have stepped in and
    offered additional help. But you didn't wait for additional help. You went
    off on your own and acquired some pseudo-solution from some other resouce.


    As for the procedure.. and helping others.... there are a LOT of
    dysfunctional and bad "this will fix your problem" procedures out there on
    the web, most of them posted just like people like you who found something
    "that worked", but don't have any idea why it worked, or what actually
    happened. I post what I do so that somebody tripping across this thread in a
    Google Groups search a month or a year from now will see that this procedure
    is NOT something that should be relied upon to repair an issue.


    The ONLY thing of significance you did in that whole procedure was run this
    one command:

    wuauclt /resetauthorization /detectnow

    Other than downgrading your WUA and causing it to have to selfupdate again.

    The LOGS (even the partial one you posted), already proved there was no need
    to reregister any DLL files!


    Frankly, the fact that you were trying to use the SBS MMC (a customized WSUS
    2.0 API product) to talk to a WSUS 3.0 server (something it's not really
    designed to do) probably has a LOT to do with the problem.


    --
    Lawrence Garvin, M.S., MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    MVP - Software Distribution (2005-2007)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
     
    Lawrence Garvin [MVP], Dec 21, 2007
    #10
  11. steve841

    John Fenton Guest

    wuauclt /resetauthorization /detectnow

    Did the trick for me.

    "Frankly, the fact that you were trying to use the SBS MMC (a customized WSUS
    2.0 API product) to talk to a WSUS 3.0 server (something it's not really
    designed to do) probably has a LOT to do with the problem."

    I'm pretty sure my WSUS 3.0 was a self update on my SBS server. I don't recall going out and finding it. I do recall it asking permission before installing.

    The install was not exactly smooth, but not to big of a problem to correct. I would have thought they would have pushed an update to the SBS MMC at the same time, and made the install more SBS friendly, but I guess no such luck.

    Other than this problem the SBS MMC does "appear" to be working, but that may be a dangerous assumption, so I will have to keep an eye on it.
     
    John Fenton, Apr 27, 2008
    #11
  12. steve841

    John Fenton Guest

    Boy the formating really messed up on that last post, and it dropped part of the quote :( Would be nice if we had edit or preview on this site. (Posted from eggheadcafe.com)
     
    John Fenton, Apr 27, 2008
    #12
  13. steve841

    John Fenton Guest

    I posted this from
    http://www.eggheadcafe.com/software/aspnet/31349017/sbs2003r2--wsus30--cli.aspx

    In response to this:

    As a matter of fact I was right here, watching Harry do an *excellent* job
    of trying to help you with your issue, and noting you weren't very
    responsive to his requests.

    It was only 18 hours ago that Harry noted you had an SBS box and commented
    that he might not be able to offer much more help, but he did ask you to
    post the COMPLETE log, which, had you done so, I might have stepped in and
    offered additional help. But you didn't wait for additional help. You went
    off on your own and acquired some pseudo-solution from some other resouce.

    As for the procedure.. and helping others.... there are a LOT of
    dysfunctional and bad "this will fix your problem" procedures out there on
    the web, most of them posted just like people like you who found something
    happened. I post what I do so that somebody tripping across this thread in a
    Google Groups search a month or a year from now will see that this procedure
    is NOT something that should be relied upon to repair an issue.

    The ONLY thing of significance you did in that whole procedure was run this
    one command:

    wuauclt /resetauthorization /detectnow

    Other than downgrading your WUA and causing it to have to selfupdate again.

    The LOGS (even the partial one you posted), already proved there was no need
    to reregister any DLL files!

    Frankly, the fact that you were trying to use the SBS MMC (a customized WSUS
    2.0 API product) to talk to a WSUS 3.0 server (something it's not really
    designed to do) probably has a LOT to do with the problem.

    --
    Lawrence Garvin, M.S., MCTS, MCP
    Senior Data Architect, APQC, Houston, Texas
    MVP - Software Distribution (2005-2007)

    MS WSUS Website: http://www.microsoft.com/wsus
    My Websites: http://www.onsitechsolutions.com;
    http://wsusinfo.onsitechsolutions.com
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

    **************************************************

    Should have just come here directly :(
     
    John Fenton, Apr 27, 2008
    #13
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.