Sql Server Faq

While installing security patch KB 948109 on the sql server 2005, the installation of the patch may fail. In order to find the cause of the failure we need to look into the setup bootstrap logs which are located in the following location

C:\Progarm Files\Microsoft Sql Server\90\Setup Bootstrap\LOG\Hotfix\Summary.txt

One of the cause of the failure can be Error 11032 which is reported in the summary.txt as shown

***********************************************************************

Product Installation Status

Product : SQL Server Database Services 2005 (SQLCMSP6)

Product Version (Previous): 3042

Product Version (Final) :

Status : Failure

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB948109_sqlrun_sql.msp.log

Error Number : 11032

Error Description : Unable to install Windows Installer MSP file

———————————————————————–

Product : SQL Server Analysis Services 2005 (SQLCMSP6)

Product Version (Previous): 3042

Product Version (Final) : 3068

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB948109_sqlrun_as.msp.log

Error Number : 0

Error Description :

———————————————————————————-

Product : SQL Server Reporting Services 2005 (SQLCMSP6)

Product Version (Previous): 3042

Product Version (Final) : 3068

Status : Success

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB948109_sqlrun_rs.msp.log

Error Number : 0

Error Description :

———————————————————————–

CAUSE:

====================

During the installation of the Hotfix (948109 in my case) the Windows installer looks for the folder FTData in the location c:\Program files\Microsoft sql server\MSSQL.X\MSSQL\FTdata.

However if the FTData folder has been willingly or unknowingly deleted from the location c:\Program files\Microsoft sql server\MSSQL.X\MSSQL\. then the setup of the HotFix may fail with error 11032 and following error will reported in the HotFix.log and SQL9_Hotfix_KB948109_sqlrun_sql.msp.log.

HotFix.log

=====

18/2008 18:08:30.614 Registry: Opened registry key “Software\Policies\Microsoft\Windows\Installer”

08/18/2008 18:08:30.632 Registry: Cannot read registry key value “Debug”

08/18/2008 18:10:02.595 MSP returned 1603: A fatal error occurred during installation.

08/18/2008 18:10:03.057 Registry: Opened registry key “Software\Policies\Microsoft\Windows\Installer”

08/18/2008 18:10:03.075 Registry: Cannot read registry key value “Debug”

08/18/2008 18:10:04.205 Copy Engine: Error, unable to install MSP file: e:\73ee7eecf2f2f0aa67706f3e\HotFixSQL\Files\sqlrun_sql.msp

08/18/2008 18:10:04.222 The following exception occurred: Unable to install Windows Installer MSP file Date: 08/18/2008 18:10:04.222 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807

08/18/2008 18:10:09.275 Watson: Param1 = Unknown

08/18/2008 18:10:09.344 Watson: Param2 = 0×2b18

08/18/2008 18:10:09.378 Watson: Param3 = Unknown

08/18/2008 18:10:09.446 Watson: Param4 = 0×0

08/18/2008 18:10:09.481 Watson: Param5 = copyengine.cpp@807

08/18/2008 18:10:09.498 Watson: Param6 = Unknown

08/18/2008 18:10:09.515 Watson: Param7 = SQL9

08/18/2008 18:10:09.532 Watson: Param8 = @

08/18/2008 18:10:09.566 Watson: Param9 = x86

08/18/2008 18:10:09.583 Watson: Param10 = 3068

08/18/2008 18:10:09.601 Installed product: SQL9

08/18/2008 18:10:09.618 Installing product: OLAP9

08/18/2008 18:10:09.875 Registry: Opened registry key “Software\Microsoft\Windows\CurrentVersion\Uninstall”

08/18/2008 18:10:09.926 Installing instance: SQLCMSP6

08/18/2008 18:10:09.960 Installing target: KDESQLDBOP6

08/18/2008 18:10:09.995 Stopping service: MSOLAP$SQLCMSP6

08/18/2008 18:10:17.103 Stopped service: MSOLAP$SQLCMSP6

08/18/2008 18:10:17.137 Installing file: sqlrun_as.msp

08/18/2008 18:10:17.154 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB948109_sqlrun_as.msp.log

08/18/2008 18:10:17.171 Registry: Opened registry key “Software\Policies\Microsoft\Windows\Installer”

08/18/2008 18:10:17.189 Registry: Cannot read registry key value “Debug”

08/18/2008 18:11:23.909 MSP returned 0: The action completed successfully.

SQL9_Hotfix_KB948109_sqlrun_sql.msp.log.

==================================

MSI (s) (48:50) [18:24:03:651]: Executing op: CustomActionSchedule(Action=CAFTEInstallFTERef.68C6D15C_77E0_11D5_8528_00C04F68155C,ActionType=1025,Source=BinaryData,Target=InstallFTERef,CustomActionData=C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\FTERef\|C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\)

MSI (s) (48:9C) [18:24:03:667]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI416.tmp, Entrypoint: InstallFTERef

FTECa.DLL: INFO: FTE: InstallFTERef(), Entering…

FTECa.DLL: INFO: FTE: GetFTERefInstallParams: FTERef : C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTDataFTECa.DLL: ERROR: FTE: InstallFTERef: Fail to create FTERef file: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData\noiseCHS.txt, Err=3

MSI (s) (48:50) [18:24:04:763]: User policy value ‘DisableRollback’ is 0

MSI (s) (48:50) [18:24:04:763]: Machine policy value ‘DisableRollback’ is 0

Action ended 18:24:04: InstallFinalize. Return value 3.

RESOLUTION/WORKAROUND:

====================

We need to create empty FTData folder in the location C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\FTData (in my case) and rerun the setup and the setup runs fine without any errors

 

Have you ever wondered how to change the keys for the encryption for an already encrypted database. For this you can use “Key Rotation”. Key rotation is the process of decrypting data with the old encryption key and encrypting the data with the new encryption key.

But how to use the Key Rotation with SQL Server 2005??

Below are specified a few details as to how you can go ahead and use the Key Rotation to change the key with which the data has been encrypted.

1. You can add an encryption by a temporary new certificate.
2. Drop the old encryption and the old certificate.
3. Create a new certificate with the old name, add an encryption by it.
4. Finally drop the encryption made with the temporary certificate and drop the temporary certificate as well.

And with this you have the data encrypted with a new key and the old key has been dropped.

You can refer to this blog by Laurentiu Cristofor of the Microsoft SQL Server Security team for more details and the alternatives as well.