Yes I do..
Vino's Event Viewer v01c run on Windows 7 in English
Report run at 29/01/2017 9:29:26 PM
Note: All dates below are in the format dd/mm/yyyy
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/01/2017 7:25:40 PM
Type: Error Category: 2
Event: 17120 Source: MSSQL$TEW_SQLEXPRESS
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Log: 'Application' Date/Time: 29/01/2017 7:25:40 PM
Type: Error Category: 2
Event: 17826 Source: MSSQL$TEW_SQLEXPRESS
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
Log: 'Application' Date/Time: 29/01/2017 7:25:40 PM
Type: Error Category: 2
Event: 17182 Source: MSSQL$TEW_SQLEXPRESS
TDSSNIClient initialization failed with error 0x5, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Access is denied.
Log: 'Application' Date/Time: 29/01/2017 7:25:40 PM
Type: Error Category: 2
Event: 17182 Source: MSSQL$TEW_SQLEXPRESS
TDSSNIClient initialization failed with error 0x5, status code 0x51. Reason: Unable to configure MDAC-compatibility Named Pipes protocol pipe name in registry. Access is denied.
Log: 'Application' Date/Time: 29/01/2017 7:25:40 PM
Type: Error Category: 2
Event: 17053 Source: MSSQL$TEW_SQLEXPRESS
UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
Log: 'Application' Date/Time: 29/01/2017 7:25:37 PM
Type: Error Category: 3
Event: 320 Source: DbxSvc
Failed to connect to the driver: (-2147024894) The system cannot find the file specified.
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 4098:44-4098:45 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 4498:57-4498:58 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 1506:32-1506:33 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 1627:54-1627:55 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 5870:15-5870:16 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 10277:23-10277:24 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 8023:36-8023:37 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 7760:72-7760:73 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:55 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 2354:29-2354:30 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:54 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 1483:35-1483:36 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:54 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 15124:39-15124:40 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:54 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 11920:3-11920:4 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:54 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 4005:19-4005:20 in IStream
Log: 'Application' Date/Time: 29/01/2017 7:09:54 PM
Type: Error Category: 0
Event: 17 Source: WNIW
syntax error from 2649:20-2649:21 in IStream
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Warning Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 29/01/2017 7:26:07 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0xC004F074 AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69 Trigger=UserLogon(1)
Log: 'Application' Date/Time: 29/01/2017 6:11:00 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0xC004F074 AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69 Trigger=NetworkAvailable
Log: 'Application' Date/Time: 29/01/2017 6:10:39 PM
Type: Warning Category: 0
Event: 8233 Source: Microsoft-Windows-Security-SPP
The rules engine reported a failed VL activation attempt. Reason:0xC004F074 AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = b322da9c-a2e2-4058-9e4e-f59a6970bd69 Trigger=UserLogon(1)
Log: 'Application' Date/Time: 29/01/2017 6:10:29 PM
Type: Warning Category: 0
Event: 8225 Source: Microsoft-Windows-Security-SPP
The existing scheduler data does not match the expected data. The schedule will be re-evaluated. Reason:0x8007000D
Log: 'Application' Date/Time: 29/01/2017 6:08:35 PM
Type: Warning Category: 0
Event: 2007 Source: Microsoft-Windows-LoadPerf
Cannot repair performance counters for .NET CLR Data service. Reinstall the performance counters manually using the LODCTR tool.
Log: 'Application' Date/Time: 29/01/2017 6:08:35 PM
Type: Warning Category: 0
Event: 2007 Source: Microsoft-Windows-LoadPerf
Cannot repair performance counters for .NET CLR Networking service. Reinstall the performance counters manually using the LODCTR tool.
Log: 'Application' Date/Time: 29/01/2017 6:08:35 PM
Type: Warning Category: 0
Event: 2007 Source: Microsoft-Windows-LoadPerf
Cannot repair performance counters for .NET Data Provider for Oracle service. Reinstall the performance counters manually using the LODCTR tool.
Log: 'Application' Date/Time: 29/01/2017 6:08:35 PM
Type: Warning Category: 0
Event: 2007 Source: Microsoft-Windows-LoadPerf
Cannot repair performance counters for .NET Data Provider for SqlServer service. Reinstall the performance counters manually using the LODCTR tool.
Log: 'Application' Date/Time: 29/01/2017 6:08:35 PM
Type: Warning Category: 0
Event: 2007 Source: Microsoft-Windows-LoadPerf
Cannot repair performance counters for .NETFramework service. Reinstall the performance counters manually using the LODCTR tool.
Log: 'Application' Date/Time: 29/01/2017 5:59:15 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, WsmAgent, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\winrm to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:15 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, WsmAgent, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\winrm to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:13 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_UserStateConfigurationProvider, has been registered in the Windows Management Instrumentation namespace root\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:13 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_UserStateConfigurationProvider, has been registered in the Windows Management Instrumentation namespace root\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:10 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_OfflineFilesConfigurationProvider, has been registered in the Windows Management Instrumentation namespace ROOT\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:10 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_OfflineFilesConfigurationProvider, has been registered in the Windows Management Instrumentation namespace ROOT\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:10 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_OfflineFilesConfigurationProvider, has been registered in the Windows Management Instrumentation namespace ROOT\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:07 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_FolderRedirectionConfiguration, has been registered in the Windows Management Instrumentation namespace root\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:07 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, Win32_FolderRedirectionConfiguration, has been registered in the Windows Management Instrumentation namespace root\CIMV2 to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:07 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
Log: 'Application' Date/Time: 29/01/2017 5:59:07 PM
Type: Warning Category: 0
Event: 63 Source: Microsoft-Windows-WMI
A provider, DSCCoreProviders, has been registered in the Windows Management Instrumentation namespace root\Microsoft\Windows\DesiredStateConfiguration to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.