حل مشكلة خطأ تنصيب sqlserver

The “Wait on the Database Engine recovery handle” error during SQL Server 2014 installation on Windows 11 typically indicates that SQL Server failed to start during the setup process. This usually stems from issues with the SQL Server service account or a compatibility issue with the disk drive’s sector size on Windows 11. To resolve this, review the SQL Server error logs, check the disk sector size, and potentially adjust the service account or use a trace flag. 

Troubleshooting Steps:

1. 1. Check SQL Server Error Logs:
   • The primary location for troubleshooting is the SQL Server error log, typically found at C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\LOG\ERRORLOG for SQL Server 2014. 
   • Review the error log for specific error messages that can pinpoint the cause of the failure. 
     • 2. Verify Disk Sector Size:
       • Windows 11, with certain NVMe drives, can report a disk sector size greater than the 4KB that SQL Server supports. 
         • Use the command fsutil fsinfo sectorinfo <volume pathname> (e.g., fsutil fsinfo sectorinfo C:) to check the physical sector size reported by the drive. 
         • If PhysicalBytesPerSectorForAtomicity is greater than 4096, it’s likely the cause of the error. 
     • 3. Adjust SQL Server Service Account:
       • During installation, the service account used for the SQL Server Database Engine can sometimes cause this error. 
       • Ensure the selected account has sufficient privileges. 
       • Consider using the NT AUTHORITY\SYSTEM (local system account) or NT AUTHORITY\NETWORK SERVICE accounts during installation. 
       • You can modify this setting in SQL Server Configuration Manager after installation. 
     • 4. Consider Trace Flags or Registry Modifications:
       • If the issue is due to the disk sector size, a trace flag (-T8024) or a registry modification might be necessary. 
       • For registry modification, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device and add a Multi-String value named ForcedPhysicalSectorSizeInBytes with the value * 4095. 
       • Restart the computer after making registry changes. 
2. 5. Repair or Reinstall SQL Server:
   • If the error persists after troubleshooting, try repairing the existing SQL Server installation through the installation media. 
   • If repair doesn’t work, uninstall SQL Server completely (including registry entries) and reinstall it. 

Example:

Let’s say your error log indicates a problem related to the service account. You can try these steps:

1. Open SQL Server Configuration Manager: Search for and open it. 
2. Navigate to SQL Server Services: Locate the SQL Server instance. 
3. Change the Startup Type: Right-click the service, go to Properties, and change the Startup Type to Manual or Disabled. 
4. Modify Service Account: Go to the Log On tab and change the account to a suitable one like NT AUTHORITY\SYSTEM or NT AUTHORITY\NETWORK SERVICE. 
5. Start the service: Start the SQL Server service manually. 
6. Reinstall/Repair: If the issue persists, uninstall and reinstall, or try repairing the installation. 

Check Sector Size:

Open Command Prompt as an administrator and run fsutil fsinfo sectorinfo C: (replace C: with the drive where you are installing SQL Server) to check the sector size.

If the issue is due to the disk sector size, a trace flag (-T8024) or a registry modification might be necessary.
For registry modification, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device and add a Multi-String value named ForcedPhysicalSectorSizeInBytes with the value * 4095.
Restart the computer after making registry changes.