none
Windows Server Update Services 安装好后的同步为什么总是出错? RRS feed

  • 问题

  • 全新安装的 Windows Server 2019 系统,安装了 Windows Server Update Services ,从第一次同步到现在的多次同步都失败。以前安装过 2008 和 2012 版中的 WSUS 同步也总是失败。

    选项中语言只选择了简体中文和英文,选择了所有产品和所有分类,选择了存储更新文件到本地服务器。可从安装完成到现在从来没有一次同步成功过。

    以下是几次同步失败的详细信息:

    InvalidOperationException: There is an error in XML document (1, 14886). ---> System.Net.WebException: The operation has timed out.
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAnd


    InvalidOperationException: There is an error in XML document (1, 29328). ---> System.Net.WebException: The operation has timed out.
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAnd


    InvalidOperationException: There is an error in XML document (1, 1113843). ---> System.Net.WebException: The operation has timed out.
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)


    InvalidOperationException: There is an error in XML document (1, 27246363). ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetRevisionIdList(Cookie cookie, ServerSyncFilter filter)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetRevisionIdList(ServerSyncFilter filter, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.ExecuteSyncProtocol(Boolean allowRedirect)


    InvalidOperationException: There is an error in XML document (5, 8349). ---> System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream.
    at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
       at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
       at Microsoft.UpdateServices.ServerSyncWebServices.ServerSync.ServerSyncProxy.GetUpdateData(Cookie cookie, UpdateIdentity[] updateIds)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.WebserviceGetUpdateData(UpdateIdentity[] updateIds, List`1 allMetadata, List`1 allFileUrls, List`1& updatesWithSecureFileData, Boolean isForConfig)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetUpdateDataInChunksAndImport(List`1 neededUpdates, List`1 allMetadata, List`1 allFileUrls, Boolean isConfigData)
       at Microsoft.UpdateServices.ServerSync.CatalogSyncAgentCore.GetAnd

    请问可能的原因是什么?

    2020年4月28日 8:20

全部回复

  • 请检查以下内容

     

    1. 验证主机名是否正确。
    2. 验证默认端口是否正确。对于Windows Server 2012 R2和更高版本,默认为端口8530
    3. 确保端口是开放的,并且主机名可以由DNS解析
    4. 验证与上游服务器的网络连
    5. 验证下游服务器是否已连接到上游服务器
    6. 使用WSUS console检查代理服务器设置
    7. 如果WSUS服务器通过代理服务器连接到Microsoft Update,则必须使用WSUS console来配置WSUS,以便它可以访问Internet
    8. 检查防火墙设置
    9. 如果您的网络在WSUS服务器和Internet之间具有防火墙,请确保打开了所有必要的端口,并允许了必要的域。

     

    您也可以参考下面这个链接,不过论坛不支持日志分析,进一步分析需要开case.

     

    https://support.microsoft.com/zh-cn/help/4482416/wsus-synchronization-fails-with-soapexception

     

    Best regard,

    Sylvia


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2020年4月30日 8:12
  • 您好,

     

    您的问题解决了吗?

    如果回复对您有所帮助,请记住将其标记为答案。

    如果否,请回复并告诉我们当前情况,以便提供进一步的帮助。

     

    Best regard,

    Sylvia


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2020年5月5日 1:33
  • 您好,

    1. 如何验证主机名是否正确?我在局域网内用 ping 带 -a 参数命令可以正确解析到该 WSUS 主机的主机名。请问这是否算验证正确了?
        为何要验证主机名是否正确?不正确的主机名系统本身就不允许设置的吧?

    2. 通过 netstat -an 命令查看 8530 端口 处于监听状态
        TCP    0.0.0.0:8530           0.0.0.0:0              LISTENING
    这里有个问题,我是本 WSUS 服务器无法与上游,即 Microsoft 官方的 Update 服务器同步,而不是我客户端无法与本 WSUS 服务器同步,那么本 WSUS 服务器的 8530 端口是否开放是否影响到与上游服务器(无论是否是 Microsoft 的官方 Update 服务器)的同步?

    3. 本环境不是域环境,所以没有内部 DNS 服务器,该 WSUS 服务器主机名也不能由外部的 DNS 解析。

    4. 如何验证与上游服务器的网络连接?不知道 WSUS 所查询的 Microsoft Update 服务器的域名是什么,或 IP 是什么

    5. 没有下游服务器

    6. 7. 原来没有使用通过代理连接到 Microsoft Update ,后来想会不会是现在出口流量小了所以同步总是失败,所以就试了下用代理连接试试,在 Update Services 控制台的 Options 中 Update Source and Proxy Server 中就有代理服务器设置,不知为何必须使用 WSUS console 来配置 WSUS ?
    Proxy Server

    8. 您是指 WSUS 主机本身的防火墙还是网关的防火墙?防火墙要怎么样设置才能符合 WSUSU 向上游服务器同步的要求?

    9. 网络环境很简单,即一个 LAN 通过 NAT Gateway 连接到 Internet ,网关上无特别的防火墙,如果是 LAN 内的客户端单独连接到 Windows Update 是可以更新的。所以我认为问题4应该没什么问题,不知这点是否正确?

    2020年5月6日 7:22
  • 您好,

    看了下同步报告,所有的出错原因都是由于依赖性引起的:

    Synchronization Errors
    Error Update ID
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    0dae744b-956e-4c8f-b1dd-c1aefcb93f4f : Revision
    101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    23917592-b4fe-4398-b963-7d5303aeddd2 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    104d0058-a143-4563-91c1-c6741a04435a :
    Revision 101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    085d3558-9bf6-47cc-89df-05b540decebc :
    Revision 103
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    47be2327-2939-4f8b-8cc0-69b4648be0f1 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    5dba9b10-1e20-4b11-9389-42f5e5653b13 :
    Revision 103
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    4d287ad6-a11b-4432-880e-f7a18c3529e0 :
    Revision 101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    4b8fa40d-c9dc-4cca-871a-da7a4971e5eb :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    52dad270-ad0d-4c27-a0f2-019d721efa52 :
    Revision 101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    61b91bad-cefe-4dee-9a41-069430d2b069 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    3ab4e365-5526-46d5-91f0-fca795a9799c :
    Revision 101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    3c028685-8529-43b2-bf9d-5b776bc60260 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    929766ee-7bf9-4fd1-9054-88d7d92326e0 :
    Revision 101
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    76696123-bd1f-4528-8993-5189f4610b36 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    8c2fa024-ad38-4500-a67c-1557f950327f :
    Revision 103
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    7d1f9a57-f115-488b-8259-cf5c1f0842ed : Revision
    104
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    7aa7e421-a957-4db1-901e-e7abc80a0660 :
    Revision 102
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    6e076709-14c1-4b3d-8294-d9080ea59848 :
    Revision 104
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    7546fd13-bc6d-4d0f-aa49-1de3e4e51edf :
    Revision 103
    A dependency of the update was not found on the server and was not
    provided by the upstream server.
    7b7d1543-d120-4a45-ae24-7095e07fc4fd :
    Revision 102

    我设置的是手动 synchronize 和手动 approve ,不知是否是因为需要先 approve 一些 updates 才能进一步 synchronize 的原因?

    2020年5月28日 1:43
  • 你好,请问你的问题解决了没有?我也有相同的问题,几天过去了,找不到问题原因所在。我是用VMware  workstation上安装 Windows 2019,2016,2012的WSUS服务,但都不能同步。
    2020年11月14日 16:59