Share via

SQL Server 2022 fails installation

David Float 0 Reputation points
2024-03-23T09:33:55.9033333+00:00

Hello i downloaded the express version of SQL server 2022 and i tried both installation basic and custom.Every time the installation stucks at sqlenginedbstartconfigaction_install_configrc_cpu64 and the database engine doesnt install.

The error log is this :

2024-03-22 16:08:48.59 Server Microsoft SQL Server 2022 (RTM) - 16.0.1000.6 (X64) 

Oct  8 2022 05:58:25 

Copyright (C) 2022 Microsoft Corporation

Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22631: ) (Hypervisor)

2024-03-22 16:08:48.60 Server UTC adjustment: 2:00

2024-03-22 16:08:48.60 Server (c) Microsoft Corporation.

2024-03-22 16:08:48.60 Server All rights reserved.

2024-03-22 16:08:48.60 Server Server process ID is 6620.

2024-03-22 16:08:48.60 Server System Manufacturer: 'ASUS', System Model: 'System Product Name'.

2024-03-22 16:08:48.60 Server Authentication mode is WINDOWS-ONLY.

2024-03-22 16:08:48.60 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Log\ERRORLOG'.

2024-03-22 16:08:48.60 Server The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.

2024-03-22 16:08:48.60 Server Registry startup parameters: 

 -d C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\DATA\master.mdf

 -e C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Log\ERRORLOG

 -l C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\DATA\mastlog.ldf

2024-03-22 16:08:48.60 Server Command Line Startup Parameters:

 -s "SQLEXPRESS"

 -m "SqlSetup"

 -Q

 -q "Latin1_General_CI_AS"

 -T 4022

 -T 4010

 -T 3659

 -T 3610

 -T 8015

 -d "C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Template Data\master.mdf"

 -l "C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Template Data\mastlog.ldf"

2024-03-22 16:08:48.60 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2024-03-22 16:08:48.60 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2024-03-22 16:08:48.60 Server Detected 31893 MB of RAM. This is an informational message; no user action is required.

2024-03-22 16:08:48.60 Server Using conventional memory in the memory manager.

2024-03-22 16:08:48.60 Server Detected pause instruction latency: 44 cycles.

2024-03-22 16:08:48.60 Server Spin divider value used: 1

2024-03-22 16:08:48.60 Server Page exclusion bitmap is enabled.

2024-03-22 16:08:48.66 Server Buffer Pool: Allocating 4194304 bytes for 3199356 hashPages.

2024-03-22 16:08:48.67 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)

2024-03-22 16:08:48.68 Server Buffer pool extension is already disabled. No action is necessary.

2024-03-22 16:08:48.69 Server CPU vectorization level(s) detected: SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2 AVX512 (F CD BW DQ VL IFMA VBMI VBMI2 VNNI BITALG VPOQCNTDQ BF16)

2024-03-22 16:08:48.69 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.

2024-03-22 16:08:48.70 Server Query Store settings initialized with enabled = 1,

2024-03-22 16:08:48.70 Server The maximum number of dedicated administrator connections for this instance is '1'

2024-03-22 16:08:48.70 Server This instance of SQL Server last reported using a process ID of 10888 at 22/03/2024 16:05:45 (local) 22/03/2024 14:05:45 (UTC). This is an informational message only; no user action is required.

2024-03-22 16:08:48.70 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2024-03-22 16:08:48.71 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.

2024-03-22 16:08:48.71 Server Lock partitioning is enabled. This is an informational message only. No user action is required.

2024-03-22 16:08:48.71 Server In-Memory OLTP initialized on standard machine.

2024-03-22 16:08:48.72 Server [INFO] Created Extended Events session 'hkenginexesession'

2024-03-22 16:08:48.72 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.

2024-03-22 16:08:48.72 Server Total Log Writer threads: 2, Node CPUs: 4, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2

2024-03-22 16:08:48.72 Server Database Mirroring Transport is disabled in the endpoint configuration.

2024-03-22 16:08:48.72 Server clwb is selected for pmem flush operation.

