Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- From: BILL T. <BILL T.@xxxxxxxxxxxxxxxx>
- Date: Mon, 23 Mar 2009 17:08:02 -0700
I have a Enterprise edition Server 2003 running the Enterprise Edition of SQL
2005.
I recently upgraded the MS Server 2003 to SP2, we also have the SQL Express
edition loaded on the server to support a Tape Backup Program.
Part of the upgrades, patched the SQL Express edition to SP2. This caused a
known problem with the SQL 2005 Maintenance Wizard, and the fix was
documented to update SQL 2005 to SP2 to correct the .dll that the Express
Edtion SP2 had corrupted.
I had updated two other SQL 2005 servers to SP2 from the Windows Update site
successfully. For this server I downloaded the SP2 file to our network, onto
one of our file servers.
I ran the SQL 2005 SP2 x86 edition patch from the file server. I watched
the entire SP2 load and it seemed to be nearly complete, having updated the
registry, and removed backup files, it then came to the end and gave me a
message: A recent applied update KB921896 failed to install.
I searched the appropriate log and found this one reference to a failure:
MSP Error: 29537 SQL Server Setup has encountered the following problem:
[Microsoft][SQL Native Client][SQL Server]Directory lookup for the file
"D:\temp_MS_AgentSigningCertificate_database.mdf" failed with the operating
system error 21(The device is not ready.).. To continue, correct the problem,
and then run SQL Server Setup again.
I also searched the Application and System event logs and found this
reference to an error: Product: Microsoft SQL Server 2005 - Update 'Service
Pack 2 for SQL Server Database Services 2005 ENU (KB921896)' could not be
installed. Error code 1603. Additional information is available in the log
file C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log.
This log is really long and complex, no simple error to find there.
I have researched many forums but have only found references to having moved
the default location of one of the system databases as the culprit. I have
moved my TEMP DB to a new location, but have left my master, msdn, and model
databases in the default locations.
The error references our (D:) drive as the device that was not ready, but
that is our CD-ROM drive and there was nothing loaded.
I can not find anyway to correct the problem, and or run the update again,
because it thinks it is up-to-date at SP2.
All of my databases are working as expected, the Maintenacne Wizard allowed
me to create a new database maintenance and backup. I can not see any way
that the SQL 2005 server is mis-behaving, yet I am curious about this SP2
update error.
Can anyone help me determine if I have a problem that I need to correct?
Does updgrading to SQL 2005 SP3 solve this problem ( the one that I can not
determine I have ) ?
I can supply the registry keys, etc. that I have seen other forums ask for,
just let me know.
--
Thanks,
Bill T.
.
- Follow-Ups:
- RE: Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- From: "Charles Wang [MSFT]"
- Re: Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- From: Aaron Bertrand [SQL Server MVP]
- RE: Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- Prev by Date: SQL2008 Express managed by machine with SQL2008 Standard?
- Next by Date: Re: Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- Previous by thread: SQL2008 Express managed by machine with SQL2008 Standard?
- Next by thread: Re: Ent MS Svr 2003, Ent MS SQL Svr 2005, SQL SP2 failed at end
- Index(es):
Relevant Pages
|
