SQL Server setup takes more time and is in hung state during ‘Setting File Security’


You might have encountered an issue where SQL Server setup will be in hung state during ‘Setting File Security’ phase.This is a known issue and is documented by Microsoft :

http://support.microsoft.com/kb/910070/en-us

The best workaround is to unplug network cable or just keep on waiting for atleast 2-5 hours!

Advertisements

Slipstreaming SQL Install


Recently I had to Install SQL Server 2008 Standard on a cluster and our setup was giving error like  ‘Value cannot be null;Parameter=Connection’

This issue was fixed when I tried Slipstreaming. What is slipstreaming? This is a combination of all the patches to the initial install (RTM). When you copy newer files over older files a slipstream is formed.

Below are the steps, which I followed to fix the issue:

Steps :

1 . Copy original SQL Server 2008 source setup to c:\SQLServer2008_FullSP1

2. Extract service pack to SQLServer2008SP1-KB968369-x64-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU

3. Copy Setup.exe and Setup.rll from the PCU extracted location to original source setup location

4. Copy all files not the folders, except the Microsoft.SQL.Chainer.PackageData.dll, in c:\SQLServer2008_FullSP1\PCU\<architecture> to C:\SQLServer2008_FullSP1 \<architecture> to update the original files.

5. Modify the defaultsetup.ini by adding PCUSOURCE=”{Full path}\PCU”,ie PCUSOURCE=”C:\SQLServer2008_FullSP1 \PCU”

6. Ran the setup

Cluster was build and there was no more errors.

File format is not valid! Error during SQL 2008 R2 Developer Edition Install


Recently I received an error while installing SQL Server 2008 R2 Developer Edition.The error was saying about ‘File format is invalid’.

Resolution : This erorr comes up when you have a corrupt sql setup.Solution is to download the setup once again from MSDN or VLSC site.

You also need to ensure that the ISO file which is downloaded from the site is properly extracted using a tool like Winrar(recommended).

I love to hear if you have faced this error anytime before and was there a different fix which was applied.