INSTALL SQL SERVER 2008 64 bit ON CLUSTER

1. Check the required Service Account and domain groups have been created for
SQL Server and Agent services
2. Reboot the server.
3. Stop all Symantec Antivirus in services of the server.
4. Cluster group where SQL Server 2008 will be installed –
a. Delete the IP address and virtual name created for SQL Server where SQL
Server is going to install.
b. Make sure no other IP address like VERITAS IP are present in group, if
present make note of the IP and delete and recreate after installing SQL
2008.
c. MSDTC Cluster group should be on the same node where the installing
SQL 2008
5. If the server is Windows 2003 with SP1 or SP2, download and install the hotfix
for windows
Windows Server 2003 hotfix KB937444 is not installed. This hotfix is
required for FILESTREAM to work on a Windows Server 2003-based
cluster.
Download the KB Article - http://support.microsoft.com/kb/937444,
install to proceed
(http://support.microsoft.com/hotfix/KBHotfix.aspx?
kbnum=937444&kbln=en-us)
6. Install on cluster only – need to installed on both nodes for adding node and
failover known issues
To avoid a known issue on scenarios like ours during the second node add
process (reference: http://support.microsoft.com/kb/957459) you must apply
the hotfix KB956717 before start adding the second node.

7. Installing on second node

8. Errors and Solutions while installing SQL Server 2008

tsshutdn /reboot

After Reboot click on setup

Click on New SQL Server Failover install
7Sq!Server
Click on Close… Successfully completed installing on one node
Follow the per-request installing hot fix on the other
node.
Start installing the set up, click on “Add Node to a SQL Server failover cluster “
Click on Install
Click on Install
Click on Close Radio button
Do the failover and check failover is running fine.

Reboot both the nodes

Errors and Solutions while installing SQL Server 2008

Cause and Solution:

Cluster groups were present and Drive were not added to the cluster groups

Add the Drives to the cluster groups and Re-Run the Support Rules
---------------------------
Rule Check Result
---------------------------
Rule "Network binding order" generated a warning.

The domain network is not the first bound network. This will cause domain operations to
run slowly and can cause timeouts that result in failures. Use the Windows network
advanced configuration to change the binding order.
---------------------------
OK

Work Around to clear the warning

Right Click on My Network Places  Properties  Advanced  Advanced Settings 

Public LAN should be first.  Click ok
If still the same warning (http://msdn.microsoft.com/en-us/library/ms189910.aspx )

Failover cluster Setup operations include a rule that checks network binding order.
Although binding orders might seem correct, you might have disabled or "ghosted" NIC
configurations on the system. "Ghosted" NIC configurations can affect the binding order
and cause the binding order rule to issue a warning. To avoid this situation, use the
following steps to identify and remove disabled network adapters:
1. At a command prompt, type: set devmgr_Show_Nonpersistent_Devices=1.
2. Type and run: start Devmgmt.msc.
3. Expand the list of network adapters. Only the physical adapters should be in the
list. If you have a disabled network adapter, Setup will report a failure for the
network binding order rule. Control Panel/Network Connections will also show
that adapter was disabled. Confirm that Network Settings in Control Panel shows
the same list of enabled physical adaptors that devmgmt.msc shows.
4. Remove disabled network adapters before you run SQL Server Setup.
5. After Setup finishes, return to Network Connections in Control Panel and disable
any network adapters that are not currently in use.
If its standalone, User can proceed installing
The warning is only meaningful on clusters with
multiple public, routed NICs.

Unbind NETBIOS from the heartbeat NICs and Windows must use the public NICs
to find a domain host.
Workaround
Type the Domain group names manually, when we browse we get error it’s a known
Microsoft bug

NA\SQL2K8 PROD SERVER SERVICE

NA\SQL2K8 PROD SERVER AGENT SERVICE
---------------------------
Rule Check Result
---------------------------
Rule "Windows Server 2003 FILESTREAM Hotfix Check" failed.

Windows Server 2003 hotfix KB937444 is not installed. This hotfix is required for
FILESTREAM to work on a Windows Server 2003-based cluster.
---------------------------
OK

Download the KB Article - http://support.microsoft.com/kb/937444, install to proceed

(http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=937444&kbln=en-us)

Once Installed reboot the server and start installing SQL Server 2008
---------------------------
Microsoft SQL Server Management Studio
---------------------------
The file C:\WINDOWS\Microsoft.NET\Framework\冬䶩冪悉冪袬冧✕媱빼-뷮秩滜冧
빰-뷸秩뺘- \mscorlib.tlb could not be loaded. An attempt to repair this condition failed
because the file could not be found.

Please reinstall this program.

---------------------------
OK

Workaround

http://support.microsoft.com/kb/918685

For SQL Server 2008

To work around this problem, you must manually specify the correct path of the
Mscorlib.tlb file in the registry. To do this, follow these steps:

1. Take backup of the registry before changing the values.

 2. Click Start, click Run, type regedit, and then click OK.
3. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\100\Tools\Shell\TlbAutoRepair\mscorlib.tlb Notes
If you install the 32-bit version of SQL Server 2008 on 64-bit operating
systems, locate the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL
Server\100\Tools\Shell\TlbAutoRepair\mscorlib.tlb
If you install SQL Server 2008 Express Edition with Advanced Services, locate
the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\100\Tools\ShellSEM\TlbAutoRepair\mscorlib.tlb
4. In the right pane, double-click TlbPath.
5. In the Value data box, replace %CLRVERSION% with the following value:
v2.0.50727

Note The value v2.0.50727 indicates the version of the .NET Framework that the
original release version of SQL Server 2008 uses.

6. Click OK, and then exit Registry Editor.

Important If you install a SQL Server 2008 service pack or hotfix, the service pack or
hotfix will change the value that you replace in step 4 back to %CLRVERSION%. If the
problem that is described in this article still exists after you install the service pack or
the hotfix, you must following these steps again to work around this problem.

===============================================================
TITLE: SQL Server Setup failure.
------------------------------
SQL Server Setup has encountered the following error:
The current SKU is invalid..
------------------------------
BUTTONS:
OK
------------------------------

Solution
Install SQL Server Hotfix
Do the following process on both nodes:
To avoid a known issue on scenarios like ours during the second node add process
(reference: http://support.microsoft.com/kb/957459) you must apply the hotfix
KB956717 before start adding the second node.

1. Access the folder SQL 2008 Ent\SQLFULL_ENU and execute file

360783_intl_i386_zip.exe and unzip the hotfix (hotfix password: oL@U-
ZH);
2. Execute file SQLServer2008-KB956717-x86.exe;
3. The hotfix will run a check, after it´s completed click NEXT;
4. Accept the License Terms and click Install;