SQL Express Server 2022 wont start.

Malte Boden 20 Reputation points
2023-11-08T11:14:40.2666667+00:00

After installing SQL Express 2022 it cannot be started. Tried to reinstall it, did nothing. After viewing the Errorlog i can see multible errors. Tried to google some errors but found nearly nothing.

What i already tried:

Nothing worked. Please Help.

Error Log-file:

2023-11-08 12:05:14.44 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 Enterprise 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-11-08 12:05:14.44 Server      UTC adjustment: 1:00
2023-11-08 12:05:14.44 Server      (c) Microsoft Corporation.
2023-11-08 12:05:14.45 Server      All rights reserved.
2023-11-08 12:05:14.45 Server      Server process ID is 3528.
2023-11-08 12:05:14.45 Server      System Manufacturer: 'LENOVO', System Model: '20YG003VGE'.
2023-11-08 12:05:14.45 Server      Authentication mode is WINDOWS-ONLY.
2023-11-08 12:05:14.45 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2023-11-08 12:05:14.45 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS'. This is an informational message; no user action is required.
2023-11-08 12:05:14.45 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
	 -T 1800
2023-11-08 12:05:14.45 Server      Command Line Startup Parameters:
	 -s "SQLEXPRESS"
2023-11-08 12:05:14.45 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.
2023-11-08 12:05:14.45 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-11-08 12:05:14.45 Server      Detected 15178 MB of RAM. This is an informational message; no user action is required.
2023-11-08 12:05:14.45 Server      Using conventional memory in the memory manager.
2023-11-08 12:05:14.45 Server      Detected pause instruction latency: 18 cycles.
2023-11-08 12:05:14.45 Server      Page exclusion bitmap is enabled.
2023-11-08 12:05:14.52 Server      Buffer Pool: Allocating 2097152 bytes for 1255737 hashPages.
2023-11-08 12:05:14.53 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-11-08 12:05:14.54 Server      Buffer pool extension is already disabled. No action is necessary.
2023-11-08 12:05:14.56 Server      CPU vectorization level(s) detected:  SSE SSE2 SSE3 SSSE3 SSE41 SSE42 AVX AVX2 POPCNT BMI1 BMI2
2023-11-08 12:05:14.59 Server      Query Store settings initialized with enabled = 1, 
2023-11-08 12:05:14.59 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-11-08 12:05:14.59 Server      This instance of SQL Server last reported using a process ID of 17560 at 08.11.2023 11:47:40 (local) 08.11.2023 10:47:40 (UTC). This is an informational message only; no user action is required.
2023-11-08 12:05:14.59 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.
2023-11-08 12:05:14.60 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-11-08 12:05:14.60 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
2023-11-08 12:05:14.61 Server      In-Memory OLTP initialized on lowend machine.
2023-11-08 12:05:14.62 Server      [INFO] Created Extended Events session 'hkenginexesession'
2023-11-08 12:05:14.62 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-11-08 12:05:14.62 Server      Total Log Writer threads: 2, Node CPUs: 4, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2
2023-11-08 12:05:14.64 Server      clwb is selected for pmem flush operation.
2023-11-08 12:05:14.64 Server      Software Usage Metrics is disabled.
2023-11-08 12:05:14.64 spid26s     Starting up database 'master'.
2023-11-08 12:05:14.66 spid26s     3 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2023-11-08 12:05:14.67 spid26s     0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2023-11-08 12:05:14.71 spid26s     SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2023-11-08 12:05:14.71 spid26s     SQL Server Audit has started the audits. This is an informational message. No user action is required.
2023-11-08 12:05:14.71 spid26s     XE session 'system_health' started.
2023-11-08 12:05:14.72 spid26s     SQL Trace ID 1 was started by login "sa".
2023-11-08 12:05:14.72 Server      CLR version v4.0.30319 loaded.
2023-11-08 12:05:14.72 spid26s     Server name is 'JEN-NB\SQLEXPRESS'. This is an informational message only. No user action is required.
2023-11-08 12:05:14.73 spid26s     Starting up database 'msdb'.
2023-11-08 12:05:14.73 spid31s     Starting up database 'mssqlsystemresource'.
2023-11-08 12:05:14.73 spid26s     Error: 17204, Severity: 16, State: 1.
2023-11-08 12:05:14.73 spid26s     FCB::Open failed: Could not open file D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\MSDBData.mdf for file number 1.  OS error: 3(Das System kann den angegebenen Pfad nicht finden.).
2023-11-08 12:05:14.73 spid26s     Error: 5120, Severity: 16, State: 101.
2023-11-08 12:05:14.73 spid26s     Unable to open the physical file "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\MSDBData.mdf". Operating system error 3: "3(Das System kann den angegebenen Pfad nicht finden.)".
2023-11-08 12:05:14.73 spid26s     Error: 17207, Severity: 16, State: 1.
2023-11-08 12:05:14.73 spid26s     FileMgr::StartLogFiles: Operating system error 2(Das System kann die angegebene Datei nicht finden.) occurred while creating or opening file 'D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\MSDBLog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2023-11-08 12:05:14.74 spid26s     File activation failure. The physical file name "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\MSDBLog.ldf" may be incorrect.
2023-11-08 12:05:14.74 spid31s     The resource database build version is 16.00.1000. This is an informational message only. No user action is required.
2023-11-08 12:05:14.76 spid31s     Starting up database 'model'.
2023-11-08 12:05:14.76 spid31s     Error: 17204, Severity: 16, State: 1.
2023-11-08 12:05:14.76 spid31s     FCB::Open failed: Could not open file D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\model.mdf for file number 1.  OS error: 3(Das System kann den angegebenen Pfad nicht finden.).
2023-11-08 12:05:14.76 spid31s     Error: 5120, Severity: 16, State: 101.
2023-11-08 12:05:14.76 spid31s     Unable to open the physical file "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\model.mdf". Operating system error 3: "3(Das System kann den angegebenen Pfad nicht finden.)".
2023-11-08 12:05:14.76 spid31s     Error: 17207, Severity: 16, State: 1.
2023-11-08 12:05:14.76 spid31s     FileMgr::StartLogFiles: Operating system error 2(Das System kann die angegebene Datei nicht finden.) occurred while creating or opening file 'D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\modellog.ldf'. Diagnose and correct the operating system error, and retry the operation.
2023-11-08 12:05:14.77 spid31s     File activation failure. The physical file name "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\modellog.ldf" may be incorrect.
2023-11-08 12:05:14.77 spid31s     Error: 945, Severity: 14, State: 2.
2023-11-08 12:05:14.77 spid31s     Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.  See the SQL Server errorlog for details.
2023-11-08 12:05:14.77 spid31s     SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

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,082 questions
0 comments No comments
{count} votes

Accepted answer
  1. Erland Sommarskog 103.7K Reputation points MVP
    2023-11-08T22:52:12.1033333+00:00

    Something has gone wrong during the installation. Those funny paths on the D drive are supposed to be replaced by correct paths by Setup, but somehow this did not happen.

    I would recommend that you uninstall the lot and start again. As a preventive action take a look at this article, in case you have one of the disk drives that is causing the issue covered in the article.

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. LiHongMSFT-4306 24,361 Reputation points
    2023-11-09T02:39:35.77+00:00

    Hi @Malte Boden

    Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space.

    Here are some workarounds:

    1. If possible, add more hard drive space either by removing of unnecessary files from hard drive or add new hard drive with larger size.
    2. Check if the database is set to Autogrow on.
    3. Check if the account which is trying to access the database has enough permission to perform operation.
    4. Make sure that .mdf and .ldf file are not marked as read only on operating system file system level.

    Best regards,

    Cosmog Hong


    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".

    Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments