August 8, 2008 at 4:49 pm
Hi All,
I was having 9.0.0.1399 RTM version of sql server 2005. Recently we planned to upgrade our server to SP2. I applied that patch and after installing that summary report is showing that successfully upgraded to SP2. But when i check the object browser it is still showing 9.0.0.1399 RTM version. I think when we apply the SP2 , client tools should also be updated. Or is there any other way to update the client tools.
Please help it is really urgent. Please provide link if available to update the client tools.
Thanks all in advance.
Zombi
August 8, 2008 at 5:26 pm
Are you talking about the About window in SSMS showing the RTM version? Or, are you looking at the connection in Object Explorer? If the latter, then - you are either connected to the wrong instance or the upgrade did not upgrade the database system.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 9, 2008 at 7:41 pm
Hi Jeff,
Thank You for ur reply. I am talking about the sql server management studio. When i applied the sql server SP2 to the SQL server 2005 RTM version it's upgrade the system and if you know then at last it shows the summary.txt which shows the report. It is showing that sql server has been successfully upgraded to the SP2. After when i open the SSMS, and look at the instance, next to it it was showing 9.0.0.1399 which means RTM version. Then i connect to the object browser then at the bottom it was showing that 9.0. RTM in the query window. So this means that clinet tools has not been upgraded.
I don;t understand that what is the problem.? can anyone please help me to solve this issue? I wan to upgrade it to 9.0.0.3042 which means sql server 2005 SP2. Is there a special way to upgrade the client tools to SP2. Because when i install the SP2 patch if was not showing the client tools in to it?? i don't know why......!
Please help. Thank you in advance...:)
August 9, 2008 at 8:04 pm
To upgrade your client tools, you need to run the service pack upgrade on your PC. You validate that the client tools have been upgraded by going to Help | About. This will tell you what version your client tools are.
When you connect to a database in Object Explorer - the numbers next to the server name will show you what version that database is. If that is not 9.0.3042 - then the server has not been upgraded.
BTW - you need to upgrade to at least 9.0.3054 because the version 9.0.3042 had problems with maintenance plans. If possible, you should be looking to upgrade to CU6/7 or 8.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 10, 2008 at 2:28 pm
I had the simmilar problem in SQL Server Express Edition and this is because of conflicts on the Microsoft provided msi.
After the SP2 is introduced this is not compatible with Express Edition and thus Microsoft provided 2 versions
Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 2
Microsoft SQL Server 2005 Express Edition with Advanced Services
Thus with Advanced Services, when u apply SP2 executable the database services do not get upgrade to SP2 although it is successful.
To get rid of all this, I have uninstalled everything that says SQL Server with the below link and applied the Advanced Services Service Pack 2
http://support.microsoft.com/kb/290301
Thanks,
Ganesh
August 12, 2008 at 5:40 pm
Hi jeff,
I again applied the service pack 2 to my sql server 2005 enterprise edition (x64) but still it is showing the 9.00.1399 (RTM) version. Not 9.0.0.3042. What should be the problem? I restarted the server and service still it is the same..........9.00.1399.
And one more thing which is makes me suspicious is when i right click on this instance the options for START, STOP, PAUSE, RESTART, RESUME are greyed out, which is not for the other server and the signal in front of the instance should be green as usual but it is showing plain white symbol. why this can be?
I am using microsoft windows server 2003 R2 enterprise x64 edition service pack 2 as operating system.
What should be the problem? please help it is very urgent....Thanks in advance.
Zombi
August 12, 2008 at 8:44 pm
By any chance, are you trying to upgrade a clustered instance of SQL Server? You will see the white icon next to a clustered instance instead of the normal green icon.
If you are, verify that you are connecting to the active node for SQL Server and that your cluster configuration is correct.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 12, 2008 at 10:21 pm
hi Jeff,
Thanks for you reply. How can i identify that it is cludtered? and if it is then how can i connect to the active node???????? can you please explain me some steps and what to do in these situation and upgrade my system to sp2?
Thank you very much in advance.
Zombi
August 13, 2008 at 9:52 am
When you RDP into the server with the SQL Server name - do you connect to a machine with a different name? For example, if you RDP to a server named SERVERA - do you end up connecting to SERVERA01?
If so, then open Cluster Administrator on the server. If you are prompted for a server name, enter the server name you logged in to. If the cluster service is started it will connect - if it is not started on that server you will get an error.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 13, 2008 at 6:00 pm
Hi jeff,
I am connecting to the same server as it is displayed. so I don't think that should be a problem. And what do u think about those START, STOP, RESTART , RESUME greyed out services. I can able to handle these only throught the Administrative tools-> services.
I opened the cluster admin and tried to connect to the server but it was showing that it is not configured or enabled. We have gone live with this server so i don't think there is a problem.
Waiting for ur reply. Thank you very much in advance.
Zombi
August 13, 2008 at 10:57 pm
Not sure about why those options are greyed out. Normally, I see those options greyed out when I have the server setup in the registered servers list, but can't connect to the server because of networking issues.
Again, if the instance you are connecting to in SSMS Object Explorer has a white icon - it usually means that instance is clustered (at least that is what I see on my systems).
When you run the service pack update - it should show you the instance(s) available to be updated on that server and all of the components that can be updated. If you select one that has already been updated - it will tell you that component has already been updated.
Are you seeing the instance being available for upgrading? If so, are you checking the box next to that instance to select it to be upgraded? I know this sounds like a stupid question - but I have to ask just to be sure 😉
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 14, 2008 at 12:26 am
Hi Jeff,
When i am trying to update the sql server with sp2 it is not showing me the instance i want to upgrade it just shows the screen shot that it is searching for the instance to upgrade and then it tells welcome to the sql server 2005 sp2 setup.This installation provides updates for sql server 2005.
Then it does show me the services i want to upgrade like,
-setup Support Files
-sql server native client
-msxml 6.0 parser
-sqlxml4
-backward compatibility
-microsoft sql server vss writer
I tick all of this then it does the installation.
Then after it shows me summary report like this
KB Number: KB921896
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x64
Package SP Level: 2
Package Version: 3042
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.2.3042 x64
SQL Server Native Client ENU 9.00.3042.00 x64
MSXML 6.0 Parser ENU 6.10.1200.0 x64
SQLXML4 ENU 9.00.3042.00 x64
Backward Compatibility ENU 8.05.2004 x64
Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64
**********************************************************************************
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): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlncli.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 1200
Product Version (Final) : 6.10.1129.0
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_msxml6.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_sqlxml4.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 2004
Product Version (Final) : 2004
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SQLServer2005_BC.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 3042
Product Version (Final) : 3042
Status : Success
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB921896_SqlWriter.msi.log
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
**********************************************************************************
Summary
Success
Exit Code Returned: 0[/color]
After this when i check the SSMS it is 9.00.1399 (RTM) version.:( Please find something.
August 14, 2008 at 6:09 am
Two ways to check the level if you have not already tried.
In the Query tool enter select @@Version.
In Management Studio open up the SQL Server errorlog. In there somewhere close to the beginning it will tell you the version/release of SQL Server it is running also.
August 14, 2008 at 12:51 pm
Okay, let's go all the way back to the beginning. Where are you seeing that the version is 9.0.1399 (RTM)?
If this is in Help | About for SSMS - then, you have a problem with the upgrade.
If this is in Object Explorer when connected to an instance of SQL Server - then, you do not have a problem. You are not running the upgrade on that server, therefore, you are not upgrading the SQL Server instance - only the client tools on your desktop.
To apply the service pack to the instance, you have to log into the server (RDP) and run the service pack from the server. When you ran this - it did not show the database service as an option to be upgraded. That means there is no SQL Server on that system that can be upgraded to service pack 2.
I will repeat this again: the server you are logged into does not have an instance of SQL Server 2005 running on it. If it did, the service pack would have listed that instance and shown that it was already upgraded. It will show up - but you will not be able to select it.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
August 14, 2008 at 12:58 pm
BTW - reviewing the summary will show you that this server does not have the database engine installed.
Time: 08/13/2008 08:59:36.608
KB Number: KB921896
Machine: DPPSQL5
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 2 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x64
Package SP Level: 2
Package Version: 3042
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.2.3042 x64
SQL Server Native Client ENU 9.00.3042.00 x64
MSXML 6.0 Parser ENU 6.10.1200.0 x64
SQLXML4 ENU 9.00.3042.00 x64
Backward Compatibility ENU 8.05.2004 x64
Microsoft SQL Server VSS Writer ENU 9.00.3042.00 x64
**********************************************************************************
Under Products Detected - the database engine is not listed. Therefore, no database engine is installed on this server.
Looking at the server name (DPPSQL5), I would guess that this is currently a non active node in a cluster. I am guessing that based upon the naming convention which has a 5 at the end. What and where are DPPSQL1/2/3/4?
Again, just guessing - but is the actual instance name something like DPPSQL (no number)?
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
Viewing 15 posts - 1 through 15 (of 28 total)
You must be logged in to reply to this topic. Login to reply