Error installing sql server 2019 development on windows 11

Alen Cappelletti 911 Reputation points
2023-01-03T13:51:02.64+00:00

Hi all,

I'm try to install on my last work notebook (windows 11 with last update path and all stuff right) a dev edition of sql server.

All other services are ok (sql browser, analysis service, integration services) but the sql server engine (also with a named instance I tried) I got always an error and service don't start or better the process is not successfull.
Here below logs from windows application... when I try to start it...

I hope in someone advise,
Alen
----

Faulting application name: sqlservr.exe, version: 2019.150.2095.3, time stamp: 0x626c9e72  
Faulting module name: sqllang.dll, version: 2019.150.2095.3, time stamp: 0x626c9f01  
Exception code: 0xc0000005  
Fault offset: 0x0000000000361f85  
Faulting process id: 0x0x3090  
Faulting application start time: 0x0x1D91F792C971D7B  
Faulting application path: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqlservr.exe  
Faulting module path: C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Binn\sqllang.dll  
Report Id: cff6802b-35b2-4037-a37d-3c021c437c1d  
Faulting package full name:   
Faulting package-relative application ID:   
SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,713 questions
0 comments No comments
{count} votes

Accepted answer
  1. Erland Sommarskog 101K Reputation points MVP
    2023-01-03T22:21:21.287+00:00

    Have you checked the SQL Server errorlog?

    If you see a message towards the end about 256 misaligned reads, you are running into a known issue, discussed in this article from Microsoft.

    Else share the errorlog here. You will need to add .txt as a file extension before you can attach it.


1 additional answer

Sort by: Most helpful
  1. Alen Cappelletti 911 Reputation points
    2023-01-04T00:21:45.373+00:00

    The install log....

    2023-01-04 01:05:22.63 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 16 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
    2023-01-04 01:05:22.64 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2023-01-04 01:05:22.64 Server Detected 23370 MB of RAM. This is an informational message; no user action is required.
    2023-01-04 01:05:22.64 Server Using conventional memory in the memory manager.
    2023-01-04 01:05:22.64 Server Page exclusion bitmap is enabled.
    2023-01-04 01:05:22.77 Server Buffer Pool: Allocating 4194304 bytes for 2438416 hashPages.
    2023-01-04 01:05:22.78 Server Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
    2023-01-04 01:05:22.81 Server Buffer pool extension is already disabled. No action is necessary.
    2023-01-04 01:05:22.85 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2023-01-04 01:05:22.87 Server Query Store settings initialized with enabled = 1,
    2023-01-04 01:05:22.88 Server The maximum number of dedicated administrator connections for this instance is '1'
    2023-01-04 01:05:22.88 Server This instance of SQL Server last reported using a process ID of 9720 at 04/01/2023 01:05:17 (local) 04/01/2023 00:05:17 (UTC). This is an informational message only; no user action is required.
    2023-01-04 01:05:22.88 Server Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2023-01-04 01:05:22.89 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.
    2023-01-04 01:05:22.89 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
    2023-01-04 01:05:22.90 Server In-Memory OLTP initialized on standard machine.
    2023-01-04 01:05:22.91 Server [INFO] Created Extended Events session 'hkenginexesession'

    2023-01-04 01:05:22.91 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.
    2023-01-04 01:05:22.92 Server Total Log Writer threads: 2. This is an informational message; no user action is required.
    2023-01-04 01:05:22.93 Server Database Mirroring Transport is disabled in the endpoint configuration.
    2023-01-04 01:05:22.93 Server clwb is selected for pmem flush operation.
    2023-01-04 01:05:22.93 spid10s Warning ******************
    2023-01-04 01:05:22.93 Server Software Usage Metrics is disabled.
    2023-01-04 01:05:22.93 spid10s SQL Server started in single-user mode. This an informational message only. No user action is required.
    2023-01-04 01:05:22.94 spid10s Starting up database 'master'.
    2023-01-04 01:05:22.95 spid10s There have been 256 misaligned log IOs which required falling back to synchronous IO. The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.ALEN2\MSSQL\DATA\master.mdf.
    2023-01-04 01:05:23.04 Server CLR version v4.0.30319 loaded.
    2023-01-04 01:05:23.13 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319.

    I resolved in this way:

    • uninstall all SQL instances
    • modify Register Editor (follow the link above where Eland talk about "256 misaligned") - if instances are installed not operate after the regedit, you have to remove all before
    • reinstall all SQL instances
    • trace flag -T1800 it not necessary to me

    ALEN

    1 person found this answer helpful.
    0 comments No comments