SQL SERVER 2022 INSTALL FAILING File activation error on a drive that has never existed on my pc. File activation failure. The physical file name "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\modellog.ldf"

Question

SQL SERVER 2022 INSTALL FAILING File activation error on a drive that has never existed on my pc. File activation failure. The physical file name "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\modellog.ldf"

kevin miller 0

This is definitely a weird issue. Let me setup the scenario. Just bought a new CyberPowerPC with a AMD Ryzen 5 5500, 3600 mhz, 6 core(s) , 12 logical processors. My issue is with installing SQL server 2022 developer's edition. Checking the error log I got the following errors. My pc has never had a d drive and it is attempting to access files on the d drive. If anyone has any ideas it would be greatly appreciated.

Error:

Total Log Writer threads: 2, Node CPUs: 6, Nodes: 1, Log Writer threads per CPU: 1, Log Writer threads per Node: 2

2025-07-05 13:38:47.05 Server Database Mirroring Transport is disabled in the endpoint configuration.

2025-07-05 13:38:47.05 Server clwb is selected for pmem flush operation.

2025-07-05 13:38:47.05 spid34s Warning ******************

2025-07-05 13:38:47.05 spid34s SQL Server started in single-user mode. This an informational message only. No user action is required.

2025-07-05 13:38:47.05 Server Software Usage Metrics is disabled.

2025-07-05 13:38:47.05 spid34s Starting up database 'master'.

2025-07-05 13:38:47.10 spid34s Setup step is FORCE copying system data file 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\Binn\Templates\model_replicatedmaster.mdf' to 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\DATA\model_replicatedmaster.mdf'.

2025-07-05 13:38:47.10 spid39s Starting up database 'mssqlsystemresource'.

2025-07-05 13:38:47.10 spid34s Setup step is FORCE copying system data file 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\Binn\Templates\model_replicatedmaster.ldf' to 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\DATA\model_replicatedmaster.ldf'.

2025-07-05 13:38:47.10 spid34s Setup step is FORCE copying system data file 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\Binn\Templates\model_msdbdata.mdf' to 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\DATA\model_msdbdata.mdf'.

2025-07-05 13:38:47.10 spid39s The resource database build version is 16.00.1135. This is an informational message only. No user action is required.

2025-07-05 13:38:47.11 spid34s Setup step is FORCE copying system data file 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\Binn\Templates\model_msdblog.ldf' to 'C:\Program Files\Microsoft SQL Server\MSSQL16.KEVBINGA\MSSQL\DATA\model_msdblog.ldf'.

2025-07-05 13:38:47.11 spid34s Starting up database 'model_replicatedmaster'.

2025-07-05 13:38:47.12 spid39s Starting up database 'model'.

2025-07-05 13:38:47.12 spid39s Error: 17204, Severity: 16, State: 1.

2025-07-05 13:38:47.12 spid39s 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(The system cannot find the path specified.).

2025-07-05 13:38:47.12 spid39s Error: 5120, Severity: 16, State: 101.

2025-07-05 13:38:47.12 spid39s 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(The system cannot find the path specified.)".

2025-07-05 13:38:47.12 spid39s Error: 17207, Severity: 16, State: 1.

2025-07-05 13:38:47.12 spid39s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) 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.

2025-07-05 13:38:47.12 spid39s 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.

2025-07-05 13:38:47.12 spid39s Error: 945, Severity: 14, State: 2.

2025-07-05 13:38:47.12 spid39s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.

Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T20:35:40.1766667+00:00

I've seen instances of these funny error messages before, but it was a while, so I need to job my memory. Can you zip all ERRORLOG files and upload them? Also, can you attach the file detail.txt from the most recent folder in C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log?
kevin miller 0 Reputation points

2025-07-05T20:50:17.18+00:00

kay I have uploaded the files you requested. Just to add a note... this seems to be an issue with SQL2022 because I just installed SQL2019 DEV edition with no issues. I have made a few modifications, but the errors presented are the most recent
Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T20:53:20.79+00:00

