M
Mike-EEE
So I recently got nagged to restart my 2016 server after a new update. Now I when I refresh my servers, I get the following warning:
Warning HOST : Configuration refresh message: The system cannot access one or more event logs because of insufficient access rights, file corruption, or other reasons. For more information, see the Operational channel in the ServerManager-ManagementProvider error log on the target server. 8/30/2017 3:32:05 AM
Looking in that log, I see these warnings:
Warning 8/30/2017 3:37:14 AM ServerManager-ManagementProvider 46 Get server inventory task
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Admin [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Analytic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Debug [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Operational [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-EventLog/Analytic [hResult = Function failed during execution., hLastResult = Configuration error.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-EventLog/Debug [hResult = Function failed during execution., hLastResult = Configuration error.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-SPB-HIDI2C/Analytic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-WCN-Config-Registrar/Diagnostic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Setup [hResult = Function failed during execution., hLastResult = Configuration error.].
I am also seeing these warnings in my Security log:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: Machine$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Type: 5
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: -
Account Domain: -
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xC0000073
Sub Status: 0xC0000073
Process Information:
Caller Process ID: 0x600
Caller Process Name: C:\Windows\System32\svchost.exe
Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
------------------------------------
I thought updates were supposed to make installs better. Does anyone over there actually do any testing before sending these things out?
Continue reading...
Warning HOST : Configuration refresh message: The system cannot access one or more event logs because of insufficient access rights, file corruption, or other reasons. For more information, see the Operational channel in the ServerManager-ManagementProvider error log on the target server. 8/30/2017 3:32:05 AM
Looking in that log, I see these warnings:
Warning 8/30/2017 3:37:14 AM ServerManager-ManagementProvider 46 Get server inventory task
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Admin [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Analytic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Debug [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Generic failure querying the localized name for channel: Microsoft-Windows-DeviceSetupManager/Operational [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-EventLog/Analytic [hResult = Function failed during execution., hLastResult = Configuration error.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-EventLog/Debug [hResult = Function failed during execution., hLastResult = Configuration error.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-SPB-HIDI2C/Analytic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Microsoft-Windows-WCN-Config-Registrar/Diagnostic [hResult = Function failed during execution., hLastResult = The system cannot find the file specified.].
Failure opening metadata of the owning provider for channel: Setup [hResult = Function failed during execution., hLastResult = Configuration error.].
I am also seeing these warnings in my Security log:
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: Machine$
Account Domain: WORKGROUP
Logon ID: 0x3E7
Logon Type: 5
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: -
Account Domain: -
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xC0000073
Sub Status: 0xC0000073
Process Information:
Caller Process ID: 0x600
Caller Process Name: C:\Windows\System32\svchost.exe
Network Information:
Workstation Name: -
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
------------------------------------
I thought updates were supposed to make installs better. Does anyone over there actually do any testing before sending these things out?
Continue reading...