Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Windows Server TechCenter >
> 
> 
WSUS 3.0 SP2 - new install of a replica server, no clients checking in ...

Answered WSUS 3.0 SP2 - new install of a replica server, no clients checking in ...

  • Friday, November 16, 2012 4:08 PM
     
     
    Sign In to Vote
    0

    I've installed WSUS 3.0 SP2 on a new server running W2K8 R2 SP1.  It installed without issues, i've connected this server as a replica server and it does receive the settings from the primary server without any issues.  I've named this server the same as the previous server that it replaced, I also gave it the same IP address.  We leverage GPO for all clients to communicate with the corresponding WSUS servers for the facility that they work in.

    The problem I have is only a handful of clients have contacted the new server and no clients/servers have reported in. (they show 'Not yet reported').

    I cannot figure out what is going on.  I don't see any error logs in the servers log files.  I don't see any AD errors and am just lost as to what is going on.

    Any suggestions would be great.


    Mike

     

All Replies

  • Monday, November 19, 2012 2:11 AM
    Moderator
     
     
    Sign In to Vote
    0
    Hi,

    Is your previous server taken offline?Run wuauclt /detect,and then post any errors on the windowsupdate.log on the client side to see whether there are any clues.My guess would be the port has been changed to 8530.You may need to confirm the setting under the policy "Specify intranet microsoft update service location"on the GPO.


    Regards,

    Clarence

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

     

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Monday, November 19, 2012 3:34 PM
     
     
    Sign In to Vote
    0

    Morning Clarence,

    I had checked the setup of this server with another replica server that is working and all the settings are the same.  Something else i'm noticing is, when I click on the server with issues in the MMC and look at the overview, the number listed in Unapproved updates is not changing/syncing with the changes made on the upstream server even though when I force a sync it does state 'succeeded'.

    Also, the old server is shutoff.

    Mike

     
  • Monday, November 19, 2012 3:44 PM
     
     
    Sign In to Vote
    0

    Sorry, forgot to include this info from the log file:

    2012-11-19 09:42:39:791 992 1070 PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2012-11-19 09:42:39:791 992 1070 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ecmgmtsvr01/ClientWebService/client.asmx
    2012-11-19 09:42:40:461 992 1070 PT WARNING: GetExtendedUpdateInfo failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2012-11-19 09:42:40:461 992 1070 PT WARNING: PTError: 0x80244019
    2012-11-19 09:42:40:461 992 1070 PT WARNING: GetExtendedUpdateInfo_WithRecovery: 0x80244019
    2012-11-19 09:42:40:461 992 1070 PT WARNING: Sync of Extended Info: 0x80244019
    2012-11-19 09:42:40:461 992 1070 PT WARNING: SyncServerUpdatesInternal failed : 0x80244019
    2012-11-19 09:42:40:461 992 2e0 AU Triggering Offline detection (non-interactive)
    2012-11-19 09:42:40:461 992 2e0 AU #############
    2012-11-19 09:42:40:461 992 2e0 AU ## START ##  AU: Search for updates
    2012-11-19 09:42:40:461 992 2e0 AU #########
    2012-11-19 09:42:40:461 992 2e0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {4E28192C-70D3-423D-A75E-8137E30B3F55}]
    2012-11-19 09:42:40:555 992 1070 Agent  * WARNING: Exit code = 0x80244019
    2012-11-19 09:42:40:555 992 1070 Agent *********
    2012-11-19 09:42:40:555 992 1070 Agent **  END  **  Agent: Finding updates [CallerId = ]
    2012-11-19 09:42:40:555 992 1070 Agent *************
    2012-11-19 09:42:40:555 992 1070 Agent WARNING: WU client failed Searching for update with error 0x80244019
    2012-11-19 09:42:40:570 992 1070 Agent *************
    2012-11-19 09:42:40:570 992 1070 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-11-19 09:42:40:570 992 1070 Agent *********
    2012-11-19 09:42:40:570 992 1070 Agent  * Online = No; Ignore download priority = No
    2012-11-19 09:42:40:570 992 1070 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
    2012-11-19 09:42:40:570 992 1070 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2012-11-19 09:42:40:570 992 1070 Agent  * Search Scope = {Machine}
    2012-11-19 09:42:40:570 4864 105c COMAPI >>--  RESUMED  -- COMAPI: Search [ClientId = <NULL>]
    2012-11-19 09:42:40:570 4864 105c COMAPI  - Updates found = 0
    2012-11-19 09:42:40:570 4864 105c COMAPI  - WARNING: Exit code = 0x00000000, Result code = 0x80244019
    2012-11-19 09:42:40:570 4864 105c COMAPI ---------
    2012-11-19 09:42:40:570 4864 105c COMAPI --  END  --  COMAPI: Search [ClientId = <NULL>]
    2012-11-19 09:42:40:570 4864 105c COMAPI -------------
    2012-11-19 09:42:40:570 4864 1504 COMAPI WARNING: Operation failed due to earlier error, hr=80244019
    2012-11-19 09:42:40:570 4864 1504 COMAPI FATAL: Unable to perform synchronous search. (hr=80244019)
    2012-11-19 09:42:54:637 992 1070 Agent  * Added update {201AEAA7-B824-42B0-A409-20F95DECC457}.200 to search result
    2012-11-19 09:42:54:637 992 1070 Agent  * Added update {846004F8-BBC0-4088-8523-98349E7DFF6E}.201 to search result
    2012-11-19 09:42:54:637 992 1070 Agent  * Found 2 updates and 64 categories in search; evaluated appl. rules of 556 out of 1005 deployed entities
    2012-11-19 09:42:54:699 992 1070 Agent *********
    2012-11-19 09:42:54:699 992 1070 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2012-11-19 09:42:54:699 992 1070 Agent *************
    2012-11-19 09:42:54:715 992 1070 Report REPORT EVENT: {57CCA4B4-45B2-419D-808B-997580B5B80F} 2012-11-19 09:42:40:555-0600 1 148 101 {00000000-0000-0000-0000-000000000000} 0 80244019 Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
    2012-11-19 09:42:54:715 992 524 AU >>##  RESUMED  ## AU: Search for updates [CallId = {4E28192C-70D3-423D-A75E-8137E30B3F55}]
    2012-11-19 09:42:54:715 992 524 AU  # 2 updates detected
    2012-11-19 09:42:54:715 992 524 AU #########
    2012-11-19 09:42:54:715 992 524 AU ##  END  ##  AU: Search for updates [CallId = {4E28192C-70D3-423D-A75E-8137E30B3F55}]
    2012-11-19 09:42:54:715 992 524 AU #############
    2012-11-19 09:42:54:715 992 524 AU Featured notifications is disabled.
    2012-11-19 09:42:54:715 992 1070 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2012-11-19 09:42:54:715 992 1070 Report WER Report sent: 7.6.7600.256 0x80244019 00000000-0000-0000-0000-000000000000 Scan 101 Managed
    2012-11-19 09:42:54:715 992 1070 Report CWERReporter finishing event handling. (00000000)
    2012-11-19 09:43:21:897 992 1070 Report Uploading 2 events using cached cookie, reporting URL = http://ecmgmtsvr01/ReportingWebService/ReportingWebService.asmx
    2012-11-19 09:43:21:897 992 1070 Report WARNING: Failed to upload events to the server with hr = 80004005.
    2012-11-19 09:43:21:897 992 1070 PT WARNING: ReportEventBatch failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
    2012-11-19 09:43:21:897 992 1070 Report WARNING: Reporter failed to upload events with hr = 80244019.

     
  • Monday, November 19, 2012 5:18 PM
    Moderator
     
     
    Sign In to Vote
    0

    2012-11-19 09:42:39:791992 1070PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://ecmgmtsvr01/ClientWebService/client.asmx
    2012-11-19 09:42:40:461992 1070PT WARNING: GetExtendedUpdateInfo failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404

    There is a web server on this machine (as evidenced by the return of the HTTP error code), but the WSUS server is not installed on port 80.

    My guess would be that your new server was installed to the alternate v-root on port 8530, and the GPOs assigned to those clients need to be updated with the correct URL for the new WSUS server.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

     
  • Monday, November 19, 2012 5:27 PM
     
     
    Sign In to Vote
    0

    Lawrence,

    I setup the WSUS server and IIS myself, there is nothing else on the server outside of these 2 apps.  When I had setup WSUS, I made sure that it only used port 80.  In looking in IIS, I do not see anything that is pointing to port 8530.  Also, in WSUS, I had copied the same config as our other replica server to our primary server.

    In looking at the site bindings in IIS, the only thing listed for Http is port 80.

    If there's somewhere else I need to check, please let me know and I will.

    Mike

     
  • Monday, November 19, 2012 5:39 PM
     
     
    Sign In to Vote
    0
     
  • Monday, November 19, 2012 6:06 PM
    Moderator
     
     
    Sign In to Vote
    0

    I setup the WSUS server and IIS myself, there is nothing else on the server outside of these 2 apps.  When I had setup WSUS, I made sure that it only used port 80.  In looking in IIS, I do not see anything that is pointing to port 8530.  Also, in WSUS, I had copied the same config as our other replica server to our primary server.

    In looking at the site bindings in IIS, the only thing listed for Http is port 80.

    The client system is not finding the 'ClientWebService' v-dir on the Default Web Site of your WSUS server. The first place to look would be to see if there is a 'ClientWebService' v-dir on the Default Web Site of that server. If there is, then inspect the IIS logs for GETs from that client to that resource and determine why the webserver is returning an HTTP 404 error. (There are many reasons; a non-existent target is but one of a dozen possible causes, and the most commonly encountered.)

    The image of the console tells us that there's a functioning APIRemoting30 v-dir on the server on port 80, but that's all we can infer from that image.

    Also, it presumes that the console and the client are actually talking to the same machine. All we know from the information presented is that they're configured to talk to the same hostname, but that may or may not actually be the same machine where the communication is being sent.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Distribution (2005-2012)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

     
  • Monday, November 19, 2012 7:29 PM
     
     Answered
    Sign In to Vote
    0

    Well, it's starting to look like a NIC driver update may have resolved my issues.  Computers are now starting to check in and the servers are now starting to show the correct set of matching items.  How frustrating. 

    I'll keep an eye on this and if the rest of the computers don't check in by tomorrow, i'll follow up again.

    Thanks for everyones help thus far.

    Mike

     
  • Tuesday, November 27, 2012 3:01 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help.

    Regards,

    Clarence

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.