Vino's Event Viewer v01c run on Windows XP in English Report run at 16/01/2012 9:50:19 AM Note: All dates below are in the format dd/mm/yyyy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - error Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 15/01/2012 1:50:25 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 13/01/2012 1:50:24 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 11/01/2012 1:50:23 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 09/01/2012 1:50:22 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 07/01/2012 1:50:21 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 05/01/2012 1:50:20 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 03/01/2012 1:50:19 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. Log: 'System' Date/Time: 01/01/2012 8:38:26 PM Type: error Category: 0 Event: 7026 Source: Service Control Manager The following boot-start or system-start driver(s) failed to load: adwarealert ftsata2 SASKUTIL Log: 'System' Date/Time: 01/01/2012 8:38:23 PM Type: error Category: 0 Event: 7023 Source: Service Control Manager The Windows Firewall/Internet Connection Sharing (ICS) service terminated with the following error: The system cannot find the file specified. Log: 'System' Date/Time: 01/01/2012 8:38:23 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The npkcrypt service failed to start due to the following error: The system cannot find the path specified. Log: 'System' Date/Time: 01/01/2012 8:38:23 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The Media Center Extender Service service depends on the SSDP Discovery Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Log: 'System' Date/Time: 01/01/2012 8:38:23 PM Type: error Category: 0 Event: 7003 Source: Service Control Manager The Apple Mobile Device service depends on the following nonexistent service: Tcpip Log: 'System' Date/Time: 01/01/2012 8:38:23 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The avast! Antivirus service failed to start due to the following error: The system cannot find the file specified. Log: 'System' Date/Time: 01/01/2012 8:19:01 PM Type: error Category: 0 Event: 7026 Source: Service Control Manager The following boot-start or system-start driver(s) failed to load: adwarealert ftsata2 SASKUTIL Log: 'System' Date/Time: 01/01/2012 8:18:58 PM Type: error Category: 0 Event: 7023 Source: Service Control Manager The Windows Firewall/Internet Connection Sharing (ICS) service terminated with the following error: The system cannot find the file specified. Log: 'System' Date/Time: 01/01/2012 8:18:58 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The npkcrypt service failed to start due to the following error: The system cannot find the path specified. Log: 'System' Date/Time: 01/01/2012 8:18:58 PM Type: error Category: 0 Event: 7001 Source: Service Control Manager The Media Center Extender Service service depends on the SSDP Discovery Service service which failed to start because of the following error: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. Log: 'System' Date/Time: 01/01/2012 8:18:58 PM Type: error Category: 0 Event: 7003 Source: Service Control Manager The Apple Mobile Device service depends on the following nonexistent service: Tcpip Log: 'System' Date/Time: 01/01/2012 8:18:57 PM Type: error Category: 0 Event: 7000 Source: Service Control Manager The avast! Antivirus service failed to start due to the following error: The system cannot find the file specified. Log: 'System' Date/Time: 01/01/2012 1:50:18 PM Type: error Category: 6 Event: 16 Source: Windows Update Agent Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'System' Log - warning Type ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Log: 'System' Date/Time: 02/01/2012 10:17:32 AM Type: warning Category: 0 Event: 36 Source: W32Time The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized. Log: 'System' Date/Time: 01/01/2012 8:38:26 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 01/01/2012 8:38:19 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 01/01/2012 8:19:01 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 01/01/2012 8:18:55 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 01/01/2012 3:22:22 AM Type: warning Category: 0 Event: 36 Source: W32Time The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized. Log: 'System' Date/Time: 31/12/2011 1:43:16 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 31/12/2011 1:43:10 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 31/12/2011 1:35:26 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 31/12/2011 1:35:20 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 31/12/2011 9:28:05 AM Type: warning Category: 0 Event: 36 Source: W32Time The time service has not been able to synchronize the system time for 49152 seconds because none of the time providers has been able to provide a usable time stamp. The system clock is unsynchronized. Log: 'System' Date/Time: 30/12/2011 7:49:00 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 30/12/2011 7:48:53 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 30/12/2011 5:58:41 PM Type: warning Category: 0 Event: 20027 Source: Rasman Remote Access Connection Manager failed to start because NDISWAN could not be opened. Log: 'System' Date/Time: 30/12/2011 5:58:36 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 30/12/2011 1:31:19 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 30/12/2011 1:27:20 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 30/12/2011 1:19:42 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 30/12/2011 11:16:43 AM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available. Log: 'System' Date/Time: 29/12/2011 11:34:51 PM Type: warning Category: 0 Event: 39 Source: W32Time The time service is unable to register for network configuration change events. This may occur when TCP/IP is not correctly configured. The time service will be unable to sync time from network providers, but will still use locally installed hardware provdiers, if any are available.