积极答复者
通过wsus更新windows10 LTSC 2019 报 0x80244019 错误

问题
-
之前原有的WSUS服务器可以更新,然后我重新建了一个WSUS 并将地址更换到了新的wsus服务器上,但是之前从原有wsus服务器可以更新的计算机,检查更新均显示 0x80244019的错误,同时wsus服务器上不能看到计算机。但是之前没有设置过wsus更新的电脑可以正常注册到WSUS并获取更新
尝试过删除SoftwareDistribution,重新启动update服务 以及使用wuauclt /detectnow命令进行注册均不能解决问题。
这里是windowsupdate.log内容
2019/04/12 14:08:25.8489291 3924 4164 ComApi * START * Federated Search ClientId = UpdateOrchestrator (cV: N7aVSptn/EKork2L.1.1.0)
2019/04/12 14:08:25.8516888 4056 6132 IdleTimer WU operation (SR.UpdateOrchestrator ID 13) started; operation # 45; does use network; is not at background priority
2019/04/12 14:08:25.8560399 4056 5400 IdleTimer WU operation (SR.UpdateOrchestrator ID 13, operation # 45) stopped; does use network; is not at background priority
2019/04/12 14:08:25.8662197 3924 8444 ComApi Federated Search: Starting search against 1 service(s) (cV = N7aVSptn/EKork2L.1.1.0)
2019/04/12 14:08:25.8663659 3924 8444 ComApi * START * Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7, Flags: 0X40010010 (cV = N7aVSptn/EKork2L.1.1.0.0)
2019/04/12 14:08:25.8681193 4056 6132 IdleTimer WU operation (CSearchCall::Init ID 14) started; operation # 48; does use network; is not at background priority
2019/04/12 14:08:25.8778067 4056 6132 Agent * START * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 14]
2019/04/12 14:08:25.8778119 4056 6132 Agent Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
2019/04/12 14:08:25.8778170 4056 6132 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
2019/04/12 14:08:25.8778211 4056 6132 Agent Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
2019/04/12 14:08:25.8779350 4056 2196 Agent Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
2019/04/12 14:08:25.8829711 4056 2312 Agent * END * Queueing Finding updates [CallerId = UpdateOrchestrator Id = 14]
2019/04/12 14:08:25.8872947 4056 2312 Agent * START * Finding updates CallerId = UpdateOrchestrator Id = 14 (cV = N7aVSptn/EKork2L.1.1.0.0.2)
2019/04/12 14:08:25.8872978 4056 2312 Agent Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = No
2019/04/12 14:08:25.8873025 4056 2312 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""
2019/04/12 14:08:25.8873059 4056 2312 Agent ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2019/04/12 14:08:25.8873070 4056 2312 Agent Search Scope = {Machine}
2019/04/12 14:08:25.8873114 4056 2312 Agent Caller SID for Applicability: S-1-5-21-1233713881-4117148406-1005165710-1113
2019/04/12 14:08:25.8873123 4056 2312 Agent ProcessDriverDeferrals is set
2019/04/12 14:08:25.8873839 4056 2312 Agent *FAILED* [8024043D] GetIsInventoryRequired
2019/04/12 14:08:25.9181562 4056 2312 Misc Got WSUS Client/Server URL: http://42.205.169.10/8530/ClientWebService/client.asmx""
2019/04/12 14:08:25.9210541 4056 2312 Driver Skipping printer driver 3 due to incomplete info or mismatched environment - HWID[(null)] Provider[Microsoft] MfgName[Microsoft] Name[Remote Desktop Easy Print] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
2019/04/12 14:08:25.9210586 4056 2312 Driver Skipping printer driver 7 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
2019/04/12 14:08:26.0184023 4056 2312 ProtocolTalker ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://42.205.169.10/8530/ClientWebService/client.asmx
2019/04/12 14:08:26.0185297 4056 2312 ProtocolTalker PT: Calling GetConfig on server
2019/04/12 14:08:26.0185395 4056 2312 IdleTimer WU operation (CAgentProtocolTalker::GetConfig_WithRecovery) started; operation # 49; does use network; is at background priority
2019/04/12 14:08:26.0185668 4056 2312 WebServices Auto proxy settings for this web service call.
2019/04/12 14:08:26.0244564 4056 2312 WebServices WS error: ???http://42.205.169.10/8530/ClientWebService/client.asmx???????????
2019/04/12 14:08:26.0244585 4056 2312 WebServices WS error: ?????HTTP ????04 (0x194)?????ot Found??
2019/04/12 14:08:26.0244594 4056 2312 WebServices WS error: ???????
2019/04/12 14:08:26.0244626 4056 2312 WebServices *FAILED* [80244019] Web service call
2019/04/12 14:08:26.0244636 4056 2312 WebServices Current service auth scheme=0.
2019/04/12 14:08:26.0244644 4056 2312 WebServices Current Proxy auth scheme=0.
2019/04/12 14:08:26.0244705 4056 2312 IdleTimer WU operation (CAgentProtocolTalker::GetConfig_WithRecovery, operation # 49) stopped; does use network; is at background priority
2019/04/12 14:08:26.0244763 4056 2312 ProtocolTalker *FAILED* [80244019] GetConfig_WithRecovery failed
2019/04/12 14:08:26.0244781 4056 2312 ProtocolTalker *FAILED* [80244019] RefreshConfig failed
2019/04/12 14:08:26.0244800 4056 2312 ProtocolTalker *FAILED* [80244019] RefreshPTState failed
2019/04/12 14:08:26.0244833 4056 2312 ProtocolTalker SyncUpdates round trips: 0
2019/04/12 14:08:26.0244845 4056 2312 ProtocolTalker *FAILED* [80244019] Sync of Updates
2019/04/12 14:08:26.0244934 4056 2312 ProtocolTalker *FAILED* [80244019] SyncServerUpdatesInternal failed
希望各位能够找到问题的所在并帮助我解决问题,谢谢
答案
-
您好,
感谢您在此发帖。
80244019表示找不到404文件, 错误不是客户端, 而是试图从 WSUS 服务器下载的文件在 WSUS 内容文件夹中不可用。WSUS 过去使用 p/80, 并且 http p/8530 是可选的, 但是, 现在 http p/8530 是默认值, 因此, 如果您不将 WSUS (通过注册表或 GP) 设置为指定的端口, 则客户端将默认为端口 80, 并且除了常量 404 之外, 客户端在该端口上不会有太多。
您需要使用更新的 WSUS 服务器和端口号更新组策略。您看到404错误, 因为工作站指向了错误的服务器。
Best regards,
Hurry
Please remember to mark the reply as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已建议为答案 hurry yang 2019年4月21日 13:11
- 已标记为答案 bossmacmillan 2020年9月20日 10:18
全部回复
-
您好,
感谢您在此发帖。
80244019表示找不到404文件, 错误不是客户端, 而是试图从 WSUS 服务器下载的文件在 WSUS 内容文件夹中不可用。WSUS 过去使用 p/80, 并且 http p/8530 是可选的, 但是, 现在 http p/8530 是默认值, 因此, 如果您不将 WSUS (通过注册表或 GP) 设置为指定的端口, 则客户端将默认为端口 80, 并且除了常量 404 之外, 客户端在该端口上不会有太多。
您需要使用更新的 WSUS 服务器和端口号更新组策略。您看到404错误, 因为工作站指向了错误的服务器。
Best regards,
Hurry
Please remember to mark the reply as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已建议为答案 hurry yang 2019年4月21日 13:11
- 已标记为答案 bossmacmillan 2020年9月20日 10:18
-
您好,
感谢您的反馈。
请问您这个问题进展的怎么样了?
希望您能及时给我一个反馈。
Best regards,
Hurry
Please remember to mark the reply as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
您好,
请问您的问题进展的如何了?
如果我的回答解决了您的问题并对您有所帮助,麻烦请将这个回答建议作为答复。
如果有需要进一步的帮助,请随时联系我。
Best regards,
Hurry
Please remember to mark the reply as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com -
您好,
感谢您的反馈。
1. 请尝试做一个干净的启动。
2. 尝试安装最新的更新并检查。
Best regards,
Hurry
Please remember to mark the reply as an answer if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com- 已编辑 hurry yang 2019年4月28日 13:51
-