ERRORLOG_1.txtI have bought a new pc with windows 11 . I tried to install sql server 2017/2019 , both didn't worked .
Error with Database Engine services.
Database Engine services failed.
I am unable to install SQL in this windows version . Is it a known bug ?
Is there a way to install it ?
I am attaching the error log.
I am pasting the error here :
Overall summary:
Final result: Failed: see details below
Exit code [Decimal]: -2061893606
Start time: 2023-01-11 09:47:50
End time: 2023-01-11 09:53:37
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name:
Machine processor count: 12
OS version: Microsoft Windows 11 Home [10.0.22621]
OS service pack:
OS region: United States
OS language: English [United Kingdom]
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
Package properties:
Description: Microsoft SQL Server 2017
ProductName: SQL Server 2017
Type: RTM
Version: 14
SPLevel: 0
Installation location: E:\SQL Installation\MSSQL2017\Developer_ENU\x64\setup\
Installation edition: Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$SQL2017
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: TABULAR
ASSVCACCOUNT:
ASSVCPASSWORD:
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS:
ASTELSVCACCT:
ASTELSVCPASSWORD:
ASTELSVCSTARTUPTYPE: 0
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME:
CLTRESULTDIR:
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT:
CLTSVCPASSWORD:
CLTWORKINGDIR:
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20230111_094749\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT:
CTLRSVCPASSWORD:
CTLRUSERS:
ENABLERANU: false
ENU: true
EXTSVCACCOUNT:
EXTSVCPASSWORD:
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME:
FTSVCACCOUNT:
FTSVCPASSWORD:
HELP: false
IACCEPTPYTHONLICENSETERMS: false
IACCEPTROPENLICENSETERMS: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files [x86]\Microsoft SQL Server\
INSTALLSQLDATADIR:
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: SQL2017
INSTANCENAME: SQL2017
ISMASTERSVCACCOUNT: NT AUTHORITY\Network Service
ISMASTERSVCPASSWORD:
ISMASTERSVCPORT: 8391
ISMASTERSVCSSLCERTCN:
ISMASTERSVCSTARTUPTYPE: Automatic
ISMASTERSVCTHUMBPRINT:
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD:
ISSVCSTARTUPTYPE: Automatic
ISTELSVCACCT:
ISTELSVCPASSWORD:
ISTELSVCSTARTUPTYPE: 0
ISWORKERSVCACCOUNT: NT AUTHORITY\Network Service
ISWORKERSVCCERT:
ISWORKERSVCMASTER:
ISWORKERSVCPASSWORD:
ISWORKERSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME:
MATRIXNAME:
MRCACHEDIRECTORY:
NPENABLED: 0
PBDMSSVCACCOUNT:
PBDMSSVCPASSWORD:
PBDMSSVCSTARTUPTYPE: 0
PBENGSVCACCOUNT:
PBENGSVCPASSWORD:
PBENGSVCSTARTUPTYPE: 0
PBPORTRANGE:
PBSCALEOUT: false
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE:
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT:
RSSVCPASSWORD:
RSSVCSTARTUPTYPE: Automatic
SAPWD:
SECURITYMODE:
SQLBACKUPDIR:
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$SQL2017
SQLSVCINSTANTFILEINIT: false
SQLSVCPASSWORD:
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS:
SQLTELSVCACCT: NT Service\SQLTELEMETRY$SQL2017
SQLTELSVCPASSWORD:
SQLTELSVCSTARTUPTYPE: Automatic
SQLTEMPDBDIR:
SQLTEMPDBFILECOUNT: 8
SQLTEMPDBFILEGROWTH: 64
SQLTEMPDBFILESIZE: 8
SQLTEMPDBLOGDIR:
SQLTEMPDBLOGFILEGROWTH: 64
SQLTEMPDBLOGFILESIZE: 8
SQLUSERDBDIR:
SQLUSERDBLOGDIR:
SUPPRESSPRIVACYSTATEMENTNOTICE: false
TCPENABLED: 0
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
USEMICROSOFTUPDATE: false
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20230111_094749\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: //go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=14.0.1000.169&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\140\Setup Bootstrap\Log\20230111_094749\SystemConfigurationCheck_Report.htm
- 2023-01-11T13:55:02.3266667+00:00 Hi @Sharon01 yes, that is a known "bug". Windows 11 uses different block sizes for disc alignment [32k] which aren't supported by SQL Server. BUT there is a work around [//learn.microsoft.com/en-us/troubleshoot/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size or, what also might help... add the traceflag 1800 to the SQL Server startup parameter I hope my answer is helpful to you, Your Bjoern Peters If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!
4 additional answers
- 2023-01-11T11:36:40.35+00:00
Hello @Sharon01 , what edition of SQL Server are you trying to install? you can check the supported OS and SQL Server 2019 editions compatibility matrix here: [//learn.microsoft.com/en-us/sql/sql-server/install/hardware-and-software-requirements-for-installing-sql-server-2019?view=sql-server-2017
operating-system-support
- 2023-01-12T06:50:17.68+00:00
Hi @Sharon01
Is it a known bug ? It is known and discussed in this article. On systems running Windows 11, some new storage devices and device drivers will expose a disk sector size greater than the supported 4-KB sector size. When this occurs, SQL Server will be unable to start due to the unsupported file system as SQL Server currently supports sector storage sizes of 512 bytes and 4 KB. Look for the values
PhysicalBytesPerSectorForAtomicity
andPhysicalBytesPerSectorForPerformance
, returned in bytes, and if they're different, retain the largest one to ascertain the disk sector size. A value of 4096 indicates a sector storage size of 4 KB.Additionally, be aware of the Windows support policy for file system and storage sector size support. For more information, see the Microsoft support policy for 4-KB sector hard drives in Windows article. Best regards, Cosmog Hong
- 2023-06-01T08:18:10.1066667+00:00 The fact that they cannot fix this is beyond me. I cannot install SQL Server 2022 on my windows 11 because of some stupid allocation size, that even after running a hack to change the disk sector size to work like windows 10 it does not work, and the Database Engine Service fails. I tried everything. So, I have to downgrade to windows 10 again to make their stuff work that was designed specifically for their operating system using tools build by the same company! Seriously. It's genuinely time to move over to Linux.
AlexD 6 Reputation points
2023-10-14T21:57:01.1666667+00:00
Is there any known solution to the problem? I have tried everything, including registry modification and traceflag 1800