none
WSUS Client Issues

    General discussion

  • Dear Experts,

    Whilst I was on leave one of my colleagues had an issue with one of our VM Servers which crashed.

    He installed everything but didnt have time to configure everything.

    I tried to get WSUS working but it just crashed everytime I tried to start the snap in.

    So I decided it best to build the server from scratch again. installed WSUS 3.0 SP2 sync'ed all required updates to the server.

    However none of my clients seem to be able to connect to WSUS.

    I Changed the name of the server but I also updated the GPO for this.

    When I run the clientdiag.exe everything seems to be reported correctly. Everything passes has the right name for wsus but is only http not https...

    On the client it says Wuaueng.dll version is 7.6.7600.256 and that its version 2

    As my server is version 3.0 do I need to update the client? I cant find a newer version of Wuaueng.dll to do this.

    There is no firewall in the way to stop the clients connecting to the server and they are on the same subnet.

    The server is configured as WSUS server and is fully uptodate. 

    I just get messages on clients saying 'Windows Cant Check For Updates'

    Any ideas what to look for please people?

    Thanks

    Shaun

    Saturday, July 06, 2013 6:34 AM

All replies

  • Hi,

    on an affected client machine, examine the windowsupdate.log file for the connection attempt and errors occurring.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Saturday, July 06, 2013 9:54 AM
  • I Changed the name of the server but I also updated the GPO for this.

    Did you also update the DNS?
    I just get messages on clients saying 'Windows Cant Check For Updates'
    It would really help to see the actual messages from the WindowsUpdate.log

    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.


    Monday, July 08, 2013 1:47 AM
    Moderator
  • Hi Guys,

    Thanks for your replies, sorry for my late reply been a away for a few days.

    DNS was updated. I can ping the servers name and get a reply.

    I can web browse the wsus server (http://0513-wsus-kav) and I get the IIS page.

    Server is 2008 SP1

    WSUS SP1 was installed then KB940518 so its managed in server manager.

    Clientdiag is:

    WSUS Client Diagnostics Tool

    Checking Machine State
            Checking for admin rights to run tool . . . . . . . . . PASS
            Automatic Updates Service is running. . . . . . . . . . PASS
            Background Intelligent Transfer Service is running. . . PASS
            Wuaueng.dll version 7.6.7600.256. . . . . . . . . . . . PASS
                    This version is WSUS 2.0

    Checking AU Settings
            AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
                    Option is from Policy settings

    Checking Proxy Configuration
            Checking for winhttp local machine Proxy settings . . . PASS
                    Winhttp local machine access type
                            <Direct Connection>
                    Winhttp local machine Proxy. . . . . . . . . .  NONE
                    Winhttp local machine ProxyBypass. . . . . . .  NONE
            Checking User IE Proxy settings . . . . . . . . . . . . PASS
                    User IE Proxy. . . . . . . . . . . . . . . . .  NONE
                    User IE ProxyByPass. . . . . . . . . . . . . .  NONE
                    User IE AutoConfig URL Proxy . . . . . . . . .  NONE
                    User IE AutoDetect
                    AutoDetect in use

    Checking Connection to WSUS/SUS Server
                    WUServer = http://0513-wsus-kav
                    WUStatusServer = http://0513-wsus-kav
            UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
            Connection to server. . . . . . . . . . . . . . . . . . PASS
            SelfUpdate folder is present. . . . . . . . . . . . . . PASS

    Press Enter to Complete

    Serevrdiagnostics tool:

    Running... GetConfiguration
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup
            :
            Version:3
            VersionString:3.1.6001.65
            ConfigurationSource:0
            ServicePackLevel:1
            TargetDir:C:\Program Files\Update Services\
            InstallType:1
            EnableRemoting:1
            WsusAdministratorsSid:S-1-5-21-4044294608-2644188196-1317443539-1003
            WSUSReportersSid:S-1-5-21-4044294608-2644188196-1317443539-1002
            SqlServerName:0513-WSUS-KAV\MICROSOFT##SSEE
            SqlAuthenticationMode:WindowsAuthentication
            SqlDatabaseName:SUSDB
            SqlUserName:
            SqlEncryptedPassword:
            SqlInstanceIsRemote:0
            wYukonInstalled:1
            IISInstallRevision:3.1.6001.65
            IISPreviousInstallRevision:
            IISUninstallConfigFilePath:C:\Program Files\Update Services\setup\Uninst
    allSettings.xml
            IISTargetWebSiteCreated:False
            IISTargetWebSiteIndex:1
            ContentDir:D:\WSUS
            SmtpUserPassword:
            ProxyPassword:
            PortNumber:80
            IIsDynamicCompression:0
            EncryptionParam:System.Byte[]
            EncryptionKey:System.Byte[]
    Error processing node: GetConfiguration
    System.Data.SqlClient.SqlException: An error has occurred while establishing a c
    onnection to the server.  When connecting to SQL Server 2005, this failure may b
    e caused by the fact that under the default settings SQL Server does not allow r
    emote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating
     Server/Instance Specified)
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception
    , Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObj
    ect stateObj)
       at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternal
    ConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Bool
    ean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection
    owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo
    serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire,
     SqlConnection owningObject)
       at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host
    , String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject
    , SqlConnectionString connectionOptions, Int64 timerStart)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnecti
    on owningObject, SqlConnectionString connectionOptions, String newPassword, Bool
    ean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdent
    ity identity, SqlConnectionString connectionOptions, Object providerInfo, String
     newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOp
    tions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection
     owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConn
    ection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owning
    Object)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection o
    wningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection ownin
    gObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection ow
    ningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection ou
    terConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SoftwareDistribution.Tools.SqlHandler.HandleQuery(TextWriter dat
    aWriter, String baseDirectory, ArrayList sqlQueryList)
       at Microsoft.SoftwareDistribution.Tools.InstallConfiguration.DumpData(String
    baseDirectory, String nodeName, XmlNode infoXml)
       at Microsoft.SoftwareDistribution.Tools.SusServerTool.ProcessDumpNode(XmlNode
     dumpNode)

    Latest from windowsupdate.log is:

    2013-07-13    09:48:43:030    1368    1f30    AU    ##  END  ##  AU: Search for updates [CallId = {8C2508A5-857F-4C4F-9AF3-F786310AB451}]
    2013-07-13    09:48:43:030    1368    1f30    AU    #############
    2013-07-13    09:48:43:030    1368    1f30    AU    Need to show Unable to Detect notification
    2013-07-13    09:48:43:030    1368    1f30    AU    AU setting next detection timeout to 2013-07-13 05:38:38
    2013-07-13    09:48:43:030    1368    1f30    AU    Setting AU scheduled install time to 2013-07-13 07:00:00
    2013-07-13    09:48:43:677    1368    1b90    PT    WARNING: Cached cookie has expired or new PID is available
    2013-07-13    09:48:43:677    1368    1b90    PT    Initializing simple targeting cookie, clientId = 17da47bc-f986-4f86-8140-8c4dd9fc449c, target group = , DNS name = eto.my-ecstasea.local
    2013-07-13    09:48:43:677    1368    1b90    PT      Server URL = http://0513-wsus-kav/SimpleAuthWebService/SimpleAuth.asmx
    2013-07-13    09:48:52:710    1368    1b90    Misc    WARNING: Send failed with hr = 80072efd.
    2013-07-13    09:48:52:710    1368    1b90    Misc    WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2013-07-13    09:48:52:710    1368    1b90    PT      + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2013-07-13    09:48:52:710    1368    1b90    PT      + Caller provided credentials = No
    2013-07-13    09:48:52:710    1368    1b90    PT      + Impersonate flags = 0
    2013-07-13    09:48:52:710    1368    1b90    PT      + Possible authorization schemes used =
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: GetAuthorizationCookie failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80072efd
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: PopulateAuthCookies failed: 0x80072efd
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: RefreshCookie failed: 0x80072efd
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: RefreshPTState failed: 0x80072efd
    2013-07-13    09:48:52:710    1368    1b90    PT    WARNING: PTError: 0x80072efd
    2013-07-13    09:48:52:710    1368    1b90    Report    WARNING: Reporter failed to upload events with hr = 80072efd.
    2013-07-13    09:48:52:710    1368    1b90    Report    REPORT EVENT: {F895306F-63FE-45B8-A05F-1DE3A1E94C65}    2013-07-13 09:48:41:641+0500    1    148    101    {D67661EB-2423-451D-BF5D-13199E37DF28}    1    80072efd    SelfUpdate    Failure    Software Synchronization    Windows Update Client failed to detect with error 0x80072efd.
    2013-07-13    09:48:52:772    1368    1b90    Report    CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2013-07-13    09:48:52:772    1368    1b90    Report    WER Report sent: 7.6.7600.256 0x80072efd D67661EB-2423-451D-BF5D-13199E37DF28 Scan 101 Managed
    2013-07-13    09:48:52:772    1368    1b90    Report    CWERReporter finishing event handling. (00000000)
    2013-07-13    09:48:52:881    1368    1b90    PT    WARNING: Cached cookie has expired or new PID is available
    2013-07-13    09:48:52:881    1368    1b90    PT    Initializing simple targeting cookie, clientId = 17da47bc-f986-4f86-8140-8c4dd9fc449c, target group = , DNS name = eto.my-ecstasea.local
    2013-07-13    09:48:52:881    1368    1b90    PT      Server URL = http://0513-wsus-kav/SimpleAuthWebService/SimpleAuth.asmx
    2013-07-13    09:48:53:883    1368    1b90    Misc    WARNING: Send failed with hr = 80072efd.
    2013-07-13    09:48:53:884    1368    1b90    Misc    WARNING: SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2013-07-13    09:48:53:884    1368    1b90    PT      + Last proxy send request failed with hr = 0x80072EFD, HTTP status code = 0
    2013-07-13    09:48:53:884    1368    1b90    PT      + Caller provided credentials = No
    2013-07-13    09:48:53:884    1368    1b90    PT      + Impersonate flags = 0
    2013-07-13    09:48:53:884    1368    1b90    PT      + Possible authorization schemes used =
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: GetAuthorizationCookie failure, error = 0x80072EFD, soap client error = 5, soap error code = 0, HTTP status code = 200
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: Failed to initialize Simple Targeting Cookie: 0x80072efd
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: PopulateAuthCookies failed: 0x80072efd
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: RefreshCookie failed: 0x80072efd
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: RefreshPTState failed: 0x80072efd
    2013-07-13    09:48:53:884    1368    1b90    PT    WARNING: PTError: 0x80072efd
    2013-07-13    09:48:53:884    1368    1b90    Report    WARNING: Reporter failed to upload events with hr = 80072efd.

    Thanks for any help you can offer.

    Saturday, July 13, 2013 5:10 AM
  • I googled some of the error messages in the windowsupdate.log file.

    And found a few things on TN that indicated a version mismatch between client and server.

    I have now installed WSUS 3.0 SP2.

    I now have in Server Manager WSUS under Roles and in Admin Tools I have a WSUS.

    I assume I should be using the one in Admin tools? or is it the same in Server manager?

    Sunday, July 14, 2013 9:09 AM
  • You should also apply http://support.microsoft.com/kb/2828185

    (this is the latest WSUS update, it supersedes 2734608 and earlier)

    you will need it, to ensure your server is offering the correct client version communication - your example above shows the client is using v7.6.7600.256

    Both of the WSUS consoles should launch the correct (same) WSUS management tools.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Sunday, July 14, 2013 9:28 AM
  • upgrading to WSUS 3.0 SP2 has not fixed the issue.

    However I have found the following:

    KB272011

    and will look at installing that once the server has finished installing some updates

    looking at the logs my Client version is 7.6.7600.256 and server version is 3.2.7600.226

    I need server version to be at 3.2.7600.251 for them to properly communicate which is why I think I may need the KB272011

    Thanks

    • Edited by Shaunie1975 Sunday, July 14, 2013 11:28 AM Edit
    Sunday, July 14, 2013 11:23 AM
  • looking at the logs my Client version is 7.6.7600.256 and server version is 3.2.7600.226

    I need server version to be at 3.2.7600.251 for them to properly communicate which is why I think I may need the KB272011

    Strictly speaking, the WSUS server needs to be at Build 251, or later.

    KB272011 will bring the server to Build 251. A later update, KB2734608, which should be installed instead of KB2720211 if you have/will have Win8/WS2012 systems will bring the server to Build 256.

    Whether you need to install KB2828185 is a matter of some opinion. The WSUS Product Team would like all WSUS servers to be updated with KB2828185 because it will make their development efforts easier. (It's also possible that subsequent WSUS updates may not be actually tested/supported on Build 251 or Build 256.)

    However, as a matter of pure operational considerations:

    • Build 251 is the absolute minimum requirment. Install KB2720211.
    • Build 256 is required to support Win8/WS2012 systems. Install KB2734608

    KB2828185 is required to support alternate data export/compression functionality for organizations that have disconnected servers and are encountering issues with the size limitations of the CAB file format.

    In any event, read the KB articles thoroughly before launching the installers. These are not point-and-click updates!

    2013-07-13    09:48:43:677    1368    1b90    PT      Server URL = http://0513-wsus-kav/SimpleAuthWebService/SimpleAuth.asmx
    2013-07-13    09:48:52:710    1368    1b90    Misc    WARNING: Send failed with hr = 80072efd.


    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.

    Sunday, July 14, 2013 5:07 PM
    Moderator
  • Hi Lawrence & Don,

    Thank you both for replying.

    I have now installed KB2720211 and restarted the server.

    However the WSUS version does not seemed to have changed it still reports as 3.2.7600.226

    Then I installed KB2828185 restarted the server and wsus still reports as version .226

    Installed server 2008 SP2 which restarted the server wsus still says its versin .226

    I have also noticed in the server side config the following line:

    IISInstallRevision:3.2.7600.226 which is the same as my wsus version.

    Do i need to update IIS or should this have been done with one of the Kb or SP2? 

    Kind Regards

    Shaun



    • Edited by Shaunie1975 Monday, July 15, 2013 7:03 AM ....
    Monday, July 15, 2013 3:00 AM
  • However the WSUS version does not seemed to have changed it still reports as 3.2.7600.226

    Then I installed KB2828185 restarted the server and wsus still reports as version .226

    This is a function of usign the About->Help screen of the MMC, rather than inspecting the actual product version as displayed in the console itself.

    Please navigate to the root page of the WSUS Console, and in the lower right corner of that details page you'll see the current build of the installed version of WSUS.


    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.

    Monday, July 15, 2013 4:05 PM
    Moderator
  • Hi Lawrence,

    You were spot on with that the actual version according to the snapin is:3.2.7600.262

    It seems the Win7 clients and Win XP clients on the network are updating.

    This problem seems isolated to my win vista machine. Unfortunatley I am the only one with Vista so can not check anyone else's :(

    Maybe I can use this as a push for an upgrade ;)

    In the meantime could you suggest anything I can do in order to get my machine updating again?

    Thank You

    Shaun

    Tuesday, July 16, 2013 3:21 AM
  • This problem seems isolated to my win vista machine. Unfortunatley I am the only one with Vista so can not check anyone else's :(

    In the meantime could you suggest anything I can do in order to get my machine updating again?

    what does your windowsupdate.log reveal?

    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Tuesday, July 16, 2013 4:01 AM
  • Hi Lawrence,

    You were spot on with that the actual version according to the snapin is:3.2.7600.262

    It seems the Win7 clients and Win XP clients on the network are updating.

    This problem seems isolated to my win vista machine. Unfortunatley I am the only one with Vista so can not check anyone else's :(

    Maybe I can use this as a push for an upgrade ;)

    In the meantime could you suggest anything I can do in order to get my machine updating again?

    Thank You

    Shaun

    Something that happens in our environment is that some Windows 7 and Windows Vista workstations fail to get updates. Turning off Windows updates and then turn it back on. This did seem to help the clients start to get updates again.
    Tuesday, July 16, 2013 2:12 PM
  • This problem seems isolated to my win vista machine. Unfortunatley I am the only one with Vista so can not check anyone else's :(

    Does your Vista system have Service Pack 2 installed?

    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.

    Tuesday, July 16, 2013 9:36 PM
    Moderator
  • Hi and thanks to all that are helping.

    My laptop does have Vista SP2 installed lawrence.

    I have managed to resolve the issue on my laptop. I work on a ship and the person who is in charge of the IT whilst I am on leave had moved the laptop to a different OU container. Once i put it back and restarted the machine it got all its updates.

    I have found another rather old laptop stored away in a cupboard that is running win vista and it has the similar issues to what my laptop had.

    I havent spent much time on this as its an old machine and really just a spares.

    Once I have a bit of spare time I will look more closely at this machine but for now I must get KAV up and running again :(

    Thanks for all advise

    Saturday, July 20, 2013 6:51 AM