Rule “Consistency validation for SQL Server registry keys” failed. The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
The issue occur when the installer unable to update the registry entries due to lack of permission. Please follow the below steps to resolved the issue.
1. Go to RUN –> Type regedit.
2. Locate HKEY_LOCAL_MACHINE -> SOFTWARE -> MICROSOFT -> Microsoft SQL Server in the registry
3. Right click and select Permissions…
4. Click on Advanced
5. Under Permission TAB, select “Replace permission entries on all child objects with entries shown here that apply to child objects”.
6. Click OK.
7. Now Re-run the SQL Server installer.
References: //sqlserverteacher.blogspot.com.es/2014/01/consistency-validation-for-sql-server.html
//connect.microsoft.com/SQLServer/feedback/details/668112/rule-consistency-validation-for-sql-server-registry-keys-failed
This entry was posted on 19 May 2014 a 3:54 pm and is filed under Errores, SQLServer. Etiquetado: installation. You can follow any responses to this entry through the RSS 2.0 feed. You can , o trackback from your own site.
The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1. WSUS Server [WSUS 3.0 SP2 ] should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled[will be enabled by default] and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. Unde
Consistency validation for SQL Server registry keys failed error -SQL for SCCM
During installation of SQL server, "Consistency validation for SQL Server registry keys failed” error pops up in the below scenarios.
- Previous installation of SQL exists.
- Inappropriate permissions on the registry keys of Microsoft SQL server.
Solution that worked me is explained below.
Identify the issue:
1. Go to %Program Files%\Microsoft SQL Server\100\SetupBootstrap\Log\”date and time of installation”
2. Search [in Detail_GlobalRules.txt] for lines containing the following string
"Could not fix registry key"
3. Run “regedit”, s
et full control permissions for the appropriate registry keys mentioned in "Detail_GlobalRules.txt" file.
Re-run the installation.
- Modifying the registry:
1. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry. [To open registry, run “regedit”]
2. Right click and go to Permission
3. Click on Advance tab and c
heck the below options.
- Include inheritable permissions from this object's parent.
ii. Replace all child object permissions with inheritable permissions from this object.Click OK twice.
Reboot the server and try installing again.
Take a backup of the registry before modifying.
Popular posts from this blog
If using a domain account to install SQL server 2008 R2 for SCCM, you have to register a SPN [Service Principal Name] in Active Directory for that domain account. Two SPNs for the account should be registered, 1. For NETBIOS name of the SQL Server 2. For the FQDN of SQL server. The procedure to do that is as follows 1. Log on to a domain controller; open a command prompt with administrative privileges. 2. Type the below commands replacing SQL server name. setspn –A MSSQLSvc/< SQL Server NETBIOS name >:1433 setspn –A MSSQLSvc/< SQL Server FQDN >:1433 3. As shown in the below screenshot, the server name here is CM2012 for NETBIOS name and CM2012.CONTOSO.COM 4. Verify the registration of SPN by typing the below command Setspn –L
You can use the below SQL query to create a new collection based on GUID. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SMBIOSGUID = " 18764D56-C91F-83A5-51FB-4AD4B6699D04 " Replace the GUID with the one that you intend to delete. This is particularly useful when performing OSD related tasks. To know how to create a collection , go through this link .