This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 6%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
I'm having problems installing SQL Server 2022 -Express edition, When almost finished, I get the following error message.
Unable to install SQL Server (setup.exe)
Exit code (Decimal): -2068119551 Error description: The target principal name is incorrect. Cannot generate SSPI context.
Here I attach the picture of error message.
In the folder listed in the screenshot you find numerous log files. The ones that is of most interest are summary.txt and detail.txt. Feel free to upload them here.
I see this:
(20) 2024-03-05 21:36:32 Slp: File 'C:\Program Files (x86)\Microsoft SQL Server\160\Shared\sqlmgmprovider.mof' not found! (01) 2024-03-05 21:36:32 Slp: Sco: Compile operation for mof file C:\Program Files (x86)\Microsoft SQL Server\160\Shared\sqlmgmprovider.mof failed. Exit code 1 (01) 2024-03-05 21:36:32 Slp: Configuration action failed for feature CommonFiles during timing ConfigNonRC and scenario ConfigNonRC. (01) 2024-03-05 21:36:32 Slp: The MOF compiler could not connect with the WMI server. This is either because of a semantic error such as an incompatibility with the existing WMI repository or an actual error such as the failure of the WMI server to start.
Which is not the same error as in your original post.
I can also tell by the timestamp that you made a new attempt today. Of course, that is quite natural to do. However, it seems that when people make new attempts after failures, they run into new errors. Possibly because they performed some random cleanups in between which made matters worse.
Unfortunately, it is very difficult to troubleshoot a machine I don't have access to, and this is not a situation I have run into myself.
I can give two suggestions. One is to give up directly, and create a virtual machine and install SQL Server on the VM. If you have never user VMs before, there is certainly a hurdle.
The other is to try this article: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/. Someone I tried to help found this article, and was eventually able to install SQL Server. Now, unless you manage to address the original reason for the failure, you will come back to that error once you have completed the uninstall entirely. But in this case, share the logs without making a new attempt.
I see that you also seem to have SQL 2019 installed. Is you SQL 2019 instance running properly?
Yes i have installed, and its running good. But i need 2022 version for more features.
But i need 2022 version for more features.
That's understandable.
I think going the VM route is the best for you. If you try the uninstall steps in the article I suggested, you may mess up your SQL 2019 instance, and that would make matters worse.
View and Read SQL Server Setup Log Files for more details.