Sql Server Faq

 

We have observed a number of cases where the installation of the sql server 2005 instance on the cluster fails with the following unexpected Failure Error Message while performing SCC checks.

ERROR MESSAGE:

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

There is unexpected failure.

MSGID 50000

 

In order to troubleshoot the issue we followed the following steps

1)       We checked the Setup Bootstraps Logs which are located in c:\Program files\Microsoft sql server\90\Setup BootStrap\LOGS\Files.

2)       We checked the Core(Local).log and found the following error was reported in the error log

 

<Func Name=’PerformDetections’>

1

Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.3042.0

Failed to enumerate disks.

HRESULT: 0×80070015

The device is not ready.

Error: Action “InvokeSqlSetupDllAction” threw an exception during execution.  Error information reported during run:

  Source File Name: datastore\clusterinfocollector.cpp

Compiler Timestamp: Sat Oct  7 09:43:48 2006

     Function Name: ClusterInfoCollector::collectClusterGroups

Source Line Number: 391

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

Failed to determine disk information

              Source File Name: datastore\clusterinfocollector.cpp

            Compiler Timestamp: Sat Oct  7 09:43:48 2006

                 Function Name: ClusterInfoCollector::collectClusterGroups

            Source Line Number: 390

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

            Enum*Disks() returned : 2147942421

WinException : -2147024875

        Error Code: -2147024875

Windows Error Text: The device is not ready.

 

  Source File Name: datastore\clusterinfocollector.cpp

Compiler Timestamp: Sat Oct  7 09:43:48 2006

     Function Name: ClusterInfoCollector::collectClusterGroups

Source Line Number: 390

 

Error: Failed to add file :”C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0020_WPSQL1_.NET Framework 2.0.log” to cab file : “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0020.cab” Error Code : 2

Error: Failed to add file :”C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0020_WPSQL1_SCC.log” to cab file : “C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0020.cab” Error Code : 32

Running: UploadDrWatsonLogAction at: 2008/8/30 10:16:17

Message pump returning: 2147942421

 

 

3)       From the above error log it was clear that setup.exe was not able to query the information about the Physical Disks.

 

Failed to enumerate disks.

HRESULT: 0×80070015

The device is not ready.

Error: Action “InvokeSqlSetupDllAction” threw an exception during execution.  Error information reported during run:

  Source File Name: datastore\clusterinfocollector.cpp

Compiler Timestamp: Sat Oct  7 09:43:48 2006

     Function Name: ClusterInfoCollector::collectClusterGroups

Source Line Number: 391

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

Failed to determine disk information

 

Cause

======

The above error is reported when either some of the physical Disk resource is Offline or is not Online from the Active Node where setup was run.

 

Resolution

========

So in order to resolve the issue we need to ensure the Disk Resource is Online from the Node from which we are installing the sql server instance in the cluster.

Once the Disk resource is brought online, the sql server 2005 installation runs fine on the cluster

 

 

 

 

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

 

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 29527 which is reported in the summary.txt as shown

Following error reported in the sumary.txt

 

·          **********************************************************************************

·          Product Installation Status

·          Product                   : SQL Server Database Services 2005 (ACT7)

·          Product Version (Previous): 3042

·          Product Version (Final)   :

·          Status                    : In Progress

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

·          SQL Express Features      :

·          Error Number              : 29527

 

CAUSE:

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

 

The issue is caused due to improper installation of support files as there may be missing files and dll’s in the 90 folder located in

 

c:\program files\Microsoft sql server\90

 

 

RESOLUTION/WORKAROUND:

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

 

We need to install a new instance of the sql server of the same edition and same built on the same system on which the original instance which need to be patched lies (i.e with required Service pack ) side by side which populates the 90 folder with correct files and dll’s.

 

Alternatively, we can also reinstall the support files  by running the SqlSupport.msi file located in the media for sql server 2005 setup.

 

The SqlSupport.msi is generally located in <cd-drive>:\servers\Setup\SqlSupport.msi

 

After installing the new instance or reinstalling the Support files by running SqlSupport.msi

We need to install security patch 948109 on the original instance on which it was failing previously, the installation of the security patch will succeed.

 

The ACT7 software installs sql server 2005 express edition along with the installation of ACT7 software. When we try to apply the latest security patch 948109 released by Microsoft for sql server 2005, the installation may fail.

