Quantcast
Channel: SQL Server Setup & Upgrade Forum
Viewing all articles
Browse latest Browse all 7701

wait on data base engine recovery handle failed SQL SERVER 2014

$
0
0

I am unable to install SQL Server on my PC. At the end of installation it gives a failure in starting DataBase Engine. When i try to log in it gives a network related instance error.

I tried uninstalling from Add or Remove Program and installed again but again getting same error.

[ERROR LOG]

2015-10-24 07:59:10.94 Server      Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
    Feb 20 2014 20:04:26
    Copyright (c) Microsoft Corporation
    Express Edition (64-bit) on Windows NT 6.3 <X64> (Build 10240: )

2015-10-24 07:59:10.94 Server      UTC adjustment: 5:30
2015-10-24 07:59:10.94 Server      (c) Microsoft Corporation.
2015-10-24 07:59:10.94 Server      All rights reserved.
2015-10-24 07:59:10.94 Server      Server process ID is 1620.
2015-10-24 07:59:10.94 Server      System Manufacturer: 'LENOVO', System Model: '20255'.
2015-10-24 07:59:10.94 Server      Authentication mode is WINDOWS-ONLY.
2015-10-24 07:59:10.94 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-10-24 07:59:10.94 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2015-10-24 07:59:10.94 Server      Registry startup parameters:
     -d C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL12.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-10-24 07:59:10.94 Server      Command Line Startup Parameters:
     -s "SQLEXPRESS"
2015-10-24 07:59:11.31 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2015-10-24 07:59:11.31 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-10-24 07:59:11.31 Server      Detected 7383 MB of RAM. This is an informational message; no user action is required.
2015-10-24 07:59:11.31 Server      Using conventional memory in the memory manager.
2015-10-24 07:59:11.40 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2015-10-24 07:59:11.47 Server      Query Store settings initialized with enabled = 1,
2015-10-24 07:59:11.47 Server      The maximum number of dedicated administrator connections for this instance is '1'
2015-10-24 07:59:11.47 Server      This instance of SQL Server last reported using a process ID of 8028 at 10/24/2015 7:58:59 AM (local) 10/24/2015 2:28:59 AM (UTC). This is an informational message only; no user action is required.
2015-10-24 07:59:11.47 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f: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-10-24 07:59:11.48 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-10-24 07:59:11.51 Server      Software Usage Metrics is disabled.
2015-10-24 07:59:11.51 spid11s     Starting up database 'master'.
2015-10-24 07:59:11.58 Server      CLR version v4.0.30319 loaded.
2015-10-24 07:59:11.62 spid11s     7 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-24 07:59:11.64 spid11s     0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-10-24 07:59:11.64 spid11s     Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2015-10-24 07:59:11.65 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-10-24 07:59:11.72 spid11s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-10-24 07:59:11.72 spid11s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-10-24 07:59:11.76 spid11s     SQL Trace ID 1 was started by login "sa".
2015-10-24 07:59:11.76 spid11s     Server name is 'RISHABH\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-10-24 07:59:11.76 spid15s     Error: 17190, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     Initializing the FallBack certificate failed with error code: 1, state: 20, error number: 0.
2015-10-24 07:59:11.76 spid15s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2015-10-24 07:59:11.76 spid15s     Error: 17182, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2015-10-24 07:59:11.76 spid15s     Error: 17182, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2015-10-24 07:59:11.76 spid15s     Error: 17826, Severity: 18, State: 3.
2015-10-24 07:59:11.76 spid15s     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.
2015-10-24 07:59:11.76 spid15s     Error: 17120, Severity: 16, State: 1.
2015-10-24 07:59:11.76 spid15s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.


Viewing all articles
Browse latest Browse all 7701

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>