i am installing sql 2012 and getting error wait on database engine handle recovery failed. i changed the credentials to "NT Authority\NETWORK SERVICE" but getting same error.
logs attached below :
-T 8015
-d "C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Template Data\master.mdf"
-l "C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Template Data\mastlog.ldf"
2019-03-22 16:23:29.98 Server SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2019-03-22 16:23:29.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2019-03-22 16:23:29.98 Server Detected 16383 MB of RAM. This is an informational message; no user action is required.
2019-03-22 16:23:29.98 Server Using conventional memory in the memory manager.
2019-03-22 16:23:30.28 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2019-03-22 16:23:30.40 Server Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2019-03-22 16:23:30.56 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.
2019-03-22 16:23:30.58 Server Database Mirroring Transport is disabled in the endpoint configuration.
2019-03-22 16:23:30.58 Server Software Usage Metrics is disabled.
2019-03-22 16:23:30.59 spid7s Warning ******************
2019-03-22 16:23:30.61 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2019-03-22 16:23:30.62 spid7s Starting up database 'master'.
2019-03-22 16:23:30.65 Server CLR version v4.0.30319 loaded.
2019-03-22 16:23:31.04 spid7s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2019-03-22 16:23:31.05 spid7s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2019-03-22 16:23:31.12 spid7s SQL Trace ID 1 was started by login "sa".
2019-03-22 16:23:31.14 spid7s Server name is 'TDL-EQ-SYSTEM\UBL'. This is an informational message only. No user action is required.
2019-03-22 16:23:31.18 spid11s Password policy update was successful.
2019-03-22 16:23:31.18 spid7s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.UBL\MSSQL\Binn\ftimport.dll'.
2019-03-22 16:23:31.18 spid11s Error: 26011, Severity: 16, State: 1.
2019-03-22 16:23:31.18 spid11s The server was unable to initialize encryption because of a problem with a security library. The security library may be missing. Verify that security.dll exists on the system.
2019-03-22 16:23:31.19 spid7s Starting up database 'msdb'.
2019-03-22 16:23:31.19 spid9s Starting up database 'mssqlsystemresource'.
2019-03-22 16:23:31.22 spid11s Error: 17182, Severity: 16, State: 1.
2019-03-22 16:23:31.22 spid11s TDSSNIClient initialization failed with error 0x139f, status code 0x80. Reason: Unable to initialize SSL support. The group or resource is not in the correct state to perform the requested operation.
2019-03-22 16:23:31.22 spid11s Error: 17182, Severity: 16, State: 1.
2019-03-22 16:23:31.22 spid11s TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct
state to perform the requested operation.
2019-03-22 16:23:31.23 spid11s Error: 17826, Severity: 18, State: 3.
2019-03-22 16:23:31.23 spid11s 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.
2019-03-22 16:23:31.23 spid11s Error: 17120, Severity: 16, State: 1.
2019-03-22 16:23:31.23 spid11s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.