2015-12-09 15:42:12.10 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64) 
	Feb 20 2014 20:04:26 
	Copyright (c) Microsoft Corporation
	Enterprise Evaluation Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )

2015-12-09 15:42:12.10 Server      UTC adjustment: -5:00
2015-12-09 15:42:12.10 Server      (c) Microsoft Corporation.
2015-12-09 15:42:12.10 Server      All rights reserved.
2015-12-09 15:42:12.10 Server      Server process ID is 9144.
2015-12-09 15:42:12.10 Server      System Manufacturer: 'IBM', System Model: 'System x3950 X6 -[6241AC1]-'.
2015-12-09 15:42:12.10 Server      Authentication mode is MIXED.
2015-12-09 15:42:12.11 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2015-12-09 15:42:12.11 Server      The service account is 'IBMSERV\Administrator'. This is an informational message; no user action is required.
2015-12-09 15:42:12.11 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2015-12-09 15:42:12.11 Server      Command Line Startup Parameters:
	 -c
	 -x
	 -T 3502
	 -T 834
	 -T 661
	 -T 8744
2015-12-09 15:42:12.52 Server      SQL Server detected 8 sockets with 18 cores per socket and 36 logical processors per socket, 288 total logical processors; using 288 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-12-09 15:42:12.52 Server      SQL Server is starting at high priority base (=13). This is an informational message only. No user action is required.
2015-12-09 15:42:12.52 Server      Detected 4194062 MB of RAM. This is an informational message; no user action is required.
2015-12-09 15:42:12.52 Server      Using large pages in the memory manager.
2015-12-09 15:42:12.53 Server      The SQL Server image sqlservr.exe was allocated using the large pages option.
2015-12-09 15:42:12.53 Server      The SQL Server image sqlmin.dll was allocated using the large pages option.
2015-12-09 15:42:12.53 Server      The SQL Server image sqldk.dll was allocated using the large pages option.
2015-12-09 15:42:12.53 Server      SQL Server has been configured for lightweight pooling. This is an informational message; no user action is required.
2015-12-09 15:42:12.53 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.53 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.53 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.53 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.54 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.54 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.54 Server      Large Page Allocated: 32MB 
2015-12-09 15:42:12.54 Server      Large Page Allocated: 32MB 
2015-12-09 15:44:08.08 Server      Default collation: Latin1_General_BIN (us_english 1033)
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 0, processor mask 0x0000000ffffffcff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 1, processor mask 0x0000000fffffffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 2, processor mask 0x0000000ffffffffc. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 3, processor mask 0x0000000fffffffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 4, processor mask 0x0000000fffffffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.08 Server      Processor affinity turned on: node 5, processor mask 0x0000000ffffffffc. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 6, processor mask 0x0000000fffffffff. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 7, processor mask 0x0000000ffffffffc. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 8, processor mask 0x0000000000000300. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 9, processor mask 0x0000000000000003. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 10, processor mask 0x0000000000000003. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.09 Server      Processor affinity turned on: node 11, processor mask 0x0000000000000003. Threads will execute on CPUs per affinity settings. This is an informational message; no user action is required.
2015-12-09 15:44:08.19 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2015-12-09 15:44:08.21 Server      Query Store settings initialized with enabled = 1, 
2015-12-09 15:44:08.28 Server      The maximum number of dedicated administrator connections for this instance is '1'
2015-12-09 15:44:08.28 Server      This instance of SQL Server last reported using a process ID of 7600 at 12/9/2015 2:57:59 PM (local) 12/9/2015 7:57:59 PM (UTC). This is an informational message only; no user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 0: CPU mask: 0x0000000ffffffcff:0 Active CPU mask: 0x0000000ffffffcff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 1: CPU mask: 0x0000000fffffffff:1 Active CPU mask: 0x0000000fffffffff:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 2: CPU mask: 0x0000000ffffffffc:2 Active CPU mask: 0x0000000ffffffffc:2. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 3: CPU mask: 0x0000000fffffffff:3 Active CPU mask: 0x0000000fffffffff:3. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 4: CPU mask: 0x0000000fffffffff:4 Active CPU mask: 0x0000000fffffffff:4. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.29 Server      Node configuration: node 5: CPU mask: 0x0000000ffffffffc:5 Active CPU mask: 0x0000000ffffffffc:5. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 6: CPU mask: 0x0000000fffffffff:6 Active CPU mask: 0x0000000fffffffff:6. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 7: CPU mask: 0x0000000ffffffffc:7 Active CPU mask: 0x0000000ffffffffc:7. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 8: CPU mask: 0x0000000000000300:0 Active CPU mask: 0x0000000000000300:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 9: CPU mask: 0x0000000000000003:2 Active CPU mask: 0x0000000000000003:2. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 10: CPU mask: 0x0000000000000003:5 Active CPU mask: 0x0000000000000003:5. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.30 Server      Node configuration: node 11: CPU mask: 0x0000000000000003:7 Active CPU mask: 0x0000000000000003:7. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2015-12-09 15:44:08.80 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2015-12-09 15:44:08.80 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2015-12-09 15:44:08.99 Server      Software Usage Metrics is disabled.
2015-12-09 15:44:09.02 spid9s      Starting up database 'master'.
2015-12-09 15:44:09.09 spid9s      7 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-12-09 15:44:09.13 spid9s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-12-09 15:44:09.14 spid9s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-12-09 15:44:09.14 spid9s      Ckpt dbid 1 started 
2015-12-09 15:44:09.14 spid9s      About to log Checkpoint begin.
2015-12-09 15:44:09.15 spid9s      Ckpt dbid 1 phase 1 ended (0)
2015-12-09 15:44:09.17 spid9s      About to log Checkpoint end.
2015-12-09 15:44:09.19 spid9s      Ckpt dbid 1 complete
2015-12-09 15:44:09.33 spid9s      Resource governor reconfiguration succeeded.
2015-12-09 15:44:09.33 spid9s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-12-09 15:44:09.33 spid9s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-12-09 15:44:09.40 spid9s      Server name is 'IBMSERV'. This is an informational message only. No user action is required.
2015-12-09 15:44:09.41 spid35s     Starting up database 'tpce'.
2015-12-09 15:44:09.41 spid30s     Starting up database 'mssqlsystemresource'.
2015-12-09 15:44:09.41 spid36s     Starting up database 'msdb'.
2015-12-09 15:44:09.44 spid30s     The resource database build version is 12.00.2000. This is an informational message only. No user action is required.
2015-12-09 15:44:09.47 spid32s     A self-generated certificate was successfully loaded for encryption.
2015-12-09 15:44:09.47 spid32s     Server is listening on [ 10.10.1.1 <ipv4> 1400].
2015-12-09 15:44:09.47 spid32s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2015-12-09 15:44:09.47 spid32s     Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2015-12-09 15:44:09.47 Server      Server is listening on [ 10.10.1.1 <ipv4> 1411].
2015-12-09 15:44:09.47 Server      Server is listening on [ 10.10.1.1 <ipv4> 1410].
2015-12-09 15:44:09.48 Server      SQL Server Network Interfaces initialized listeners on node 0 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000001. This is an informational message only. No user action is required.
2015-12-09 15:44:09.48 Server      Server is listening on [ 10.10.1.1 <ipv4> 1413].
2015-12-09 15:44:09.48 Server      Server is listening on [ 10.10.1.1 <ipv4> 1412].
2015-12-09 15:44:09.48 Server      SQL Server Network Interfaces initialized listeners on node 1 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000002. This is an informational message only. No user action is required.
2015-12-09 15:44:09.48 Server      Server is listening on [ 10.30.1.1 <ipv4> 1431].
2015-12-09 15:44:09.48 Server      Server is listening on [ 10.30.1.1 <ipv4> 1430].
2015-12-09 15:44:09.48 Server      SQL Server Network Interfaces initialized listeners on node 2 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000004. This is an informational message only. No user action is required.
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.30.1.1 <ipv4> 1433].
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.30.1.1 <ipv4> 1432].
2015-12-09 15:44:09.49 Server      SQL Server Network Interfaces initialized listeners on node 3 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000008. This is an informational message only. No user action is required.
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.20.1.1 <ipv4> 1423].
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.20.1.1 <ipv4> 1422].
2015-12-09 15:44:09.49 Server      SQL Server Network Interfaces initialized listeners on node 5 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000020. This is an informational message only. No user action is required.
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.20.1.1 <ipv4> 1421].
2015-12-09 15:44:09.49 Server      Server is listening on [ 10.20.1.1 <ipv4> 1420].
2015-12-09 15:44:09.49 Server      SQL Server Network Interfaces initialized listeners on node 4 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000010. This is an informational message only. No user action is required.
2015-12-09 15:44:09.50 Server      Server is listening on [ 10.40.1.1 <ipv4> 1441].
2015-12-09 15:44:09.50 Server      Server is listening on [ 10.40.1.1 <ipv4> 1440].
2015-12-09 15:44:09.50 Server      SQL Server Network Interfaces initialized listeners on node 6 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000040. This is an informational message only. No user action is required.
2015-12-09 15:44:09.50 Server      Server is listening on [ 10.40.1.1 <ipv4> 1443].
2015-12-09 15:44:09.50 Server      Server is listening on [ 10.40.1.1 <ipv4> 1442].
2015-12-09 15:44:09.51 Server      SQL Server Network Interfaces initialized listeners on node 7 of a multi-node (NUMA) server configuration with node affinity mask 0x0000000000000080. This is an informational message only. No user action is required.
2015-12-09 15:44:09.51 Server      Server is listening on [ ::1 <ipv6> 1434].
2015-12-09 15:44:09.51 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2015-12-09 15:44:09.52 Server      Dedicated admin connection support was established for listening locally on port 1434.
2015-12-09 15:44:09.52 spid32s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2015-12-09 15:44:09.52 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
2015-12-09 15:44:09.53 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/IBMSERV ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.
2015-12-09 15:44:09.55 spid30s     Starting up database 'model'.
2015-12-09 15:44:09.59 spid36s     1 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-12-09 15:44:09.64 spid30s     Clearing tempdb database.
2015-12-09 15:44:09.71 spid9s      0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2015-12-09 15:44:09.72 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.72 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.74 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.74 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.75 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.75 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.76 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.76 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.77 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.77 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.78 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.78 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.78 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.78 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.79 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.79 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.79 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.79 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.80 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.80 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.81 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.81 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.81 spid30s     Ckpt dbid 3 started 
2015-12-09 15:44:09.81 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.81 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.81 spid30s     About to log Checkpoint begin.
2015-12-09 15:44:09.83 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.83 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.83 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.83 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.84 spid30s     Ckpt dbid 3 phase 1 ended (0)
2015-12-09 15:44:09.84 spid30s     About to log Checkpoint end.
2015-12-09 15:44:09.84 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.84 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.84 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.84 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.85 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.85 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.86 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.86 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.86 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.86 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.86 spid30s     Ckpt dbid 3 complete
2015-12-09 15:44:09.87 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.87 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.89 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.89 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.89 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.89 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.90 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.90 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.91 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.91 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.91 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.91 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.92 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.92 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.92 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.92 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.93 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.93 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.93 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.93 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.94 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.94 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.95 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.95 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.95 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.95 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.96 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.96 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.96 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.96 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.97 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.97 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.98 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.98 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:09.99 spid35s     Error: 17053, Severity: 16, State: 1.
2015-12-09 15:44:09.99 spid35s     DoDevIoCtlOut() DeviceIoControl() : Operating system error 87(The parameter is incorrect.) encountered.
2015-12-09 15:44:10.01 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90348 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:44:10.45 spid30s     Starting up database 'tempdb'.
2015-12-09 15:44:30.00 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90365 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:44:50.01 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90364 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:45:10.01 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90330 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:45:30.01 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90308 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:45:48.80 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 90138 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2015-12-09 15:45:50.85 spid35s     Recovery of database 'tpce' (5) is 0% complete (approximately 31376 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:46:10.85 spid35s     Recovery of database 'tpce' (5) is 13% complete (approximately 762 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:46:30.85 spid35s     Recovery of database 'tpce' (5) is 16% complete (approximately 705 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:46:50.85 spid35s     Recovery of database 'tpce' (5) is 19% complete (approximately 670 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:47:10.85 spid35s     Recovery of database 'tpce' (5) is 21% complete (approximately 639 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:47:30.86 spid35s     Recovery of database 'tpce' (5) is 24% complete (approximately 621 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:47:50.86 spid35s     Recovery of database 'tpce' (5) is 26% complete (approximately 602 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:48:10.86 spid35s     Recovery of database 'tpce' (5) is 29% complete (approximately 581 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:48:24.74 spid37s     The Service Broker endpoint is in disabled or stopped state.
2015-12-09 15:48:24.75 spid37s     The Database Mirroring endpoint is in disabled or stopped state.
2015-12-09 15:48:24.79 spid37s     Service Broker manager has started.
2015-12-09 15:48:30.87 spid35s     Recovery of database 'tpce' (5) is 31% complete (approximately 564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:48:50.87 spid35s     Recovery of database 'tpce' (5) is 33% complete (approximately 546 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:49:10.87 spid35s     Recovery of database 'tpce' (5) is 35% complete (approximately 531 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:49:30.87 spid35s     Recovery of database 'tpce' (5) is 38% complete (approximately 514 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:49:50.88 spid35s     Recovery of database 'tpce' (5) is 40% complete (approximately 497 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:50:10.88 spid35s     Recovery of database 'tpce' (5) is 42% complete (approximately 481 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:50:30.88 spid35s     Recovery of database 'tpce' (5) is 44% complete (approximately 465 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:50:50.88 spid35s     Recovery of database 'tpce' (5) is 47% complete (approximately 448 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:51:10.88 spid35s     Recovery of database 'tpce' (5) is 49% complete (approximately 430 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:51:30.89 spid35s     Recovery of database 'tpce' (5) is 51% complete (approximately 413 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:51:50.90 spid35s     Recovery of database 'tpce' (5) is 53% complete (approximately 396 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:52:10.90 spid35s     Recovery of database 'tpce' (5) is 55% complete (approximately 379 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:52:30.90 spid35s     Recovery of database 'tpce' (5) is 57% complete (approximately 360 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:52:50.90 spid35s     Recovery of database 'tpce' (5) is 60% complete (approximately 341 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:53:10.90 spid35s     Recovery of database 'tpce' (5) is 62% complete (approximately 321 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:53:30.90 spid35s     Recovery of database 'tpce' (5) is 64% complete (approximately 301 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:53:50.92 spid35s     Recovery of database 'tpce' (5) is 67% complete (approximately 283 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:54:10.92 spid35s     Recovery of database 'tpce' (5) is 69% complete (approximately 266 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:54:30.92 spid35s     Recovery of database 'tpce' (5) is 71% complete (approximately 248 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:54:50.92 spid35s     Recovery of database 'tpce' (5) is 73% complete (approximately 230 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:55:10.92 spid35s     Recovery of database 'tpce' (5) is 75% complete (approximately 212 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:55:30.94 spid35s     Recovery of database 'tpce' (5) is 77% complete (approximately 194 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:55:50.94 spid35s     Recovery of database 'tpce' (5) is 79% complete (approximately 176 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:56:10.94 spid35s     Recovery of database 'tpce' (5) is 81% complete (approximately 158 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:56:30.94 spid35s     Recovery of database 'tpce' (5) is 84% complete (approximately 139 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:56:50.94 spid35s     Recovery of database 'tpce' (5) is 86% complete (approximately 121 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:57:10.94 spid35s     Recovery of database 'tpce' (5) is 88% complete (approximately 103 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:57:30.94 spid35s     Recovery of database 'tpce' (5) is 90% complete (approximately 84 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:57:50.96 spid35s     Recovery of database 'tpce' (5) is 92% complete (approximately 66 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:58:10.96 spid35s     Recovery of database 'tpce' (5) is 94% complete (approximately 48 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:58:30.96 spid35s     Recovery of database 'tpce' (5) is 96% complete (approximately 30 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:58:50.96 spid35s     Recovery of database 'tpce' (5) is 98% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2015-12-09 15:59:14.60 spid35s     10703347 transactions rolled forward in database 'tpce' (5:0). This is an informational message only. No user action is required.
2015-12-09 15:59:14.91 spid9s      Recovery of database 'tpce' (5) is 84% complete (approximately 165 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2015-12-09 15:59:16.27 spid9s      190 transactions rolled back in database 'tpce' (5:0). This is an informational message only. No user action is required.
2015-12-09 15:59:16.28 spid9s      Recovery is writing a checkpoint in database 'tpce' (5). This is an informational message only. No user action is required.
2015-12-09 15:59:16.31 spid9s      Ckpt dbid 5 started 
2015-12-09 15:59:16.31 spid9s      About to log Checkpoint begin.
2015-12-09 15:59:16.31 spid9s      Ckpt dbid 5 phase 1 ended (0)
2015-12-09 15:59:18.87 spid9s      About to log Checkpoint end.
2015-12-09 15:59:18.87 spid9s      Ckpt dbid 5 complete
2015-12-09 15:59:18.87 spid9s      Recovery completed for database tpce (database ID 5) in 908 second(s) (analysis 98817 ms, redo 798265 ms, undo 1434 ms.) This is an informational message only. No user action is required.
2015-12-09 15:59:18.94 spid9s      Recovery is complete. This is an informational message only. No user action is required.
2015-12-09 16:02:25.04 spid53      DBCC TRACEOFF 652, server process ID (SPID) 53. This is an informational message only; no user action is required.
2015-12-09 16:06:12.74 spid53      DBCC TRACEON 652, server process ID (SPID) 53. This is an informational message only; no user action is required.
2015-12-09 16:28:54.38 spid51      Ckpt dbid 5 started 
2015-12-09 16:28:54.38 spid51      About to log Checkpoint begin.
2015-12-09 16:28:54.38 spid51      Ckpt dbid 5 phase 1 ended (0)
2015-12-09 16:29:20.33 spid51      About to log Checkpoint end.
2015-12-09 16:29:20.33 spid51      Ckpt dbid 5 complete
2015-12-09 16:31:21.13 spid37s     Service Broker manager has shut down.
2015-12-09 16:31:21.13 spid51      Skipping CleanShutdownDB() checkpoint on dbid 5 (tpce) PruId 0 with 0 freedOutcomes.
2015-12-09 16:31:21.25 spid51      Ckpt dbid 4 started 
2015-12-09 16:31:21.25 spid51      About to log Checkpoint begin.
2015-12-09 16:31:21.27 spid51      Ckpt dbid 4 phase 1 ended (0)
2015-12-09 16:32:05.00 spid51      About to log Checkpoint end.
2015-12-09 16:32:05.02 spid51      Ckpt dbid 4 complete
2015-12-09 16:32:05.15 spid51      Skipping CleanShutdownDB() checkpoint on dbid 3 (model) PruId 0 with 0 freedOutcomes.
2015-12-09 16:32:05.27 spid51      Ckpt dbid 1 started 
2015-12-09 16:32:05.28 spid51      About to log Checkpoint begin.
2015-12-09 16:32:05.30 spid51      Ckpt dbid 1 phase 1 ended (0)
2015-12-09 16:32:49.79 spid51      About to log Checkpoint end.
2015-12-09 16:32:49.81 spid51      Ckpt dbid 1 complete
2015-12-09 16:32:49.81 spid51      Server shut down by request from login IBMSERV\Administrator.
