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 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

 

 

 

 

 

While installing SP2 on the sql server 2005, the installation may fail. Whenever the sql server installation fails it creates a log in the following location.
C:\Program Files\Microsoft Sql Server\90\Setup Bootstrap\LOG\

The above location generally contains following folders and file.
1) Files                (Contains Logs for the installation of the RTM (Release to Market) version of the sql server)
2) HotFix             (Contains Logs for the installation of the Hotfixes and service packs)
3) Summary.txt   (Contains summary of all the sql server products which were installed and                               whether they  Successfully installed or Failed) 

                                  
These logs are created for any sql server 2005 setup installation which applies to the installation of the RTM version or any of the service packs and even all the editions of the sql server 2005 viz Standard Edition, Express Edition, Enterprise Edition.
Whenever the sql server 2005 setup fails we need to check the summary.txt located in the above location to get the information for cause of the failure and to know which products were unsable to install.
So during the installing of the sql server 2005 sp2 if the installation fails and when you look at the summary.txt, you may find that one of the cause of the failure is ERROR 29506.
The summary.txt may have the following information
———————————————————————————-
Product                   : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number              : 29506
Error Description         : MSP Error: 29506  SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that  exists on the destination drive.

 

When you look into the file C:\Program Files\Microsoft SQL Server\90\Setup  Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log you will see the following error

 

Configuring ACL:
 Object: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data   ACL: (A;OICI;FA;;;[SQLServer2005MSSQLUser$CORPDBPRO$MSSQLSERVER])
Action: 0×103
Failed ACL:
  SetSecurityFileDescriptor is failed at the error code 5; Converted SDDL: ‘(A;OICI;FA;;;S-1-5-21-3714694515-4057322299-1779769068-1013)’
        Error Code: 0×80077342 (29506)
Windows Error Text:   Source File Name: sqlca\sqlsddlca.cpp
Compiler Timestamp: Wed Jun 14 16:27:11 2006
     Function Name: ExceptionInSDDL
Source Line Number: 65

 

The main cause of the above error is that there is improper permissions of the DATA and LOG folder of the sql server 2005. In other words the DATA and LOG folders didn’t have Full Control permissions for the user Administrator and as a result the error message says
MSP Error: 29506  SQL Server Setup failed to modify security permissions on file C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ for user Administrator

In order to avoid the error we need
1) To start the SP2 installation using an administrator or a user with administrative privileges.

2) All the files and the folder contained in the DATA and LOG must have Administrative privileges with FULL CONTROL permissions.
In order to achieve this right click on the DATA and LOG folder go to sharing and security. Click on the security tab and make sure Adminstrator is present and it has FULL CONTROL. Also go to the advanced tab and click on inherit the permissions to the child objects.
Finally confirm that all the folders and files located inside DATA and LOG folder have Full Administrator priviledge.
Once the permission issue is resolved we can restart with the installation and it will work fine

Reference
http://support.microsoft.com/kb/916766/en-us