2024-03-22 16:08:48.72 Server Software Usage Metrics is disabled.

2024-03-22 16:08:48.72 spid26s Warning ******************

2024-03-22 16:08:48.72 spid26s SQL Server started in single-user mode. This an informational message only. No user action is required.

2024-03-22 16:08:48.73 spid26s Starting up database 'master'.

2024-03-22 16:08:48.73 spid26s 2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.73 spid26s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.76 spid26s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2024-03-22 16:08:48.76 spid26s SQL Server Audit has started the audits. This is an informational message. No user action is required.

2024-03-22 16:08:48.76 spid26s XE session 'system_health' started.

2024-03-22 16:08:48.76 spid26s SQL Trace ID 1 was started by login "sa".

2024-03-22 16:08:48.76 spid26s Server name is 'David\SQLEXPRESS'. This is an informational message only. No user action is required.

2024-03-22 16:08:48.77 spid26s Starting up database 'msdb'.

2024-03-22 16:08:48.77 spid31s Starting up database 'mssqlsystemresource'.

2024-03-22 16:08:48.77 spid31s The resource database build version is 16.00.1000. This is an informational message only. No user action is required.

2024-03-22 16:08:48.78 spid26s 24 transactions rolled forward in database 'msdb' (4:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.78 spid31s Starting up database 'model'.

2024-03-22 16:08:48.78 spid26s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.78 spid26s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.

2024-03-22 16:08:48.78 spid26s Converting database 'msdb' from version 950 to the current version 957.

2024-03-22 16:08:48.78 spid26s Database 'msdb' running the upgrade step from version 950 to version 951.

2024-03-22 16:08:48.79 spid26s Database 'msdb' running the upgrade step from version 951 to version 952.

2024-03-22 16:08:48.79 spid26s Database 'msdb' running the upgrade step from version 952 to version 953.

2024-03-22 16:08:48.79 spid31s 26 transactions rolled forward in database 'model' (3:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.79 spid26s Database 'msdb' running the upgrade step from version 953 to version 954.

2024-03-22 16:08:48.79 spid31s 0 transactions rolled back in database 'model' (3:0). This is an informational message only. No user action is required.

2024-03-22 16:08:48.79 spid31s Recovery is writing a checkpoint in database 'model' (3). This is an informational message only. No user action is required.

2024-03-22 16:08:48.79 spid26s Database 'msdb' running the upgrade step from version 954 to version 955.

2024-03-22 16:08:48.79 spid26s Database 'msdb' running the upgrade step from version 955 to version 956.

2024-03-22 16:08:48.79 spid31s Converting database 'model' from version 952 to the current version 957.

2024-03-22 16:08:48.79 spid31s Database 'model' running the upgrade step from version 952 to version 953.

2024-03-22 16:08:48.79 spid31s Database 'model' running the upgrade step from version 953 to version 954.

2024-03-22 16:08:48.79 spid31s Database 'model' running the upgrade step from version 954 to version 955.

2024-03-22 16:08:48.79 spid31s Database 'model' running the upgrade step from version 955 to version 956.

2024-03-22 16:08:48.80 spid26s Database 'msdb' running the upgrade step from version 956 to version 957.

2024-03-22 16:08:48.80 spid31s Database 'model' running the upgrade step from version 956 to version 957.

2024-03-22 16:08:48.80 spid31s Clearing tempdb database.

2024-03-22 16:08:48.81 spid34s Error: 17190, Severity: 16, State: 1.

2024-03-22 16:08:48.81 spid34s Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 0.

2024-03-22 16:08:48.81 spid34s Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.

2024-03-22 16:08:48.81 spid34s Error: 17182, Severity: 16, State: 1.

2024-03-22 16:08:48.81 spid34s TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.

2024-03-22 16:08:48.81 spid34s Error: 17182, Severity: 16, State: 1.

2024-03-22 16:08:48.81 spid34s 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.

2024-03-22 16:08:48.81 spid34s Error: 17826, Severity: 18, State: 3.

2024-03-22 16:08:48.81 spid34s 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.

2024-03-22 16:08:48.81 spid34s Error: 17120, Severity: 16, State: 1.

2024-03-22 16:08:48.81 spid34s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
13,361 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thameur-BOURBITA 32,636 Reputation points
    2024-03-23T11:02:57.1166667+00:00

    Hi @David Float

    It seems a issue on certificate on this SQL server.

    Check if there is a certifiacte alreday existe on SQL server and tryto take a look at this link , it may help you :

    How can I give SQL Server permission to read my SSL Key?

    Please don't forget to accept helpful answer

    1 person found this answer helpful.
    0 comments
  2. Vinodh247 13,801 Reputation points
    2024-03-23T11:04:27.54+00:00

    Hi David Float,

    Thanks for reaching out to Microsoft Q&A.

    SSL Certificate error, please follow the below link. This fix with self-signed certificate will allow SSL encryption to be established even without an externally issued certificate.

    https://learn.microsoft.com/en-us/troubleshoot/sql/database-engine/startup-shutdown/service-cannot-start

    Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.

    0 comments
  3. MikeyQiaoMSFT-0444 2,000 Reputation points
    2024-03-25T08:42:07.76+00:00

    Hi @David Float

     

    The above issue may be caused by two types of reasons:

    1. An invalid certificate.
    2. SQL Server is unable to access the specified certificate.

     

    Configure SQL Server to use a self-signed certificate:

    1.Open the Registry Editor and navigate to the following registry key (the registry path may vary slightly depending on the instance number):

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Certificate

    2.Clear the value of the Certificate.

    3.Open the Microsoft Management Console (MMC) and add the Certificate Management console. Delete all certificates in both the Local Computer certificate store and the Current User certificate store that have a subject field that matches the server hostname (before deleting, you may want to export the certificates as a backup for future use).

     

    This should allow SQL Server to use a self-generated certificate in most cases.

     

     

    Creating a self-signed certificate for SQL Server:

    You can use the SelfSSL tool (if IIS is installed on your machine) to create a self-signed certificate for SQL Server.

    Here are the steps:

    1. Open the command prompt and type the following command, replacing <FQDN> with the actual fully qualified domain name of your SQL Server host:

    selfssl.exe /N:CN=<FQDN> /K:1024 /V:7 /S:1 /P:442 /T

    1. You will be prompted with "Do you want to replace the SSL settings for site 1 (Y/N)". Type "Y" to install the certificate to the local Certificate store.

     

    l  If IIS is not installed on your machine, you can use the makecert tool from the .NET SDK to create a self-signed certificate. Here are the steps:

    1. Use the makecert tool to generate a .pvk and .cer file:

    makecert -r -pe -sv c:\test.pvk -n "CN=<FQDN>" -b 01/01/2000 -e 01/01/2036 -eku 1.3.6.1.5.5.7.3.1 -ss my -sr localMachine -sky exchange -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 c:\test.cer

    1. Use the pvk2pfx tool to generate a .pfx file:

    pvk2pfx.exe -pvk c:\test.pvk -spc c:\test.cer -pfx c:\test.pfx -po <password>

     

    Tip:Replace <FQDN> with the actual fully qualified domain name of your SQL Server host, and replace <password> with the actual password you want to use. After obtaining the certificate, you need to install it to the certificate store (either local computer or current user store) under the Personal and "Trusted Root Certification Authorities" directories.

     

     

    To configure the certificate, you can use the Certificate registry key value. Here are the steps:

    1. Open the certificate and copy its thumbprint.
    2. If the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\Certificate key doesn't exist, create it manually. For SQL Server 2005 and later versions,

    the key value type is string.

    1. For SQL Server 2005 and later versions, remove all spaces from the thumbprint and copy it to the certificate key value.

     

    To check the certificate, you can refer to Microsoft's documentation on certificate requirements for SQL Server. Certificate requirements for SQL Server - SQL Server | Microsoft Learn

     

    Best regards,

    Mikey Qiao

     

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    0 comments