How to Install SQL server correctly?

Rita Ewoigbokhan 0

I tried installing sequel server on my pc, I got errors and a summary of the errors.
Feature: Data Quality Client

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 Data Quality Client

Component error code: 0x84D40002

Error description: Unable to open registry key: 'Software\Microsoft\Microsoft SQL Server\160\Bootstrap', registry may be corrupted.

Error help link: https://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=16.0.1000.6&EvtType=0x935EEB66%400xBC33138D%401236%402&EvtType=0x935EEB66%400xBC33138D%401236%402

Erland Sommarskog 112.8K Reputation points

2024-08-24T09:12:40.0766667+00:00

First of all, did this happen on your first attempt to install SQL Server? Or did you make multiple attempts with some attempt to clean up in between? Particularly, if you did, did you delete things in the Windows Registry?

Next, in the folder C:\Program Files\Microsoft SQL Server\160\Setup Bootstrap\Log, you find one folder per installation attempt. The files of most interest are Summary.txt and detail.txt.

Also, have you checked whether this registry key is present? Look under HKEY_LOCAL_MACHINE?

Finally, unless you know that you actually are going to work with Data Quality Services, don't install this component. I never install it myself. It's a very specialised component, and on top of all, it does not work well for what it is intended to.
Rita Ewoigbokhan 0 Reputation points

2024-08-24T09:17:05.7566667+00:00

This is not my first installation trial. Yes I deleted items from the Registry editor, I saw that as a possible solution .. now I am stuck in this mess, I don’t know what to do anymore. Is their any reset factory options that won’t affect my files ? Or any other solution you could proffer
MikeyQiaoMSFT-0444 3,190 Reputation points

2024-08-28T08:45:52.63+00:00

Hello, Rita Ewoigbokhan，how's the issue coming along? We're waiting on your newest update.

1 answer

Erland Sommarskog 112.8K Reputation points

2024-08-24T09:27:23.8633333+00:00

Try this article: https://www.sql-easy.com/learn/how-to-uninstall-sql-server/. I have not tried it myself (never had reason to), but some people have reported success after having followed it. (I actually learnt about the article from someone I tried to help here in the forums.)

The other alternative is create a virtual machine and install SQL Server on the VM. If you have never worked with virtual machines before that is certainly a hurdle. Then again, virtual machines are a tremendous asset in general, so it is good to be able to master that technique.

Finally, also check out this article. It discusses a known issue where Windows 11 reports data for certain disk-drive models that SQL Server may not be able to cope with. This could be the reason why your installation failed initially. If you have one of those disk drives, you will need to apply the workarounds in the article, no matter if you install on a physical machine or a virtual machine.
Please sign in to rate this answer.
Rita Ewoigbokhan 0 Reputation points

2024-08-24T13:15:03.7133333+00:00

These are the error I just during installation , then it says Database engine installation failed

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 star

Error 1

PerfLib 2.0 counter removal failed with exit code 2. Command line: C:\Windows\system32\unlodctr.exe /m:hkengperfctr.xml from directory C:\Program Files\Microsoft SQL Server\160\Shared.

Error 2

Erland Sommarskog 112.8K Reputation points

2024-08-24T14:48:41.6233333+00:00

The PerfLlib errors are benign, and the installation jogs along despite them.

The MOF compiler error, on the other hand, is fatal. I've seen these in logs when I tried to help people. I've never fully understood them, but my impression is that they are the result of multiple installation attempts with random cleanup in between.

I'm afraid that I don't have anything to add to what I said in my previous post.

MikeyQiaoMSFT-0444 3,190 Reputation points

2024-08-26T10:13:02.6133333+00:00

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 star

This record is usually caused by the failure to successfully clean up remnants of the SQL Server installation. The link provided by Erland shows the complete details for the cleanup, and you may want to go through the steps as indicated there.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to Install SQL server correctly?

1 answer

Your answer