登录
Microsoft.com
 
Microsoft
 
 
 

none
WSUS升级WIN7系统补丁遇到问题 RRS feed

 > 

  • 问题

  • Question
    登录进行投票
    0
    登录进行投票

    请帮忙查看如下报错出现的原因是什么，如何解决，谢谢！

    2018-01-09 14:27:53:524 304 31c PT WARNING: Cached cookie has expired or new PID is available
    2018-01-09 14:27:53:524 304 31c PT Initializing simple targeting cookie, clientId = 933a7612-7689-4263-999f-0a860c868d53, target group = , DNS name = cnwf054.hk-pkc.local
    2018-01-09 14:27:53:524 304 31c PT   Server URL = http://10.7.1.51:8530/SimpleAuthWebService/SimpleAuth.asmx
    2018-01-09 14:28:14:583 304 31c Misc WARNING: Send failed with hr = 80072ee2.
    2018-01-09 14:28:14:583 304 31c Misc WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
    2018-01-09 14:28:14:583 304 31c Misc FATAL: SOAP/WinHttp - SendRequest: SendRequestUsingProxy failed. error 0x80072ee2
    2018-01-09 14:28:14:583 304 31c PT   + Last proxy send request failed with hr = 0x80072EE2, HTTP status code = 0
    2018-01-09 14:28:14:583 304 31c PT   + Caller provided credentials = No
    2018-01-09 14:28:14:583 304 31c PT   + Impersonate flags = 0
    2018-01-09 14:28:14:583 304 31c PT   + Possible authorization schemes used = 
    2018-01-09 14:28:14:583 304 31c PT WARNING: GetAuthorizationCookie failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200
    2018-01-09 14:28:14:583 304 31c PT WARNING: Failed to initialize Simple Targeting Cookie: 0x80072ee2
    2018-01-09 14:28:14:583 304 31c PT WARNING: PopulateAuthCookies failed: 0x80072ee2
    2018-01-09 14:28:14:583 304 31c PT WARNING: RefreshCookie failed: 0x80072ee2
    2018-01-09 14:28:14:583 304 31c PT WARNING: RefreshPTState failed: 0x80072ee2
    2018-01-09 14:28:14:583 304 31c PT WARNING: PTError: 0x80072ee2
    2018-01-09 14:28:14:583 304 31c Report WARNING: Reporter failed to upload events with hr = 80072ee2.
    2018-01-09 14:51:12:143 304 122c PT WARNING: Cached cookie has expired or new PID is available
    2018-01-09 14:51:12:143 304 122c PT Initializing simple targeting cookie, clientId = 933a7612-7689-4263-999f-0a860c868d53, target group = , DNS name = cnwf054.hk-pkc.local
    2018-01-09 14:51:12:143 304 122c PT   Server URL = http://10.7.1.51:8530/SimpleAuthWebService/SimpleAuth.asmx
    2018-01-09 14:51:12:346 304 122c Report Uploading 1 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:361 304 122c Report Reporter successfully uploaded 1 events.
    2018-01-09 14:51:12:377 304 122c Report Uploading 2 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:377 304 122c Report Reporter successfully uploaded 2 events.
    2018-01-09 14:51:12:408 304 122c Report Uploading 1 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:408 304 122c Report Reporter successfully uploaded 1 events.
    2018-01-09 14:51:12:439 304 122c Report Uploading 2 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:439 304 122c Report Reporter successfully uploaded 2 events.
    2018-01-09 14:51:12:470 304 122c Report Uploading 5 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:486 304 122c Report Reporter successfully uploaded 5 events.
    2018-01-09 14:51:12:486 304 122c Report Uploading 2 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-09 14:51:12:486 304 122c Report Reporter successfully uploaded 2 events.

    2018年1月9日 7:30
    |