In order to find the cause of the installation we need to look into the setup boothstrap logs located in the folder c:\program files\microsoft sql server \90\setup bootstrap\log\hotfix\Summary.txt.

When we check the summary.txt we may find the following error reported

Product Installation Status

Product                   : SQL Server Database Services 2005 (ACT7)

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

SQL Express Features      :

Error Number              : 29533

Error Description         : MSP Error: 29533 Service ‘TEST-PC\ACT7′ could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386)

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

Product                   : SQL Server Tools and Workstation Components 2005

Product Version (Previous): 3068

Product Version (Final)   :

Status                    : Not Selected

Log File                  :

SQL Express Features      :

Error Description         :

 

 

CAUSE:

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

 

When ACT7 software is installed on the system and the sql server instance is used by ACT7 software, it deletes all the Windows logins (for security reasons) including the BUILTIN\Administrator account for that instance of the sql server instance, generally the instance name is ACT7.

 

During the installation of the security patch 948109 the setup.exe tries to login to the sql server using the credential of the windows user with which we are trying to install the security patch. However it will not be able to login to the sql server since there is windows login for the user with which it will try to login

 

Also it is difficult to enter in the sql server instance as the sql user ‘sa’ password are not known to the end users and there is no means by which we can enter into the sql server instance

RESOLUTION/WORKAROUND:

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

 

So to resolve or workaround this we need to add the Windows login account as a sql server login with which we are installing the security patch.

 

So to add the windows login as sql server login for the sql server 2005 express edition instance ACT7 which is installed alongwith ACT7 we can use the following procedure

 

Stop the sql server service and start the sql server from command line as shown

 

C:\program files\microsoft  sql  server\MSSQL.1\MSSQL\Binn\Sqlservr.exe -s ACT7 -m -c

 

we then need to login into the sql server using sqlcmd using the following commands

 

sqlcmd -S <computer-name>\ACT7 -E

 

create login [<Windows user name>] from windows from e.g

Create login [TEST-PC\SAM] from Windows

 

grant sysadmin to windows login just created above

Sp_addsrvrolemember ‘SAM-PC\SAM,’sysadmin’

 

Stop the sql server from command line and start the sql server service again

 

You can then start the installation of service pack or hotfix and it should work

 

Note: ACT7 software tries to delete the windows login periodically and the login which we just created above might get deleted in say 15 mins so need to make sure the installation is sstarted immediately after adding the login

The ACT7 software installs sql server 2005 express edition along with the installation of ACT7 software. When we try to apply the latest security patch 948109 released by Microsoft for sql server 2005, the installation may fail.

In order to find the cause of the installation we need to look into the setup boothstrap logs located in the folder c:\program files\microsoft sql server \90\setup bootstrap\log\hotfix\Summary.txt.

When we check the summary.txt we may find the following error reported

Product Installation Status

Product                   : SQL Server Database Services 2005 (ACT7)

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

SQL Express Features      :

Error Number              : 29533

Error Description         : MSP Error: 29533 Service ‘TEST-PC\ACT7′ could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (16386)

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

Product                   : SQL Server Tools and Workstation Components 2005

Product Version (Previous): 3068

Product Version (Final)   :

Status                    : Not Selected

Log File                  :

SQL Express Features      :

Error Description         :

 

 

CAUSE:

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

 

When ACT7 software is installed on the system and the sql server instance is used by ACT7 software, it deletes all the Windows logins (for security reasons) including the BUILTIN\Administrator account for that instance of the sql server instance, generally the instance name is ACT7.

 

During the installation of the security patch 948109 the setup.exe tries to login to the sql server using the credential of the windows user with which we are trying to install the security patch. However it will not be able to login to the sql server since there is windows login for the user with which it will try to login

 

Also it is difficult to enter in the sql server instance as the sql user ‘sa’ password are not known to the end users and there is no means by which we can enter into the sql server instance

RESOLUTION/WORKAROUND:

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

 

So to resolve or workaround this we need to add the Windows login account as a sql server login with which we are installing the security patch.

 

So to add the windows login as sql server login for the sql server 2005 express edition instance ACT7 which is installed alongwith ACT7 we can use the following procedure

 

Stop the sql server service and start the sql server from command line as shown

 

C:\program files\microsoft  sql  server\MSSQL.1\MSSQL\Binn\Sqlservr.exe -s ACT7 -m -c

 

we then need to login into the sql server using sqlcmd using the following commands

 

