Install SQL Server 2012 in Stand Alone Machine

Requirements for Installing SQL Server 2012:

1.       Operating system Requirement :

You can install in below operating systems

Windows Server 2012,

Windows 8,

Windows server 2008 R2 SP1,

Windows 7 SP1.

You can also install in below operating systems but you require to install update http://support2.microsoft.com/?kbid=956250 on below operating system before initiating the installation.

Windows Vista SP2

Windows Server 2008 SP2

2.       NET Framework

.NET 4.0 is a requirement for SQL Server 2012. SQL Server installs .NET 4.0 during the feature installation step.

You must enable or install.NET 3.5 SP1, If you select to install Database Engine, Reporting Services, Master Data Services, Data Quality Services, Replication, SQL Server Management Studio on Windows Vista SP2 or Windows Server 2008 SP2 operating systems. OS wont have .NET 3.5 SP1 Framework 

3.       Windows Powershell

Powershell 2.0 is mandatory to install SQL Server 2012. If  SQL Server setup reports Powershell 2.0 is not present, you can install or enable it.

4.       Internet Explorer 7 or a later version.

5.       Hard Disk : SQL Server 2012 requires minimum of 6 GB.

6.       Memory

 Minimum :  

<![if !supportLists]>1.       <![endif]>Express : 512 MB

<![if !supportLists]>2.       <![endif]>Other  : 1 GB

       Recommended

<![if !supportLists]>                                                         i.            <![endif]>Express : 1 GB

<![if !supportLists]>                                                       ii.            <![endif]>Other  : 4 GB

Installation Steps:

Go to setup file location  click on setup.exe

Next you will see the SQL Server Installation Center  page. In Left side pane select Installation Tab

In installation page, right side pane you will found 4 option 

               

Option 1 : New SQL Server stand-alone installation or add features to existing installation 

                                Using this option you can install Stand-alone server  or add SQL Server features to an existing installation

Option 2 : New SQL Server failover cluster installation

                                Using this option you can install a SQL Server in Failover Cluster

Option 3 : Add Node to the SQL Server failover cluster

                                This option is used to add a node to an existing failover cluster

Option 4 : Upgrade from SQL Server 2005, SQL Server 2008 or SQL Server 2008 R2

                                Using this option we can upgrade the existing SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 to SQL Server 2012

Now we are performing SQL Server stand-alone installation so click on Option 1.

It will initiate the stand-alone installation process of SQL Server 2012

                               

Next screen displays you Setup Support Rules screen, click on  button to see all the rules information.

Click on Ok

Above screen will provide you the available latest updates.

Click on the Next.

In next screen you need to select weather is it new installation are adding features to an existing installed instance.

Select Perform a new installation of SQL Server 2012 radio button for fresh installation

In next screen need to select weather is it free edition or need to provide product key and click on Next

Next  is the license  terms screen. You need to accept the license terms and click on Next.

l

Select All features with defaults to install all features with default values and select Next

Select the what ever you want install in the instances. If this is the first installation you can select what ever shared features you want. If it is another instance already installed shared features are grayed out. Click on Next

TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.

2015-02-17 12:27:38.19 spid15s     Error: 26014, Severity: 16, State: 1.

2015-02-17 12:27:38.19 spid15s     Unable to load user-specified certificate [Cert Hash(sha1) "5B4FF9FFF4E6752A3AD51489E1A9C455E580BCC3"]. The server will not accept a connection. You should verify that the certificate is correctly installed. See "Configuring Certificate for Use by SSL" in Books Online.

2015-02-17 12:27:38.19 spid15s     Error: 17182, Severity: 16, State: 1.

2015-02-17 12:27:38.19 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 

2015-02-17 12:27:38.19 spid15s     Error: 17182, Severity: 16, State: 1.

2015-02-17 12:27:38.19 spid15s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 

2015-02-17 12:27:38.19 spid15s     Error: 17826, Severity: 18, State: 3.

2015-02-17 12:27:38.19 spid15s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

2015-02-17 12:27:38.19 spid15s     Error: 17120, Severity: 16, State: 1.

2015-02-17 12:27:38.19 spid15s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Event ID 17182: TDSSNIClient initialization failed with error 0x7e, status code 0x3a.

Event ID 17826: Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

Event ID 17120: SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Solution :

1. Check 'Forced Encryption' (Turned False) and 'Certificate' value is cleared under SQL Server Configuration Manager.
2> Check the following registry key 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.SQL2008\MSSQLServer\SuperSocketNetLib\Certificate
and clear the Certificate values.

Installing SQL Server – reboot required check fails

Not able to install SqlServer 2008 says Restart computer failed

SQL Server Installation Rules and "System Reboot Required" Error

I get the error message the prerequisites  "Restart the computer is required".