全部回复

  • Question
    登录进行投票
    0
    登录进行投票
    您好，

    根据我的研究，建议您可以参考下面的步骤进行故障排查：
    1. 在客户端上打开注册表HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate，检查其配置是否正确。
    2. 打开浏览器，看看是否能够访问http://<WSUS服务器地址:端口>/SimpleAuthWebService/SimpleAuth.asmx。

    另外，WSUS服务器工作正常吗？其他客户端是否可以顺利获取并安装补丁？建议检查一下WSUS服务器看看是否有ID为1309或5117的事件日志。

    如果需要进一步的帮助，请随时告诉我们。

    此致
    Albert

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

    2018年1月10日 11:30
    |
  • Question
    登录进行投票
    0
    登录进行投票

    经过排查，Win7电脑可以访问WSUS服务了，但是在AD同一个OU底下，设置了同样的策略，Win10系统的电脑可以正常连接WSUS服务并有更新进度，Win7电脑终端及Server均无进度汇报。我做过的操作如下：通过组策略关闭了win7电脑及win10电脑的防火墙，启用了windows update服务，通过手工在控制面板windows update测试更新可以正常连接微软服务器并更新补丁包，就是不能与wsus服务器通讯，一直是显示尚未报告状态，请问这是怎么回事呢？

    2018年1月11日 2:47
    |
  • Question
    登录进行投票
    0
    登录进行投票

    在WIN7电脑更新WSUS补丁收集到的报错日

    2018-01-11 10:53:53:478 304 888 Report Uploading 1 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-11 10:53:53:493 304 888 PT WARNING: ReportEventBatch failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2018-01-11 10:53:53:493 304 888 PT WARNING: SOAP Fault: 0x000190
    2018-01-11 10:53:53:493 304 888 PT WARNING:     faultstring:服务器无法处理请求。 ---> “Microsoft.UpdateServices.Internal.Reporting.WebService”的类型初始值设定项引发异常。 ---> 无法打开登录所请求的数据库 "SUSDB"。登录失败。
    用户 'NT AUTHORITY\NETWORK SERVICE' 登录失败。
    2018-01-11 10:53:53:493 304 888 PT WARNING:     ErrorCode:(null)(0)
    2018-01-11 10:53:53:493 304 888 PT WARNING:     Message:(null)
    2018-01-11 10:53:53:493 304 888 PT WARNING:     Method:(null)
    2018-01-11 10:53:53:493 304 888 PT WARNING:     ID:(null)
    2018-01-11 10:53:53:493 304 888 Report WARNING: Reporter failed to upload events with hr = 8024400e.
    2018-01-11 10:55:50:094 304 9d8 AU AU received policy change subscription event
    2018-01-11 10:56:50:134 304 454 AU Triggering AU detection through DetectNow API
    2018-01-11 10:56:50:134 304 454 AU Triggering Online detection (non-interactive)
    2018-01-11 10:56:50:134 304 9d8 AU #############
    2018-01-11 10:56:50:134 304 9d8 AU ## START ##  AU: Search for updates
    2018-01-11 10:56:50:134 304 9d8 AU #########
    2018-01-11 10:56:50:134 304 9d8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {60AF7A37-B6F8-4ADD-96FC-186AA4548711}]
    2018-01-11 10:56:50:134 304 888 Agent *************
    2018-01-11 10:56:50:134 304 888 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2018-01-11 10:56:50:134 304 888 Agent *********
    2018-01-11 10:56:50:134 304 888 Agent   * Online = Yes; Ignore download priority = No
    2018-01-11 10:56:50:134 304 888 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"
    2018-01-11 10:56:50:134 304 888 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2018-01-11 10:56:50:134 304 888 Agent   * Search Scope = {Machine}
    2018-01-11 10:56:50:134 304 888 Setup Checking for agent SelfUpdate
    2018-01-11 10:56:50:134 304 888 Setup Client version: Core: 7.6.7601.23806  Aux: 7.6.7601.23806
    2018-01-11 10:56:50:149 304 888 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190194
    2018-01-11 10:56:50:149 304 888 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190194
    2018-01-11 10:56:50:149 304 888 Misc WARNING: DownloadFileInternal failed for http://10.7.1.51:8530//selfupdate/wuident.cab: error 0x80190194
    2018-01-11 10:56:50:149 304 888 Setup FATAL: DownloadCab failed, err = 0x80190194
    2018-01-11 10:56:50:149 304 888 Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244019
    2018-01-11 10:56:50:149 304 888 Setup FATAL: SelfUpdate check failed, err = 0x80244019
    2018-01-11 10:56:50:149 304 888 Agent   * WARNING: Skipping scan, self-update check returned 0x80244019
    2018-01-11 10:56:50:149 304 888 Agent   * WARNING: Exit code = 0x80244019
    2018-01-11 10:56:50:149 304 888 Agent *********
    2018-01-11 10:56:50:149 304 888 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2018-01-11 10:56:50:149 304 888 Agent *************
    2018-01-11 10:56:50:149 304 888 Agent WARNING: WU client failed Searching for update with error 0x80244019
    2018-01-11 10:56:50:149 304 1338 AU >>##  RESUMED  ## AU: Search for updates [CallId = {60AF7A37-B6F8-4ADD-96FC-186AA4548711}]
    2018-01-11 10:56:50:149 304 1338 AU   # WARNING: Search callback failed, result = 0x80244019
    2018-01-11 10:56:50:149 304 1338 AU   # WARNING: Failed to find updates with error code 80244019
    2018-01-11 10:56:50:149 304 1338 AU #########
    2018-01-11 10:56:50:149 304 1338 AU ##  END  ##  AU: Search for updates [CallId = {60AF7A37-B6F8-4ADD-96FC-186AA4548711}]
    2018-01-11 10:56:50:149 304 1338 AU #############
    2018-01-11 10:56:50:149 304 1338 AU Successfully wrote event for AU health state:0
    2018-01-11 10:56:50:149 304 1338 AU AU setting next detection timeout to 2018-01-11 07:56:50
    2018-01-11 10:56:50:149 304 1338 AU Setting AU scheduled install time to 2018-01-11 04:00:00
    2018-01-11 10:56:50:149 304 1338 AU Successfully wrote event for AU health state:0
    2018-01-11 10:56:50:149 304 1338 AU Successfully wrote event for AU health state:0
    2018-01-11 10:56:55:157 304 888 Report REPORT EVENT: {740FBAA6-5263-440B-9412-D58643BFE01C} 2018-01-11 10:56:50:149+0800 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244019 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80244019.
    2018-01-11 10:56:55:157 304 888 Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
    2018-01-11 10:56:55:157 304 888 Report WER Report sent: 7.6.7601.23806 0x80244019(0) 67661EB-2423-451D-BF5D-13199E37DF28 Scan 1 0 SelfUpdate {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} 0
    2018-01-11 10:57:30:085 304 888 Report Uploading 1 events using cached cookie, reporting URL = http://10.7.1.51:8530/ReportingWebService/ReportingWebService.asmx
    2018-01-11 10:57:30:100 304 888 PT WARNING: ReportEventBatch failure, error = 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code = 200
    2018-01-11 10:57:30:100 304 888 PT WARNING: SOAP Fault: 0x000190
    2018-01-11 10:57:30:100 304 888 PT WARNING:     faultstring:服务器无法处理请求。 ---> “Microsoft.UpdateServices.Internal.Reporting.WebService”的类型初始值设定项引发异常。 ---> 无法打开登录所请求的数据库 "SUSDB"。登录失败。
    用户 'NT AUTHORITY\NETWORK SERVICE' 登录失败。
    2018-01-11 10:57:30:100 304 888 PT WARNING:     ErrorCode:(null)(0)
    2018-01-11 10:57:30:100 304 888 PT WARNING:     Message:(null)
    2018-01-11 10:57:30:100 304 888 PT WARNING:     Method:(null)
    2018-01-11 10:57:30:100 304 888 PT WARNING:     ID:(null)
    2018-01-11 10:57:30:100 304 888 Report WARNING: Reporter failed to upload events with hr = 8024400e.

    请帮忙判断一下问题出在哪里，谢谢！

    2018年1月11日 3:27
    |
  • Question
    登录进行投票
    0
    登录进行投票
    您好，

    我们现在正在研究这个问题，会尽快回复。感谢您的理解与耐心。
    另外，如果在此过程中有任何更新，请随时通知我。

    此致
    Albert

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

    2018年1月12日 9:33
    |
  • Question
    登录进行投票
    0
    登录进行投票
    您好，

    抱歉回复晚了。根据“用户 'NT AUTHORITY\NETWORK SERVICE' 登录失败”这个错误来看，请问是否为WSUS服务器上的%windir%\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files配置过完全访问权限？下面的截图供您参考：


    另外，建议您参考下面的系列文章对WSUS服务器的部署进行检查，看看是否都配置正确。之后再试一次看看问题是否依然存在，报错信息是否会改变：
    步骤 1：为你的 WSUS 部署做好准备
    https://technet.microsoft.com/zh-cn/library/hh852344(v=ws.11).aspx

    如果您需要进一步的帮助，请告诉我们。

    此致
    Albert

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

    2018年1月15日 8:42
    |
  • Question
    登录进行投票
    0
    登录进行投票
    您好，

    我想确认一下目前的情况，请问您试过之前所提供的方法吗？

    如果您已经尝试过，或者在试过之后仍然有问题，请告诉我们，我会做更多研究，并尽我所能给出有帮助的答复。

    如果您需要进一步的帮助，请告诉我们。

    此致
    Albert

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

    2018年1月17日 8:44
    |
  • Question
    登录进行投票
    0
    登录进行投票
    您好，

    我正在查看这个问题的进度，如果您有任何问题，请随时与我们联系。

    如果您使用我们的方法解决了问题，请将其“标记为答复”，以帮助其他社区成员能够快速找到有帮助的答复。
    如果您使用自己的方法解决了问题，请在此分享您的经验，这将对其他有类似问题的社区成员非常有益。
    如果问题还没有解决，请回复并告诉我们目前的情况，以便我们能够提供进一步的帮助。

    期待您的反馈。

    此致
    Albert

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

    2018年1月19日 2:32
    |