Scribd
Upload
34 views14 pages

Installations Part2

Uploaded by

a3073686
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
34 views14 pages

Installations Part2

Uploaded by

a3073686
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

1.

Patching
Sql server 2005

RTM(Release to manufacture)-base version


Sp=service pack,its a collection of CUs and some hotfixes
CU=Cumulative update,its a collection of hotfixes.
Hotfix=Solution for a specific bug/issue.
Hotfixes (CVE,OD,COD,GDR,QFE)
GDR- General distribution release(global impact and very critical)
QFE- Quick fix engineering
CVE- Common vulnerabilities and exposures
OD- ON demand
COD- Critical on demand

9.00.5000.00
Major Version=9
Minor version=00
Build number =5000(represents patch applied)
Revision History=00

Sp1 = 2047
Sp2 = 3042
Sp3 = 4035
Sp4 = 5000

SQL SERVER 2008R2 SP3


SQL SERVER 2022 CU FIX
1.SLIP STREAM INSTALLATION(Graphical way)
SQL SERVER 2016+ SP2+CU17+CVE

Precautions to take before applying patches:

1.Before and after patching validation and communications with


all stake holders(Application Teams or developers)
2.Take SQL Server all database backups
3.If any HADR (Log shipping,mirroring,clustering,Always on
AG,Replication etc) take necessary actions based on the HADR
you have (either disable HADR or failover or pause)
4.System State Backups(OS level backup) taken by windows
Team
5.if needed initiate a server restart.
2a. Slipstream command based installation
QS(quiet simple)

setup.exe /QS/ACTION="Install"/INSTANCEID="SQL2022_2"
/INSTANCENAME="SQL2022_2"/FEATURES=SQLENGINE,REPLICATION,FULLTEX
T,TOOLS /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM"
/AGTSVCACCOUNT="NT AUTHORITY\SYSTEM"/FTSVCACCOUNT= "NT
AUTHORITY\SYSTEM"/SQLSYSADMINACCOUNTS="desktop-lippeoh\kapil"/IACC
EPTSQLSERVERLICENSETERMS

2b.Slipstream command based Quiet(Q) mode


setup.exe /Q /ACTION="Install" /INSTANCEID="SQL2022_4"
/INSTANCENAME="SQL2022_4"
/FEATURES=SQLENGINE,REPLICATION,FULLTEXT,TOOLS
/SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /AGTSVCACCOUNT="NT
AUTHORITY\SYSTEM" /FTSVCACCOUNT= "NT AUTHORITY\SYSTEM"
/SQLSYSADMINACCOUNTS="desktop-lippeoh\kapil"
/IACCEPTSQLSERVERLICENSETERMS

3.INSTALL USING CUI PARAMETER FILE

setup.exe /CONFIGURATIONFILE="C:\018_SQL2022.ini"
SQL 2005 COMMAND BASED INSTALLATION

start /wait setup.exe /qb INSTANCENAME=SQL2005_2


ADDLOCAL=SQL_Engine,Client_Components
SQLACCOUNT="NT AUTHORITY\SYSTEM"
AGTACCOUNT="NT AUTHORITY\SYSTEM"
SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM"
SECURITYMODE=SQL SAPWD=Admin143$$
TROUBLESHOOTING

SQL SERVER 2005 TROUBLESHOOTING

Troubleshooting:
1) Verify Summary.txt file
Check if any components have failed. If any component has failed then check the error message and
search further based on it.

If there is no proper error number/message in the summary file for the component that failed. Then
open the individual log file to troubleshoot further the failed component.

2) Identify any error number of message in the failed component. Alternatively open Individual Log file
and search for
'return value 3'
'ue 3'

When SQL Server installation fails it returns a value 3. Check for errors above and below the return value
3 message. If not much information found in individual log file then the alternate options to look are.
Keyword Search: ERROR, FAILURE and EXCEPTION

3) Verify Core.log and Core(Local).log files to find more information about failed installation.

4) Event viewer can be helpful to identify errors that are related to pre-installation i.e. before installation
starts.
Start->Run-> eventvwr

