PATCH ADDING - SQL Server Forums

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2005 Forums

SQL Server Administration (2005)

PATCH ADDING

Author

Topic

pdset
Constraint Violating Yak Guru

310 Posts

Posted - 2011-10-18 : 20:30:41

While it is downloaded and executing the package on the Server OS have gone through all the steps but at the end the SQL Server when checked with VERSION still exposes to be SP2 rather SP4.

Can anyone let me know the general precautions to be taken while adding patch of SP4 to existing environment of SP2 on SQL box.

Thanks in advance.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-18 : 21:26:05

There aren't any general precautions, but it seems your installation hasn't updated all aspects so something failed. Have you tried re-running it after a reboot?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

pdset
Constraint Violating Yak Guru

310 Posts

Posted - 2011-10-18 : 22:37:12

Yep! I have done the 2nd time, but same result.

I have downloaded from MS Site, closed down all activated processes and depended applications. Then Ran the EXE file directly on click where it resided everything went on well asked for Reboot for 'SQL Server Native Client' and 'Client Components', which has done.

But after reboot when checked with @@VERSION shows:
Microsoft SQL Server 2005 - 9.00.2050.00 (Intel X86) Feb 13 2007 23:02:48 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

From the MS site it is clear steps to execute as what I have done above.

Can you deduce where it went wrong.

Thanks

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-18 : 22:47:29

You'll need to open a case with Microsoft to get this resolved.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2011-10-19 : 13:29:41

quote:
Originally posted by pdset

Yep! I have done the 2nd time, but same result.

I have downloaded from MS Site, closed down all activated processes and depended applications. Then Ran the EXE file directly on click where it resided everything went on well asked for Reboot for 'SQL Server Native Client' and 'Client Components', which has done.

But after reboot when checked with @@VERSION shows:
Microsoft SQL Server 2005 - 9.00.2050.00 (Intel X86) Feb 13 2007 23:02:48 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

From the MS site it is clear steps to execute as what I have done above.

Can you deduce where it went wrong.

Thanks

Based on this message - it looks like you have only upgraded the client tools and not the database engine. Are you running the upgrade on your desktop and referencing a server instance of SQL Server?

Jeff

pdset
Constraint Violating Yak Guru

310 Posts

Posted - 2011-10-19 : 18:29:02

Thanks Jeff.

I was just contemplating with the ways and means and got delayed in getting back HERE.

Rightly said I was running this EXE on my Server's Remote Desktop which is accessed from the Data Centre.

Yes Client Tools got upgraded but do I need to go Physically to do this EXE run to get upgrade to SP4, impacting the Database Engine.

Please Suggest, Many Thanks.

jeffw8713
Aged Yak Warrior

819 Posts

Posted - 2011-10-20 : 13:26:41

If you have connected to the server using RDP, and run the service pack on the server - it should give you the options to upgrade all instances and all components on the server.

If you are not given the options to upgrade the database engine, then you most likely have the wrong service pack. There are a couple of possibilities:

1) You have the Express Edition service pack, and the express edition client tools - but the database engine is not an Express Edition.
2) You have an x64 database engine and an x86 service pack (which would allow updating of the x86 components, but not the x64 components).
3) Or, you have an x64 service pack on an x64 machine, with an x86 database engine installed.

There could be other issues, but I would recommend that you check those first.

Jeff

pdset
Constraint Violating Yak Guru

310 Posts

Posted - 2011-10-20 : 19:08:29

From the MS Download Site. Options:

1. SQL Server 2005SP4-kb2463332-IA64-ENU.exe

2. SQL Server 2005SP4-kb2463332-X64-ENU.exe

3. SQL Server 2005SP4-kb2463332-x86-ENU.exe

Option 1 is ruled out in our case and left with 2 and 3.

To distinguish between them: X86 --> exceptionally on C Drive where I can see PROGRAMFILES(x86) then I presume it is needed with OPTION 3.

However, we do have only x64 related to OPTION 2.

So I have downloaded OPTION 2 and striaght on to RDP server copied just RAN and found:

Setup Support Files
MS SQL SERVER
Database Services

SQL Server Native Client
Client Components
SQLXML4
Backward Compatibility
Microsoft SQL Server VSS Writer

(All of the above were accepted for Upgrade).

SUMMARY:

Time: 10/20/2011 16:56:51.937
KB Number: KB2463332
Machine: DHSV-SQLDEV01
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 4
Package Version: 5000
Command-line parameters specified:
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.4.5000 x86
Database Services (MSSQLSERVER) ENU SP4 2005.090.5000.00 x86 ENTERPRISE
SQL Server Native Client ENU 9.00.5000.00 x86
Client Components ENU SP4 9.4.5000 x86 ENTERPRISE
SQLXML4 ENU 9.00.5000.00 x86
Backward Compatibility ENU 8.05.2312 x86
Microsoft SQL Server VSS Writer ENU 9.00.5000.00 x86

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID

**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2463332_sqlrun_sql.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_sqlncli.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2463332_sqlrun_tools.msp.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 2312
Product Version (Final) : 2312
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 5000
Product Version (Final) : 5000
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB2463332_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------

**********************************************************************************
Summary
Success
Exit Code Returned: 0

Later, Obvious REBOOT of the Server and still found like this. on @@VERSION.

Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86) Dec 10 2010 10:56:29 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
And the Plaform being x86.

Later Checked for any Running processes were STOPped.

Later Installation has been progressed.

Still Unsure where it went wrong or is it ambiguity.

Please anlayse thanks.

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-20 : 19:27:42

You need to download and install the x86 version as your @@VERSION shows x86.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog

pdset
Constraint Violating Yak Guru

310 Posts

Posted - 2011-10-20 : 19:36:57

Otherwise I have used X86 as the OPTION.

Were the STEPS which I followed Correct?

Thanks

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2011-10-20 : 19:45:08

They seem fine, but your post is very long and hard to read.