Forum Discussion
SQL2022 installation failed in Win Server2022 with code 0x851A001A
Hello,
SQL2022 installation failed under MS Windows Server 2022 Standard (10.0.20348) with error code 0x851A001A.
Follow MS Troubleshooting "Troubleshoot errors related to system disk sector size greater than 4 KB" wasn´t helpful.
Thank you in advance for help.
Screenshot of error and info attached:
we got the same error when we were upgrading our 2016 environment to 2022.
Are you upgrading any database?
In our case we copied SSISDB from old(2016)to new(2022). It was looking for enough permissions to upgrade SSISDB from 2016 to 2022, which were not present. If you check the installation log, it clearly specifies what's the issue is?
After reading the log, granted enough permissions to SSISDB system user "##MS_SSISServerCleanupJobUser##".
The installation/patch/cumulative update completed successfully.
Hope that helps.with error code 0x851A001A.
The error code is useless.
Instead do what the error message clearly says:
Viewing the SQL Server Error Log - SQL Server | Microsoft Learn for more details.
Not helpful answer.
This error happened (for us) in December 2024, more users on different forums reported it.
MS published first official info about it on 10th January 2025, but for us wasn´t helpful.
What we did
- Lot of reading and testing (for every error message from SQL error log file).
- MS published on 10th January this year troubleshooting "Troubleshoot errors related to system disk sector size greater than 4 KB" wasn´t helpful" (some description in origin message).
- Here reported what we did by MS troubleshooting, but wasn´t helpful (with our paramaters + inserted regedit value "* 4095").
- More times (in this topic) attached SQL error log file, but wasn´t approved and published (sensitive content was deleted).
- More times (in this topic) - when SQL error log file wasn´t published - content of sql error log file inserted (sensitive content again deleted) in blockquote, but again not approved and not published (don´t know the reason).
Assuming you're installing your database files on C:\, this is indeed strange.
Are you at liberty to share your summary log?Content of summary log shared in quotation marks, but for unknown reason not approved (sensitive data deleted).
