locked
wsus client diagnostic tool displays this error RRS feed

  • 問題

  • Hi


    When I am running WSUS client diagnostic tool in one client vm host running under windows 2008 server standard R2, I am getting the following error.



    When pinging the WSUS Server from this vm host , it pings successfully and telnetting to the wsus too works.

    Any help regarding this issue is appreciated!


    Thanks & Regards S.Swaminathan Live & let others live!!!

    2013年8月14日 下午 07:08

解答

  • Hi Pete,

    WSUS version - 3.2.7600.226 on Server 2008 R2 SP1

    General - Windows Update failed to check for updates with error 0x800b0001

    Applying patch kb2720211 and kb2734608 on your server will help you not getting the error 0x800B0001

    TiGrOu.

    2013年8月15日 上午 10:02
  • I've run the WSUS Client Diagnostics Tool on one of the servers and have got this responce:

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    Client Diagnostic Tool is 32-bit only; see above post for link to SolarWinds tool which will run on 64-bit systems.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013年8月14日 下午 09:34

所有回覆

  • On our site we use a WSUS server but when I manually try to up date any other server on the site I get the following message:

    "Windows could not search for new updates

    An error occurred while checking for new updates for you computer

    Error(s) found:

    Code 80244023 Windows Update encountered an unknown error. Get help with the error."

    I tried clicking on the link but this code don't appear in the list.

    I've tried running the FitIt tool for Windows Update and this does report that it's repared an issue with the Windows Update omponents but I'm still getting the same issue and code.

    Searches on google have suggested DNS issues but I can ping the WSUS server from any of the server and the a get a responce and the name is resolved.

    I've run the WSUS Client Diagnostics Tool on one of the servers and have got this responce:

    "WSUS Client Diagnostics Tool

    Checking Machine State

    Checking for admin rights to run tool.........PASS

    Automatic Updates Service is running........PASS

    Background Intelligent Transfer Server is running........PASS

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    The system cannot find the file specified."

    Which I can assume isn't good!

    All servers are running on Server 2008 R2 and we use Client Side Targeting for all the servers.

    Currently it is the summer holidays so the perfect time to update all the servers in the school but I can't seem to get them to talk to WSUS to pick up the approved updates despite them showing in the correct computer list. Some have reported back in the last couple of days but other no essential servers haven't for over a year (since the last time I ran the updates).

    Could someone please respond to this and give me some helpful pointers. In the mean time I will just update manually over the net - somewhat defeating the object of having a WSUS server but time is against me.  

    2013年8月14日 下午 02:19
  • Can you please let us know what version of WSUS you have installed, and what service packs and KBs you have installed?
    2013年8月14日 下午 07:13
  • Hi Pete,

    From Lawrence Garvin, the Client Diagnostics Tool is a 32bits based software.

    The error code "GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002" you received is specific from running a 32bits software on a 64bits server.

    Can you give us more details for your 80244023 error code with your WindowsUpdate.log file updated after running a wuauclt /detectnow.

    TiGrOu.

    • 已提議為解答 Brice Pradel 2013年8月15日 上午 07:31
    2013年8月14日 下午 07:28
  • Hi

    The service pack is SP1 and the wsus version is below


    Thanks & Regards S.Swaminathan Live & let others live!!!

    2013年8月14日 下午 08:29
  • Hi all

    Thanks for all , finally got resolved the update issue when Ben Herila asked me the wsus agent version, service pack details.From this question , it made me to re register the wuaueng.dll  and when I tried to update I successfully got these updates as below

    Shall I go for the updates since it is a production server? and also found the update settings as below


    Thanks & Regards S.Swaminathan Live & let others live!!!

    2013年8月14日 下午 09:26
  • When I am running WSUS client diagnostic tool in one client vm host running under windows 2008 server standard R2, I am getting the following error.

    The Microsoft WSUS Client Diagnostic Tool does not run on x64 systems. It is 32-bit only. For a functional diagnostic tool, try the SolarWinds Diagnostic Tool for the WSUS Agent, which does run on both x86 and x64 systems.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013年8月14日 下午 09:32
  • I've run the WSUS Client Diagnostics Tool on one of the servers and have got this responce:

    GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002

    Client Diagnostic Tool is 32-bit only; see above post for link to SolarWinds tool which will run on 64-bit systems.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013年8月14日 下午 09:34
  • Code 80244023 Windows Update encountered an unknown error. Get help with the error."

    0x80244023 is an HTTP 504 error. (Timed Out Waiting For Gateway)

    Never seen this in from a WUAgent before, but based on the resolution below, I'll file it under "DLLs possibly not registered correctly".


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.


    2013年8月14日 下午 09:35
  • Hi Lawrence

    Thanks for the update ; and shall I go for the updates now?

    Hi Lawrence

    My error is hr:0x80070002 but Pete's post immediately came beneath my post.

    This is the error you can update in your database for the re registering of the wuaeng.dll

    Shall I install the updates now ?If the server goes for reboot cannot be done now


    Thanks & Regards S.Swaminathan Live & let others live!!!


    • 已編輯 TECHSHAN 2013年8月14日 下午 09:56
    2013年8月14日 下午 09:48

  • Shall I install the updates now ?If the server goes for reboot cannot be done now

    You can install them and postpone the restart.

    Restart is not necessary required, and in case it is, it's to finalize the install, but it's not a forced one as you're doing it manually.

    TiGrOu.

    2013年8月15日 上午 07:34
  • Good day all. Apologies for highjacking your thread Techshan. I fairly sure I started my own but there you go.

    Details as requested:

    WSUS version - 3.2.7600.226 on Server 2008 R2 SP1

    Window Update Agent - same as in Techshan's post, also 2008 R2 SP1 server

    WindowsUpdate log shows the following after 1st trying to check for updates:

    General - Windows Update failed to check for updates with error 0x80244023.

    Details -

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    - <System>

    <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945A8954-C147-4ACD-923F-40C45405A658}" />

    <EventID>25</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>1</Task>

    <Opcode>11</Opcode>

    <Keywords>0x4000000000000022</Keywords>

    <TimeCreated SystemTime="2013-08-15T09:12:23.860572800Z" />

    <EventRecordID>9068</EventRecordID>

    <Correlation ActivityID="{018C4A40-F800-0000-8745-9277D932CE01}" />

    <Execution ProcessID="824" ThreadID="836" />

    <Channel>Microsoft-Windows-WindowsUpdateClient/Operational</Channel>

    <Computer>Severname.etc</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    - <UserData>

    <errorCode xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">0x80244023</errorCode>

    </UserData>

    </Event>

    I then get 3 entries with the following details:

    General - There has been a change in the health of Windows Update

    Details -

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    - <System>

    <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945A8954-C147-4ACD-923F-40C45405A658}" />

    <EventID>42</EventID>

    <Version>0</Version>

    <Level>4</Level>

    <Task>2</Task>

    <Opcode>18</Opcode>

    <Keywords>0x4000000000000480</Keywords>

    <TimeCreated SystemTime="2013-08-15T09:12:23.860572800Z" />

    <EventRecordID>9071</EventRecordID>

    <Correlation ActivityID="{018C4A40-F800-0000-8745-9277D932CE01}" />

    <Execution ProcessID="824" ThreadID="836" />

    <Channel>Microsoft-Windows-WindowsUpdateClient/Operational</Channel>

    <Computer>servername.etc</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    - <EventData>

    <Data Name="hc_stateid">1</Data>

    <Data Name="restartDate" />

    <Data Name="restartTime" />

    </EventData>

    </Event>

    After running wuauclt /detectnow the log shows...

     General - Windows Update failed to check for updates with error 0x800b0001

    Thanks in Advance, Pete

    Details -

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

    - <System>

    <Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945A8954-C147-4ACD-923F-40C45405A658}" />

    <EventID>25</EventID>

    <Version>0</Version>

    <Level>2</Level>

    <Task>1</Task>

    <Opcode>11</Opcode>

    <Keywords>0x4000000000000022</Keywords>

    <TimeCreated SystemTime="2013-08-15T09:25:15.640277300Z" />

    <EventRecordID>9072</EventRecordID>

    <Correlation ActivityID="{018C4A40-F800-0000-8745-9277D932CE01}" />

    <Execution ProcessID="824" ThreadID="836" />

    <Channel>Microsoft-Windows-WindowsUpdateClient/Operational</Channel>

    <Computer>servername.etc</Computer>

    <Security UserID="S-1-5-18" />

    </System>

    - <UserData>

    <errorCode xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2004/08/windows/eventlog">0x800b0001</errorCode>

    </UserData>

    </Event>

    2013年8月15日 上午 09:44
  • Hi Pete,

    WSUS version - 3.2.7600.226 on Server 2008 R2 SP1

    General - Windows Update failed to check for updates with error 0x800b0001

    Applying patch kb2720211 and kb2734608 on your server will help you not getting the error 0x800B0001

    TiGrOu.

    2013年8月15日 上午 10:02
  • Thanks for the quick responce TiGrOu

    I assume I apply these to the WSUS server or all the servers that are failing to connect? or both?

    2013年8月15日 上午 10:34
  • You need to apply this to the WSUS server only.

    This is to make WUAgent communicates again with your WSUS server updating the version from 3.2.7600.226 to 3.2.7600.251 (kb2720211) then to 3.2.7600.256 (kb2734608)

    TiGrOu.

    • 已提議為解答 Brice Pradel 2013年8月15日 下午 12:25
    2013年8月15日 上午 10:54
  • Top Man TiGrOu!

    After installing those two patches and running wuauclt /detectnow on the another server it started picking up all the updates and reporting back to the WSUS server.

    Just got to go through and run the command on all the others and i'm done.

    Saved me a lot of time and effort, thank you.

    Regards

    Peter

    2013年8月15日 下午 12:13
  • Maybe using a batch file to deploy it on others will be easier than to do it on each of them. ;)

    TiGrOu.

    2013年8月15日 下午 12:25
  • Hi

    Everything is fine


    Thanks & Regards S.Swaminathan Live & let others live!!!

    2013年8月15日 下午 01:53
  • You need to apply this to the WSUS server only.

    Also any machines where you have installed a remote WSUS console.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013年8月15日 下午 05:42
  • WSUS version - 3.2.7600.226 on Server 2008 R2 SP1

    General - Windows Update failed to check for updates with error 0x800b0001

    Applying patch kb2720211 and kb2734608 on your server will help you not getting the error 0x800B0001

    To clarify.. you only need to install *ONE* of these updates. KB2734608 is cumulative; it includes KB2720211.

    KB2734608 provides the capability to patch Windows 8/Windows Server 2012 systems. It also has special installation requirements. If you don't have Win8/WS2012 systems, you might choose to forego the installation of this patch.

    KB2720211 is the minimum patch required. It provides an updated Windows Update Agent, and the updated certificates that are necessary for the (already updated) WUAgent on your clients to communicate with WSUS successfully. However, this update has been problematic in certain installation scenarios (which is the other advantage to KB2734608).

    Please READ the KB articles for both of these updates thoroughly before clicking on the installer.

    Do NOT deploy KB2720211 from the WSUS repository. Install it interactively ONLY.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    2013年8月15日 下午 05:46
  • Hello,

    I've got the same problem on Windows 2008 R2 SP1.

    Re register the wuaueng.dll solve it.

    regsvr32 wuaueng.dll

    Thx.


    2015年8月13日 上午 10:01
  • Can you please let me know how to do it? my wsus agent is old, thanks.
    2017年9月15日 上午 08:40
  • Hi, can you please let me know how to do it? my wsus agent is old, thanks.
    2017年9月15日 上午 08:40