When installing SQL Server some times you may run to situation for "Reboot required check failed" failed issue in prerequisites validation screen.  To skip this failure without restarting machine. 

Goto run and type regedit.exe to open registry 

in registry 

Goto:  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager , and instead of "EXPANDING" Session Manager, "SELECT" it and you will see the entry called, PENDING FILE RENAME OPERATION 

Take backup of registry value first.

Then, If PENDING FILE RENAME OPERATION has any values just remove it and clear the value

Reboot the System and again go to PENDING FILE RENAME OPERATION and see if there is any values still available.

--

Thanks & Regards
Venkat Sangu

SPLIT STREAM Installation

If you are getting below error while installing SQL 2008 RTM Version in cluster environment please install SQL 2008 SP1 using  Split Stream

<![if !vml]><![endif]>

PROCEDURE TO DO SPLIT STREAM:-

Step:1  copy your original SQL server setup to a folder named “SQL2008R2”------ this name is for reference I am using in this doc you can use any based on the version.

Step:2  download the service pack from 

http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=26727

location . make sure you download them all 3 (x86,x64 and ia64).

irrespective of the fact you will eventually be using one … but to make sure your SP are complete in every sense.

step:3  you need to create a FOLDER named SP2 (or whatever you want to name it ) with in the folder named SQL2008R2 (that is the location where your original installation is placed) .

step: 4 extract the 3 downloaded EXE into this newly created FOLDER named SP2 below is the example for your

  reference.

                               SQLServer2008R2SP2-KB2630458-IA64-ENU.exe /x:T:\SQL2008R2\SP2

                                SQLServer2008R2SP2-KB2630458-x64-ENU.exe /x:T:\SQL2008R2\SP2

SQLServer2008R2SP2-KB2630458-x86-ENU.exe /x:T:\SQL2008R2\SP2

Step: 5     make sure T:\SQL2008R2 contains the original SQL server setup and we created a folder named SP2 within

T:\SQL2008R2.

Step:6  copy the SETUP.exe  file from newly created folder SP2 into original setup .. that we want to replace the setup.exe file of original SQL server setup with SP2 setup.exe

                                T:\SQL2008R2_SP2>robocopy T:\SQL2008R2\SP2 T:\SQL2008R2 setup.exe

Step: 7 Copy all files not the folders, except the Microsoft.SQL.Chainer.PackageData.dll, in T:\SQL2008R2\SP2\<architecture> to T:\SQL2008R2\<architecture> to update the original files. Here is the Robocop command.

In the above step we are moving the dll files which are present in  x86,x64,ia64 of SP2 to main version software  of either it may be 2005,2008,2012  Of  x86,x64,ia64 overwrite the dll  files present in the destination location that is main software folder.

T:\SQL2008R2_SP2>robocopy T:\SQL2008R2\SP2\x64 T:\SQL2008R2\x64 /XF

Microsoft.SQL.Chainer.PackageData.dll  ---for reference use.

T:\SQL2008R2_SP2>robocopy T:\SQL2008R2\SP2\x86 T:\SQL2008R2\x86 /XF

Microsoft.SQL.Chainer.PackageData.dll---for reference use.

T:\SQL2008R2_SP2>robocopy T:\SQL2008R2\SP2\ia64 T:\SQL2008R2\ia64 /XF

 Microsoft.SQL.Chainer.PackageData.dll---for reference use.

Step: 8   check whether you have DefaultSetup.INI .. at main version location in respective folders x86,x64,ia64 if not there create it with the name “ DefaultSetup.INI “

                                                                                T:\SQL2008R2\x64

T:\SQL2008R2\x86 and

T:\SQL2008R2\ia64

Step: 9  If you have a DefaultSetup.INI at the above locations, add the following lines to each DefaultSetup.INI:

PCUSOURCE=”.\SP2”

Note: In that mark place provide the sp2 path location which is present outside of 2008 folder or inside the folder  in  three folders

            x86,x64,ia64 at  DefaultSetup.INI

Note : SP2 is the folder we created within the original setup files .. if you used a different name .. please use that folder name ..

          this tells the installation setup  that service patch files are located within this folder .

step : 10   run the default  setup as the SP2 patch location is also mentioned in the default setup so we can run below setup normally.

                                    T:\SQL2008R2----for reference

below are the indications that you are doing a slipstream installation.

for this … I showing  only chosen database engine .. in the features ..

install411> confirm tht you see “Update Setup Media Language Rule” as PASSED in the installation rules page

install512> On the Ready to Install dialog, the Action will indicated (“Slipstream”) … this confirms … that we are going right .. till now ..

install613>  PCUSource parameters in the summary log .. states that it picked up the SP2 from the path we pointed it to ..

install8install9

this confirms that our installation has gone right … do confirm the same by connecting using SSMS