sqlcmd -S <computer-name>\ACT7 -E

 

create login [<Windows user name>] from windows from e.g

Create login [TEST-PC\SAM] from Windows

 

grant sysadmin to windows login just created above

Sp_addsrvrolemember ‘SAM-PC\SAM,’sysadmin’

 

Stop the sql server from command line and start the sql server service again

 

You can then start the installation of service pack or hotfix and it should work

 

Note: ACT7 software tries to delete the windows login periodically and the login which we just created above might get deleted in say 15 mins so need to make sure the installation is sstarted immediately after adding the login

 

 

 

 

 

There have been a number of instances where we observed that the installation of the sql express edition on Windows Vista which also gets installed along with Microsoft Office Accounting 2008 fails which ultimately causes the installation of the Office Accounting 2008 on Windows Vista to fail.

So in order to successfully install Sql Express Edition on Windows Vista we need to take the following precautions before starting the installation so as to ensure that successful install of Sql Express On Windows Vista

 

1)   Disable User Access Control(UAC) Feature of the Windows Vista

            User Account Control (UAC) is a new security feature in Windows Vista that requires all users to log on and run in standard user privileges mode instead of as administrator with full administrative rights, thus prevent unauthorized or accidental changes that could destabilize the computers or allows virus and malware to exploit the system-level privileges provided to the local administrator to attack the network security, compromise computer safety and privacy, and damage files and settings in the network. However, in a lot of cases, administrator rights are needed by end-users to perform certain tasks such as install or update programs and perform typical system-level task. Beside, many software applications also need administrator privileges to run properly without conflicts, as they are designed to write to system locations during normal operation, and computer in locked-down state in which users operate in standard user mode severely limits user productivity.

 

·        In order to disable UAC we need to follow the following steps

·        Click Start and then open Control Panel.

·        In the Control Panel, click User Accounts and Family Safety.

·        Click User Accounts.

·        Click Turn User Account Control on or off.

·        Clear the tick or check mark on the box beside the Use User Account Control (UAC) to help protect your computer option.

·        Click OK.

·        When prompted, restart the computer. Note that the changes will affect all users on the computer.

·        To enable the UAC, simply tick or select the checkbox again.

 

2)   Disable all the Non-Microsoft Services

There are certain services which can prevent or hinder in the installation of the sql server on Windows system. Some of these services which are observed to cause problems while installation of the sql server are Antivirus, Malware and even Citrix Virtual Memory Optimization service. So in order to prevent any third party service from the installation of the sql server we would preferably disable all the Non-Microsoft services which can re enabled after the installation

In order to disable the Non-Microsoft services.

·        Go to Start->Run->type msconfig

·        Click on the services tab in the Dialog box

·        Click the check box Hide all Microsoft Services

·        Click On Disable ALL

·        Click On Ok

·        We now need to restart the system for the changes to take effect

 

 

 

3)   Check whether WMI repository is INCONSISTENT

If during the installation of the sql server on Windows vista fails with the following error

 

TITLE: Microsoft SQL Server 2005 Setup

——————————

 

SQL Server Setup Failed to compile the Managed Object Format (MOF) file c:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see “Troubleshooting an Installation of SQL Server 2005″ or “How to: View SQL Server 2005 Setup Log Files” in SQL Server 2005 Setup Help documentation.

 

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29513&EvtType=sqlca%5csqlmofca.cpp%40Do_sqlMofcomp%40Do_sqlMofcomp%40×7349

 

 The above error indicates that the WMI repository might be inconsistent so to resolve the error we need to fire the following command

 

C:\Users\Owner>winmgmt /verifyrepository

WMI repository is INCONSISTENT

If the output shows that WMI repository is INCONSISTENT we need to fire the following command to salvage the repository

C:\Users\Owner>winmgmt /salvagerepository

WMI repository salvage failed

Error code:     0×8007041B

Facility:       Win32

Description:    A stop control has been sent to a service that other running ser

vices are dependent on.

 

It may throw the following error when you fire the above command for the first time so run the command again as shown

C:\Users\Owner>winmgmt /salvagerepository

WMI repository has been salvaged

 

Once the above precaution is being taken we can start with the installation of the sql server express and it should go fine.

If still the error occurs while installation we might have to troubleshoot further by looking at the setup bootstrap logs. But precaution can be helpful in the installation of the sql express edition on Windows Vista