It seems that you failed to attach the files. Or at least, I can't see any.

I don't think this is an issue with SQL 2022 per se, because I've seen this error with older versions of SQL Server as well.
kevin miller 0 Reputation points

2025-07-05T22:11:24.5766667+00:00

Not sure what you mean by attaching the files? This is a clean install of this version and the log has an error with opening system databases.
Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T22:16:01.1633333+00:00

You would attach the files I asked for to a post to this forum, so that we can take a look at them. You said you had uploaded them, but they are not visible here.

To attach a file, use this button:
kevin miller 0 Reputation points

2025-07-05T22:38:09.2+00:00

Apologies I was sure I attached them.Detail.txt ERRORLOG.txt The file size limit is very small so to do an additional post
kevin miller 0 Reputation points

2025-07-05T23:01:05.99+00:00

Detail.txt
kevin miller 0 Reputation points

2025-07-06T01:20:35.97+00:00

ERRORLOG.txt ERRORLOGzip.txt the errorlogzip.txt is a zip file. you can just rename it after downloading or before viewing. Sorry for the delay.

1 answer

Your answer

Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T20:35:40.1766667+00:00

I've seen instances of these funny error messages before, but it was a while, so I need to job my memory. Can you zip all ERRORLOG files and upload them? Also, can you attach the file detail.txt from the most recent folder in C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log?
kevin miller 0 Reputation points

2025-07-05T20:50:17.18+00:00

kay I have uploaded the files you requested. Just to add a note... this seems to be an issue with SQL2022 because I just installed SQL2019 DEV edition with no issues. I have made a few modifications, but the errors presented are the most recent
Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T20:53:20.79+00:00

It seems that you failed to attach the files. Or at least, I can't see any.

I don't think this is an issue with SQL 2022 per se, because I've seen this error with older versions of SQL Server as well.
kevin miller 0 Reputation points

2025-07-05T22:11:24.5766667+00:00

Not sure what you mean by attaching the files? This is a clean install of this version and the log has an error with opening system databases.
Erland Sommarskog 122K Reputation points MVP Volunteer Moderator

2025-07-05T22:16:01.1633333+00:00

You would attach the files I asked for to a post to this forum, so that we can take a look at them. You said you had uploaded them, but they are not visible here.

To attach a file, use this button:
kevin miller 0 Reputation points

2025-07-05T22:38:09.2+00:00

Apologies I was sure I attached them.Detail.txt ERRORLOG.txt The file size limit is very small so to do an additional post
kevin miller 0 Reputation points

2025-07-05T23:01:05.99+00:00

Detail.txt
kevin miller 0 Reputation points

2025-07-06T01:20:35.97+00:00

ERRORLOG.txt ERRORLOGzip.txt the errorlogzip.txt is a zip file. you can just rename it after downloading or before viewing. Sorry for the delay.

Answer 1

I can see in the errorlog files, that your original problem was due to a known issue where Windows 11 reports a disk-sector size that SQL Server chokes on. It seems that you found that a possible workaround is to apply the trace flag 1800.

Unfortunately, after these multiple attempts Setup gets a little confused. There is one point where Setup starts SQL Server to copy the templates for the system databases in place, and this step also change the locations in the master database. To do this, it starts SQL Server with a number of trace flags. And for your first attempts, it did use those trace flags, but after a while if "forgot" about them. This means that you have a master database with the values from the template, and this where the funny paths on D: come from.

I think the best bet is to uninstall the SQL 2022 instance and start over. This article can be helpful: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/.

You said that you were able to install SQL 2019 successfully. I guess that you applied any of the workarounds in this article before you did anything else, so you started with a clean slate.

Share via

SQL SERVER 2022 INSTALL FAILING File activation error on a drive that has never existed on my pc. File activation failure. The physical file name "D:\dbs\sh\5uj5\1008_054209\cmd\11\obj\x64retail\sql\mkmastr\databases\mkmastr.nativeproj\modellog.ldf"

1 answer

Your answer