SBS 2008 上的 IIS 7 - 日志记录变得混乱

Question

JukEboX

Asked: 2018-11-29 13:26:46 +0800 CST2018-11-29 13:26:46 +0800 CST 2018-11-29 13:26:46 +0800 CST

如何在 1809 之后将客户端重新连接到 WSUS 导致安装后出现问题

772

使用 1809 更新对我们的测试环境进行一些测试。此系统不是 Internet，仅从 WSUS 获取更新。我试图停止服务并重命名 SoftwareDistribution 文件夹，但这也无济于事。我已经完成了疑难解答，但这并没有做任何事情。我已将交付优化设置为简单 (99)。

我正在停止尝试使用此 GPO 设置连接到 Internet：

Computer Configuration > Administrative Templates > Windows Components > Windows Update > Do not connect to any Windows Update Internet locations

运行 powershell 命令后(New-Object -ComObject 'Microsoft.Update.ServiceManager').Services

我得到结果Windows Server Update Service IsDefautlAUService = True

修补了从 2018.11.13 到 17763.134 的 11-2018 更新

我已经在 1809 上进行了 Windows 重置，看看是否可以解决问题，但它只是显示了同样的问题。系统不会检查 WSUS 的更新并说它无法连接。它甚至不会向 WSUS 重新注册，因为我们设置了客户端定位。

这就是错误目前向我展示的内容。

这是我目前的日志。试图找出错误是什么LoadHistoryEventsFromRegistry。Microsoft 没有关于这些问题的信息。

    InitializeSus
2018/12/07 07:30:59.6145871 5316  76    IdleTimer       Non-AoAc machine.  Aoac operations will be ignored.
2018/12/07 07:30:59.6146719 5316  76    Agent           WU client version 10.0.17763.107
2018/12/07 07:30:59.6149469 5316  76    Agent           SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2018/12/07 07:30:59.6150268 5316  76    Agent           Base directory: C:\WINDOWS\SoftwareDistribution
2018/12/07 07:30:59.6179939 5316  76    Agent           Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore\DataStore.edb
2018/12/07 07:30:59.6190270 5316  76    DataStore       JetEnableMultiInstance succeeded - applicable param count: 5, applied param count: 5
2018/12/07 07:31:00.1001631 5316  76    DataStore       Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 added
2018/12/07 07:31:00.1188537 5316  76    DataStore       Service 9482F4B4-E343-43B6-B170-9A65BC822C77 added
2018/12/07 07:31:00.1202710 5316  76    DataStore       Data store successfully created
2018/12/07 07:31:00.1254989 5316  76    Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/12/07 07:31:00.1260950 5316  76    Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/12/07 07:31:00.1307344 5316  76    Shared          Network state: Connected
2018/12/07 07:31:00.5661308 5316  76    Agent           Created new random SusClientId 5ee99c27-c788-4ed7-910d-be7ecefcb4d3. Old Id: none.
2018/12/07 07:31:00.5753449 5316  76    Misc            *FAILED* [8024000C] LoadHistoryEventFromRegistry completed
2018/12/07 07:31:00.5756015 5316  76    Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/12/07 07:31:00.5756166 5316  76    Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/12/07 07:31:00.5756276 5316  76    Shared          Power status changed
2018/12/07 07:31:00.5819017 5316  76    Agent           WU client refresh cache for DisableWUAccess policy: 1
2018/12/07 07:31:00.5819073 5316  76    Agent           Initializing global settings cache
2018/12/07 07:31:00.5819100 5316  76    Agent           WSUS server: http://WSUS.DOMAIN.460i:8530
2018/12/07 07:31:00.5819125 5316  76    Agent           WSUS status server: http://WSUS.DOMAIN.460i:8530
2018/12/07 07:31:00.5819151 5316  76    Agent           Alternate Download Server: http://IWSUS.DOMAIN.460i:8530
2018/12/07 07:31:00.5819167 5316  76    Agent           Fill Empty Content Urls: No
2018/12/07 07:31:00.5819186 5316  76    Agent           Target group: Update Testing
2018/12/07 07:31:00.5819207 5316  76    Agent           Windows Update access disabled: Yes
2018/12/07 07:31:00.5819227 5316  76    Agent           Do not connect to Windows Update Internet locations: Yes
2018/12/07 07:31:00.5999439 5316  76    Agent           Initializing Windows Update Agent
2018/12/07 07:31:00.6001722 5316  76    Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x80248007
2018/12/07 07:31:00.6001826 5316  76    Agent           CPersistentTimeoutEvent | Resubscribe, no existing/cached timer for Id=29A863E7-8609-4D1E-B7CD-5668F857F1DB.
2018/12/07 07:31:00.6001961 5316  76    Agent           Adding timer: 
2018/12/07 07:31:00.6002034 5316  76    Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-12-08 12:31:01, not idle-only, not network-only
2018/12/07 07:31:00.6017327 5316  76    IdleTimer       IdleTimer::NetworkStateChanged. Network connected? Yes
2018/12/07 07:31:00.6152671 5316  2732  DownloadManager HandleScavengeSandboxTask: Cleaning up sandboxes.
2018/12/07 07:31:00.6337411 5316  2732  DownloadManager PurgeExpiredFiles::Found 0 expired files to delete.
2018/12/07 07:31:00.6337679 5316  2732  DownloadManager PurgeExpiredUpdates: Found 0 non expired updates.
2018/12/07 07:31:00.6337761 5316  2732  DownloadManager PurgeExpiredUpdates: Found 0 expired updates.
2018/12/07 07:31:00.6446587 5316  2732  DownloadManager Received power state change notification: Old: <unknown>; New: AC.
2018/12/07 07:31:00.6446609 5316  2732  DownloadManager Power state changed from <unknown> to AC.
2018/12/07 07:32:12.5240857 5660  9008  ComApi          IUpdateServiceManager::AddService2
2018/12/07 07:32:12.5240922 5660  9008  ComApi          Service ID = {7971f918-a847-4430-9279-4a52d1efe18d}
2018/12/07 07:32:12.5240988 5660  9008  ComApi          Allow pending registration = Yes; Allow online registration = Yes; Register service with AU = Yes
2018/12/07 07:32:12.5302886 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '117CAB2D-82B1-4B5A-A08C-4D62DBEE7782'.
2018/12/07 07:32:12.5302932 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:32:12.5302982 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '855E8A7C-ECB4-4CA3-B045-1DFA50104289'.
2018/12/07 07:32:12.5303011 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:32:12.5303077 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '7971F918-A847-4430-9279-4A52D1EFE18D'.
2018/12/07 07:32:12.5303106 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:32:12.5313973 5316  9004  Agent           Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x8024500c
2018/12/07 07:32:12.5314154 5316  9004  Agent           *FAILED* [8024500C] Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 (cV: GdfTDldxRUyC9aLL.1)
2018/12/07 07:32:12.5316674 5316  9004  Agent           Failed to retrieve SLS response data for service 855e8a7c-ecb4-4ca3-b045-1dfa50104289, error = 0x8024500c
2018/12/07 07:32:12.5316725 5316  9004  Agent           *FAILED* [8024500C] Caller Service Recovery failed to opt in to service 855e8a7c-ecb4-4ca3-b045-1dfa50104289 (cV: GdfTDldxRUyC9aLL.2)
2018/12/07 07:32:12.5318996 5316  9004  Agent           Failed to retrieve SLS response data for service 7971f918-a847-4430-9279-4a52d1efe18d, error = 0x8024500c
2018/12/07 07:32:12.5319045 5316  9004  Agent           *FAILED* [8024500C] Caller UpdateOrchestrator failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d (cV: GdfTDldxRUyC9aLL.3)
2018/12/07 07:32:12.5319174 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '7971F918-A847-4430-9279-4A52D1EFE18D'.
2018/12/07 07:32:12.5319205 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:32:12.5322116 5660  9008  ComApi          Deferred service opt-in
2018/12/07 07:32:12.5366676 5660  9008  ComApi          *FAILED* [800704C6] CheckNetworkCostForCostPolicy
2018/12/07 07:33:57.7948349 5660  9008  ComApi          IUpdateServiceManager::AddService2
2018/12/07 07:33:57.7948410 5660  9008  ComApi          Service ID = {7971f918-a847-4430-9279-4a52d1efe18d}
2018/12/07 07:33:57.7948479 5660  9008  ComApi          Allow pending registration = Yes; Allow online registration = Yes; Register service with AU = Yes
2018/12/07 07:33:57.7984642 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '117CAB2D-82B1-4B5A-A08C-4D62DBEE7782'.
2018/12/07 07:33:57.7984751 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:33:57.7984884 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '855E8A7C-ECB4-4CA3-B045-1DFA50104289'.
2018/12/07 07:33:57.7984960 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:33:57.7985083 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '7971F918-A847-4430-9279-4A52D1EFE18D'.
2018/12/07 07:33:57.7985156 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
2018/12/07 07:33:57.7993250 5316  9004  Agent           Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x8024500c
2018/12/07 07:33:57.7993472 5316  9004  Agent           *FAILED* [8024500C] Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 (cV: H4qkYaccI0S+sZ8U.1)
2018/12/07 07:33:57.7999318 5316  9004  Agent           Failed to retrieve SLS response data for service 855e8a7c-ecb4-4ca3-b045-1dfa50104289, error = 0x8024500c

寻找有关如何让我的客户回叫我的 WSUS 服务器的想法。我也找不到有关此“服务”的信息。据我所知，它是一个指向在线 WU 的网络连接的链接。如果有人能告诉我有关 WSUS 如何使用这些服务 ID 或这些 FAILURE 是什么的任何信息，我们将不胜感激。

更新1： 这是我发现的最新消息。WSUS 服务器显示 1809 更新是系统需要安装的最后一个更新。安装了更新并重新启动计算机，此后，没有人签入。正如您在下面的屏幕截图中看到的那样。

受影响计算机的注册表显示问题来自的服务 ID 显示在待处理的注册表项中。不确定那是什么意思。此屏幕截图来自我从 WSUS 中删除并清除 WSUS ID 注册表项并尝试重新连接它的机器。WSUS 服务器尚未看到这台计算机，但日志出现相同的错误。请参阅下面的屏幕截图。

失败的服务 ID：

     2018/12/07 07:32:12.5302886 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '117CAB2D-82B1-4B5A-A08C-4D62DBEE7782'.
    2018/12/07 07:32:12.5302932 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
    2018/12/07 07:32:12.5302982 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '855E8A7C-ECB4-4CA3-B045-1DFA50104289'.
    2018/12/07 07:32:12.5303011 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
    2018/12/07 07:32:12.5303077 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '7971F918-A847-4430-9279-4A52D1EFE18D'.
    2018/12/07 07:32:12.5303106 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]
    2018/12/07 07:32:12.5313973 5316  9004  Agent           Failed to retrieve SLS response data for service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, error = 0x8024500c
    2018/12/07 07:32:12.5314154 5316  9004  Agent           *FAILED* [8024500C] Caller Service Recovery failed to opt in to service 117cab2d-82b1-4b5a-a08c-4d62dbee7782 (cV: GdfTDldxRUyC9aLL.1)
    2018/12/07 07:32:12.5316674 5316  9004  Agent           Failed to retrieve SLS response data for service 855e8a7c-ecb4-4ca3-b045-1dfa50104289, error = 0x8024500c
    2018/12/07 07:32:12.5316725 5316  9004  Agent           *FAILED* [8024500C] Caller Service Recovery failed to opt in to service 855e8a7c-ecb4-4ca3-b045-1dfa50104289 (cV: GdfTDldxRUyC9aLL.2)
    2018/12/07 07:32:12.5318996 5316  9004  Agent           Failed to retrieve SLS response data for service 7971f918-a847-4430-9279-4a52d1efe18d, error = 0x8024500c
    2018/12/07 07:32:12.5319045 5316  9004  Agent           *FAILED* [8024500C] Caller UpdateOrchestrator failed to opt in to service 7971f918-a847-4430-9279-4a52d1efe18d (cV: GdfTDldxRUyC9aLL.3)
    2018/12/07 07:32:12.5319174 5316  9004  Agent           *FAILED* [80248014] GetServiceObject couldn't find service '7971F918-A847-4430-9279-4A52D1EFE18D'.
    2018/12/07 07:32:12.5319205 5316  9004  Agent           *FAILED* [80248014] Method failed [CAgentServiceManager::GetServiceObject:1902]

根据Microsoft 2 的这篇文章， ID 是 MU（Microsoft Update）和 Store。WSUS ID (3DA21691 ....) 没有显示为待处理，也没有密钥可供检查。

组策略设置显示我已禁用与外界的所有连接，因为此系统未连接到 Internet。

最后有证据表明他们没有提取更新，因为 1 月份的更新已获批准且尚未提取。他们还没有算作需要它们，因为机器已经几个月没有登记了。

仍在搜索更多信息以了解系统未连接到 WSUS 服务器的原因。在 1809 更新之后，我没有对防火墙或配置进行任何更改，因此更新显然中断了通信。

2 个回答

Voted

JukEboX · Answer 1 · 2019-04-25T04:08:50+08:00

Best Answer

JukEboX

2019-04-25T04:08:50+08:002019-04-25T04:08:50+08:00

看起来我们的错误报告已提交给修复团队，并且 4 月的更新已经修复了这个问题。

2019 年 4 月 Windows 10 版本 1809 或基于 x64 的系统的累积更新 (KB4493509)

此更新安装后已重新连接我的客户端，并且更新现在从 WSUS 返回。希望这也适用于您的环境。

2

yagmoth555 · Answer 2 · 2019-01-27T06:41:57+08:00

yagmoth555

2019-01-27T06:41:57+08:002019-01-27T06:41:57+08:00

如果您使用的是 WSUS 服务器 3.0 SP2 或更低版本，请确保计算机不强制执行 SHA1 贬值，因为 WSUS 3.0 提供的更新是 SHA1 签名的。WSUS 服务器的修复程序将于 2 月到期。

一些上下文信息； https://support.microsoft.com/en-us/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus

1

如何在 1809 之后将客户端重新连接到 WSUS 导致安装后出现问题

新安装后 postgres 的默认超级用户用户名/密码是什么？

SFTP 使用什么端口？

命令行列出 Windows Active Directory 组中的用户？

什么是 Pem 文件，它与其他 OpenSSL 生成的密钥文件格式有何不同？

如何确定bash变量是否为空？

如何在 1809 之后将客户端重新连接到 WSUS 导致安装后出现问题

2 个回答

相关问题