Common Installation Errors:-

1) Error 1603:
Servers and Tools directories in SQL Server 2005 should be on the same directory level and also the
names should be the same (Cd1, Cd2 and other naming conventions are not accepted).

SQL Server 2005 is sensitive to this path location which is changed later in SQL
2008/2008R2/2012/2014.

KB Article: https://support.microsoft.com/en-in/kb/916760

2) Error 1603:
Error 1603 may also occur if previous un-installation was not clean, when trying to reinstall the sql
server instance the installation may fail.

If you verify Summary.txt file, we get messages like this.


���������������������������
Machine : NODE01
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup001_NODE01_SQL.log
Error Number : 1603
���������������������������

When individual log file is verified, we get more details as below near "Return Value 3".

SQLSetup001_NODE01_SQL.log
=================================================================================
=
MSI (s) (34:E4) [02:35:53:642]: Doing action:
CAResolveInstanceName.68C6D15C_77E0_11D5_8528_00C04F68155C
Action ended 02:35:53: SQLLicensing.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (34:A0) [02:35:53:642]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI32F.tmp, Entrypoint: ResolveInstanceName
Action start 02:35:53: CAResolveInstanceName.68C6D15C_77E0_11D5_8528_00C04F68155C.
FTECa.DLL: INFO: FTE: ResolveInstanceName(), Entering�
FTECa.DLL: INFO: FTE: This is NOT an Exchange Server install�
FTECa.DLL: INFO: ResolveInstanceName: FTEInstName obtained: TMSDERIV_PROD
FTECa.DLL: INFO: ResolveInstanceName: FTERudeInstName obtained: MSSQL.8
FTECa.DLL: INFO: LookupInstanceId: Iterating the key: 1
FTECa.DLL: INFO: LookupInstanceId: Iterating rude name: MSSQL.1
FTECa.DLL: INFO: LookupInstanceId: Iterating the key: 2
FTECa.DLL: INFO: LookupInstanceId: Iterating rude name: MSSQL.2
FTECa.DLL: INFO: LookupInstanceId: Iterating the key: 3
FTECa.DLL: INFO: LookupInstanceId: Iterating rude name: MSSQL.4
FTECa.DLL: INFO: LookupInstanceId: Iterating the key: 4
FTECa.DLL: INFO: LookupInstanceId: Iterating rude name: MSSQL.6
FTECa.DLL: INFO: LookupInstanceId: Iterating the key: 5
FTECa.DLL: ERROR: LookupInstanceId: RegQueryValueEx(RudeName) failed. Err = 2
Action ended 02:35:53: CAResolveInstanceName.68C6D15C_77E0_11D5_8528_00C04F68155C. Return
value 3.
Action ended 02:35:53: INSTALL. Return value 3.
=================================================================================
=

From the error we can see that setup is unable to resolve the GUID
"68C6D15C_77E0_11D5_8528_00C04F68155C". We need to search in registry for this GUID key as it
refers to RegQueryValueEx(RudeName) failed.
So it is not able to identify instance name. So it means there is wrong mapping to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSFTESQLInstMap key and it is not able to identify
GUID.

As a temporary remedy, this key can be renamed as OLD and then re-attempting installation it was
successful.
MSI MSP MISSING SCENARIO
MSI:Microsoft installer
MSP:Microsoft software patch

After installing SQL SERVER 2022 CU13 PATCH


We can fix this by 3 solutions
Solution 1: Repair the SQL Server installation
You should run the repair from the original installation media by using the
following command line:

Repair the common shared components and features first, and then repeat the
command to repair the installed instances. During the process, the setup dialog
box disappears. As long as the progress window doesn't show an error, the
process proceeds as expected. If the installer cache file for a specific component
is missing, the repair process encounters an error.

Solution 2: Use the FixMissingMSI tool


You can download the FixMissingMSI tool from the GitHub repository.
After downloading extract the files and find msi missing exe file.
After fixing this run the sql server it will be succeeded

You might also like