RE: registry: Could not open key:

Try right clicking on the install .exe and Select "Run as Administrator"
--
Paul


"MXC" wrote:

> When I uninstall or install SQL Server 2005
> I got several error message:
>
> Could not open key: key name.
> Verify that you have sufficient access to that key, or contact your support
> personnel
>
> When I check the permision of these keys, I found that it was blank in
> "Group and user Name"
> I had to set user there manually one by one.
>
> I do not know how the user would be deleted in these keys.
> If there are program could scan the regstry to find these keys which no any
> group or userhasthe permissions for the keys.
>
> Thanks
>

That usually happens because a developer created the registry key
containing a null value, which cannot be read in Windows, to hide
some copy protection scheme.

You can delete an undeletable registry key using SysInternals'
RegDelNull:

"This command-line utility searches for and deletes Registry keys
that contain embedded-null characters that are undeleteable using
standard Registry-editing tools."

RegDelNull 44 KB (Freeware)
Info: http://technet.microsoft.com/en-us/s.../bb897448.aspx
Download: http://download.sysinternals.com/Files/Regdelnull.zip

Usage:
regdelnull <path> [-s] [-r]

path Registry path e.g. HKLM\SOFTWARE\
-s Recurse into subkeys

Example:
regdelnull -s HKLM\SOFTWARE\Classes\CLSID\{54955D07-73DF-4592-9A0F-C9D63E9360D2}


ju.c


"PaulB" <> wrote in message newsEBEA1CB-91B7-4606-B9FF-...
> Try right clicking on the install .exe and Select "Run as Administrator"
> --
> Paul
>
>
> "MXC" wrote:
>
>> When I uninstall or install SQL Server 2005
>> I got several error message:
>>
>> Could not open key: key name.
>> Verify that you have sufficient access to that key, or contact your support
>> personnel
>>
>> When I check the permision of these keys, I found that it was blank in
>> "Group and user Name"
>> I had to set user there manually one by one.
>>
>> I do not know how the user would be deleted in these keys.
>> If there are program could scan the regstry to find these keys which no any
>> group or userhasthe permissions for the keys.
>>
>> Thanks
>>