SQL SERVER – FIX: RequireKerberos Error During SQL 2008 Installation on Windows 2008 R2 Cluster

SQL SERVER - FIX: RequireKerberos Error During SQL 2008 Installation on Windows 2008 R2 Cluster SQL-Cluster Today the progress made in technology is astounding and beyond our imaginations, but still there are clients who can’t move to higher, latest and greatest version of SQL so easily. They are still stuck with SQL 2005 and SQL 2008 SQL servers. In this blog post we will learn how to fix RequireKerberos Error During SQL 2008 Installation on Windows 2008 R2 Cluster.

One of my client was trying to install SQL Server 2008 on Windows 2008 R2 cluster. While the setup was almost at the end, here was the error popped up.

The following error has occurred:
There was an error setting private property ‘RequireKerberos’ to value ‘1’ for resource ‘SQL Network Name (DELHISQLPRD)’. Error: Value does not fall within the expected range.

He was not sure what was wrong with his cluster. He contacted me and since I have worked with many other clients and this was seen earlier. I told him that this is a known issue (List of known issues when you install SQL Server on Windows 7 or on Windows Server 2008 R2) and Microsoft has fixed it in SP1 for SQL Server 2008

WORKAROUND/SOLUTION

As mentioned in knowledge base article by Microsoft, the issue is fixed in SP1 of SQL 2008. We need to use “Slipstream media” to install SQL Server 2008. Slipstream media mean include patch (like service pack) into the original installation. We need to follow below article to create slipstream media.

https://support.microsoft.com/en-us/help/955392/how-to-update-or-slipstream-an-installation-of-sql-server-2008

We made sure that we uninstalled SQL using “Remove Node” option before using slipstream media to install SQL cluster again. This time it worked like a charm.

Have you seen similar setup issues which you solved? Please comment and share with other readers.

Reference: Pinal Dave (https://blog.sqlauthority.com)

, , ,
Previous Post
SQL SERVER – Msg 1833 – File Cannot be Reused Until After the Next BACKUP LOG Operation
Next Post
SQL SERVER – Automatic Startup Not Working for SQL Server Service

Related Posts

Leave a Reply

Menu