Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL Server 2005 SP3

Status
Not open for further replies.

mattmontalto

IS-IT--Management
Feb 26, 2010
68
US
Hello all... I am new here and look forward to sharing information with you all as time moves forward... I have a questions regarding SP 3 for SQL 2005.... I am runnig W2003 Svr R2 with clustering and when I first installed SP 3 everything went in except for client components which failed.... I then fixed and issue with MSDTC network access and then reapplied the service pack to Client Components and was successful. However... sqlserve.exe is still reporting that it is v. 2005.90.3042 which indicates that it is still SP 2.... Anyone have any idea as to why or what to do about it.... Thank you in advance for your reading time....

 
In follow up...

I re-read the log files and am led to believe that the cluster I run the Service Pack from has to have some resources running on it... (previously I had moved all the resources over to the other node)... so now the service pack installer is allowing me to update Database and Analysis services, but the update failed claiming: "Error 11009 No Passive Nodes were successfully patched". Any ideals anyone?
 
With SQL 2005 you need to patch from the active node of the cluster. What happens when you run the service pack on the active node?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Thanks for the response mrdenny..... I tried again today to attempt this.... ( I am running it on the active node)... I have 2 servers in the cluster and on the first it failed to update the Database services, but did update the Analysis services when I paused the passive node....

Then I changed active nodes and paused the other one (the one I had just run the update on...) The update failed on both the database and analysis services on this one.

For both of them, the error for the database services is that the "SQL Server setup was unable to add the user NT AUTHORITY\SYSTEM to the local group RCDAOFFICE\SQL Server Agent."

and for the one that failed on Analysis service, the error is that the "SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files (x86)\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"

Both servers are running 64 bit and both have everything else (besides what we are discussing here, showing as being service pack 3)

Any help would be greatly appreciated.... Thanks.. - Matt
 
FOLLOW UP POSTING....

I have now successfully updated both servers to SP3... I had to go into "Services" on both machines and change the "SQL Server Agent" service to be able to log on with a valid domain account (with rights) rather than the local system account.

As for the second error (about the .mof file) I looked for it on the server reporting the error and noticed that it didn't exist, so I copied that file over from the other server that did not have this error and the update of Analysis completed successfully.

I verified that both servers are at SP3 with a sql query and by checking both sqlservr.exe file versions and confirming them to be 2005.90.4035

Solution may seem rather simple now, but, believe me, this was a battle every step of the way.
 
You shouldn't have ever changed the account that the SQL Services run under from a domain account to local system. Running the SQL Server or SQL Agent under the system account in a cluster isn't supported.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
thanks mrdenny.... I actually didnt change that account in the first place. I recently started working here and was not involved in the initial setup.
 
Ah, sounds like someone mucked around with the services before you started leaving you a little time bomb.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top