question

SR5331 avatar image
0 Votes"
SR5331 asked TomPhillips-1744 edited

Couldnot Open Key UNKNOWN\Components\. when install SQL2019

Hi ,

Uninstalled SQL 2016 version completely and install SQL 2019 Developer version in windows 10 , while installing getting the error prompt "Error 1402. Could not open key UNKNOWN\Components.... Verify that you have sufficient access to that key or contact your support personnel " .

I have tried all the suggestion from MIcrosoft forums ,I gave Full Control under adminstrator account and run the query in cmd Prompt "SECEDIT /CONFIGURE /CFG %WINDIR%\INF\DEFLTBASE.INF /DB DEFLTBASE.SDB /VERBOSE /AREAS REGKEYS" and still issue persists. Any help is appreciated.

205845-sl.jpeg


sql-server-general
sl.jpeg (402.2 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Do you notice the link in the bottom of the picture? That link takes you a folder with lots of log files. I am not saying that you will be able to resolve the issue with help of these log files, because they are very verbose. Most of it is Greek to me as well, But if you are lucky, the penny may drop.

The one to start with is detail.txt.

1 Vote 1 ·
SR5331 avatar image
0 Votes"
SR5331 answered ErlandSommarskog commented

205854-summary-145729.txt


I tried to click that file to check , same error persists with some explanation and when i click the error link it goes to Microsoft website .


summary-145729.txt (18.6 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I didn't say that it would be easy, did I?

The summary file does not give that much more information, but the talk of the MOF compiler and the WMI server suggests that your machine is a little hosed.

As I said, the file to start with is detail.txt, and then possibly look in the other files. And, no, I am not promising that you will spot the root cause that way, or for matter that anyone else will. But it can be worth giving a shot before you take more drastic measures.

One option if you don't want to flatten the machine, is to create a virtual machine and install SQL Server on the VM.

0 Votes 0 ·
TomPhillips-1744 avatar image
1 Vote"
TomPhillips-1744 answered TomPhillips-1744 edited
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Cathyji-msft avatar image
0 Votes"
Cathyji-msft answered TomPhillips-1744 edited

Hi @SR5331,

Could not open key: UNKNOWN\Components\E76F7102E9174B94484FD2237D1B06C6\7705D418F39C2E248B571707701C689B.
Could not open key: UNKNOWN\Components\023B3CE874798074CA60E2B343A45479\4D4F33C25A9E1ED4CAEFA33164E47630.
Could not open key: UNKNOWN\Components\1C577CC61E2D0E84E920735D0B9EEA23\763D39D9CC2A8734DB3697FEF37EC687.

The error is generally caused by insufficient or incorrect permissions on the named registry keys or parent container of such registry keys. Error seen in summary log is pointing to three registry paths. To resolve this issue, select appropriate permission to the Windows Registrys that mentioned in summary log. Note: Back up the registry key before you modify any key in the registry.

1.Click Start > Run, type regedit, and click OK. The Registry Editor window opens.
2.Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components. The 'S-1-5-18' key may be different on your computer.
3.Once you find the registry key (such as E76F7102E9174B94484FD2237D1B06C6) displayed in the error message under components, you need to provide permission for the key.
Right Click the GUID –> go to Permissions –>
Click on Advanced –> Click Add –> Type <hostname>\administrators and click Ok –> Click Ok –> Click Ok
206073-screenshot-2022-05-27-112800.jpg
206056-screenshot-2022-05-27-112920.jpg

Refer to the blog SQL SERVER – FIX – Error 1402 – Could not Open Key: UNKNOWN\Components to get detail information.


If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".








· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi Cathyji-msft,

I tried all the suggestions referred from the link and gave permissions also but my situation didn't change anything. When I right click the parent key not getting an error prompt but child key says key couldn't opened.
205996-a.png


0 Votes 0 ·
a.png (104.4 KiB)

Hi,

According to your screenshot, it is still permission issue. Please give the permission to the child key.

0 Votes 0 ·

Is this your private machine, or is this in a corporate environment?

What anti-malware software do you have installed?

0 Votes 0 ·
SR5331 avatar image SR5331 ErlandSommarskog ·

Its Corporate environment and using Trend Micro security Agent Anti malware.

After Uninstall sql 2016 and then install sql 2019 , suddenly got this issue

0 Votes 0 ·
Show more comments
ErlandSommarskog avatar image
0 Votes"
ErlandSommarskog answered

Its Corporate environment and using Trend Micro security Agent Anti malware.

After Uninstall sql 2016 and then install sql 2019 , suddenly got this issue

It is not implausible that the permissions errors you see are due to Group Policy or (over-)zealous surveillance of the registry from TrendMicro. We certainly have seen cases where the anti-malware software has prevented SQL Server from being installed. Although, the UNKNONWN thing suggests that something is really wonky. But it could be a combination of both.

Anyway, I suggest that you discuss with your IT department. Possibly, your machine has to be refreshed from your corporation standard image.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.