locked
Problem synchronizing w2012 server with wsus server RRS feed

  • Question

  • Hi,

    I have some server 2012 which cannot synchronize with a wsus server (version 6.2).

    I have reviewed this page (https://technet.microsoft.com/en-us/library/dd939857(v=ws.10).aspx) and have checked that everything is fine from the client (server 2012) but, I don't know why the servers don't contact with the wsus.

    The rest of pc are synchronizing without problem.

    In the gpmc I have a policy which apply to these servers but looking in "Local compute policy > Computer Configuration > Administrative Templates > Windows" the settings are not filled, however in the regedit the settings are correct.

    Can anybody help me?

    Thanks in advanve.


    Friday, June 12, 2015 2:53 PM

Answers

  • Hi,

    Please find the Fatal entry in the Windowsupdate.log.

    Not all warnings are  critical errors. Start with the fatal errors and then work to the top of the Windowsupdate.log log file to make sure that you have identified the correct error message.

    Here is a good article about how to troubleshooting WSUS issue by using windowsupdate.log file.

    https://support.microsoft.com/en-us/kb/902093

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, July 7, 2015 9:46 AM

All replies

  • have you checked the WindowsUpdate.log ?
    Friday, June 12, 2015 8:23 PM
  • Thanks for your help.

    This is a part of the log from the client side (server 2012):

    2015-06-16 13:14:46:630 836 1ffc EP Got WSUS Client/Server URL: "http://wsus:8530/ClientWebService/client.asmx"
    2015-06-16 13:14:46:662 836 1ffc PT WARNING: Cached cookie has expired or new PID is available
    2015-06-16 13:14:46:677 836 1ffc EP Got WSUS SimpleTargeting URL: "http://wsus:8530"
    2015-06-16 13:14:46:693 836 1ffc PT Initializing simple targeting cookie, clientId = 43049195-b904-4998-8345-52dce769ab63, target group = WSUS Servers (2012), DNS name = wsusserver.mydomain.com
    2015-06-16 13:14:46:693 836 1ffc PT  Server URL = http://wsus:8530/SimpleAuthWebService/SimpleAuth.asmx
    2015-06-16 13:14:46:708 836 1ffc WS WARNING: Nws Failure: errorCode=0x803d0013
    2015-06-16 13:14:46:724 836 1ffc WS WARNING: The body of the received message contained a fault.
    2015-06-16 13:14:46:724 836 1ffc WS WARNING: Soap fault info:
    2015-06-16 13:14:46:724 836 1ffc WS WARNING: reason: Fault occurred
    2015-06-16 13:14:46:724 836 1ffc WS WARNING: code: Server

    I'm looking for information abour the first warning but without success at the moment..

    Tuesday, June 16, 2015 11:35 AM
  • Hi,

    Please find the Fatal entry in the Windowsupdate.log.

    Not all warnings are  critical errors. Start with the fatal errors and then work to the top of the Windowsupdate.log log file to make sure that you have identified the correct error message.

    Here is a good article about how to troubleshooting WSUS issue by using windowsupdate.log file.

    https://support.microsoft.com/en-us/kb/902093

    Best Regards.


    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Tuesday, July 7, 2015 9:46 AM