1. Skip to Menu
  2. Skip to Content
  3. Skip to Footer>

Expert Sessions!

SQL Service Pack Upgrade Issues

31 July 2012

Written by Prakash Palani

Today I had to deal with many number of issues those occurred while performing SQL Service Pack 4 Upgrade in MSCS environment, the issues were absolutely strange (at least to me), there were no structural solution given either by SAP / Microsoft, hence I had to go with my own way of identifying the root cause.  I have listed down all of the issues and the possible solutions below,  I am sure this will help you one or the other day when you attempt to implement SQL Service Packs in MSCS environment.

 

Issue # 1 : Unable to install windows installer MSP file

 

Solution :  Stop the installation process, kill all the hotfix.exe and  related processes (msiexec) those are running in both the nodes. If needed, restart both the nodes to clear the hanging installation processes.

Issue # 2 :  Installation in Passive Node gets stuck and runs for a very long time, below kind of message can be seen in the log, but nothing more.

 

 

Solution : Killed msiexec process on the passive node (when the installation is running), then it will be alright (believe me, it worked very well for me)

 

Issue # 3 : MSP Error 29512, SQL Server Setup was unable add user to local group

Solution : Check the user which is used to run the SQL services is added to the cluster group mentioned in the error message, if not add the user to the user  group related to the cluster. If that is something not doable, then change the service to run with the user that is maintained in the cluster group mentioned in the error (the same should be done using the configuration manager and not directly in the services.msc)

 

 

Issue # 4 : sqlsrvres.dll is being held in use by the following process name : resrcmon

 

Solution : You may ignore the error message as this is just a warning, this is really not something to be worried about, if you still think that there is a problem due to the file being blocked, then  uncheck the “Run this resource in a separate resource monitor” in the cluster configuration for the services related to SQL server.

 

{fcomment} {flike}

Share

SQL Service Pack Upgrade Issues

SQL Server Installation, an instance with the same name is already installed on this computer,

31 July 2012

Written by Prakash Palani

During SQL Server Installation, you may get an error saying “An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.” Below suggestions may help you take necessary steps to overcome the mentioned error.

 

Below are the few reasons and solutions which can help you with the above mentioned error

 

Reason # 1: An instance is already installed

 

Solution : Install a Named Instance with Unique Name

 

Reason # 2: Previous uninstallation was not successful

 

Solution : Use the Windows Installer Cleanup Utility (MSICUU2.EXE) / MS KB 290301 to cleanly uninstall the SQL Server Software (then proceed with the installation)

 

Reason # 3 : Previous installation was successful, but the registry entries are not cleaned even after running the Cleanup Utility

 

Solution : regedit, HKLM -> Software -> Wow6432Node -> Microsoft -> Rename/delete Microsoft SQL Server Entries, then start with the installation.

 

{fcomment} {flike}

Share

 

 

SQL Server Installation, an instance with the same name is already installed on this computer,

Configure Database Mail, sp_send_dbmail

31 July 2012

Written by Prakash Palani

 

Here are the steps to configure Database Mail in Microsoft SQL Server, please note that these steps are only valid to Microsoft SQL Server 2005.  Please refer to article http://basisondemand.com/mss/script_to_monitor_transaction_log_space_and_alert_dbcc_sqlperflogspace to understand, how this functionality can be used in a stored procedure/scripts.

 

 

Read Article

Script to monitor Transaction Log Space and Alert

31 July 2012

Written by Prakash Palani

 

Here is a script that can help you to monitor the used transaction log space and alert by email when it reaches the threshold value.

 

Step 1 : Create a stored procedure that will be called from Step 2 to send out the alert email

 

Read Article

Never Delete files from c:\windows\installer directory

31 July 2012

Written by Prakash Palani

 

The reason for preserving files from installer directory is that Windows keeps all the necessary .msi/.msp files in that directory for the subsequent service pack upgrades, for example, if you install SQL 2005, windows will keep an .msi file in installer directory. Similarly when you apply service packs, windows will keep an .msp file into installer directory, if you apply 4 different service packs (SP2, SP3, SP4, SP5), then you will be able to see 4 different .msp file and one .msi (original installation) file in the installer directory. If you need to upgrade to SP6, then you will need all these .msi / .msp file in installer directory, even if you miss a single file in the whole chain, your service pack upgrade will fail for sure with the below message.

 

Read Article

Latest Articles

  1. No Service for System SAP (1999-11-30 00:00:00)
  2. WebUI Not Starting (1999-11-30 00:00:00)
  3. WebUI Not Starting (1999-11-30 00:00:00)
  4. No RFC Destination for SID (2014-05-15 10:20:15)
  5. SQL 2005 Installation - number of CPUs is not a power of 2 (2014-01-03 04:59:23)

FollowUs on Twitter

SAP Web Dispatcher

SAP Web Dispatcher

Defining Backup Strategy

Defining Backup Strategy

Security Patch Strategy

Defining Security Patch Strategy

RCA Setup Guide

RCA Setup Guide for BI SBOP (BOBJ)

End-To-End SSL Setup

End-To-End SSL Setup Guide for Web Dispatcher