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.
Author |
Topic |
LA768
Starting Member
9 Posts |
Posted - 2007-06-30 : 22:16:14
|
I tried to install "Cumulative update package 2 for SQL Server 2005 Service Pack 2"Everything went well except for the "SQL Server Database Services" update.It errored out as it was trying to "Finalize" the update.Kicker to this whole thing is the database file "temp_MS_AgentSigningCertificate_database.mdf" does not even exist.I could not see any references to it in the master database. I checked the registry and I can find a couple of search references for it.It apparently may have been a database that existed in the server at one time.I am not sure if I should remove the registry references to the database.Below is a part of the install summary where it has failed:===========================================================Product Installation StatusProduct : SQL Server Database Services 2005 (MSSQLSERVER)Product Version (Previous): 3050Product Version (Final) : Status : FailureLog File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB936305_sqlrun_sql.msp.logError Number : 29537Error Description : MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]A file activation error occurred. The physical file name 'F:Data\temp_MS_AgentSigningCertificate_database.mdf' may be incorrect. Diagnose and correct additional errors, and retry the operation.. To continue, correct the problem, and then run SQL Server Setup again.If someone can tell me what I need to do to resolve this issue, I would greatlyappreciate it.Thanks,Larry :-(Larry :-) |
|
LA768
Starting Member
9 Posts |
Posted - 2007-07-05 : 20:45:32
|
Solved it!I changed the "Database Default Locations" to the default and it worked.I can only think of one reason for this. The "Database Default Locations" shouldbe set to the locations at the time SP2 was installed since KB936305 is just anupdate to SP2 SQL Server 2005.Hope this helps someone in the future.Thanks,Larry :-) |
 |
|
rosponda57
Starting Member
1 Post |
Posted - 2008-07-25 : 05:55:37
|
Hi,I got the same problem. But the worst of this it that when i changed the Default DB location i run the SQL-SP2 setup again it doesn't want to install - it says that SP is allready installed.....Dou You know what to do now? |
 |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-07-26 : 21:22:57
|
That's right, sql will not apply sp2 again if you applied it before. |
 |
|
ss2005variant
Starting Member
2 Posts |
Posted - 2009-01-14 : 18:15:53
|
quote: Originally posted by LA768 Solved it!I changed the "Database Default Locations" to the default and it worked.I can only think of one reason for this. The "Database Default Locations" shouldbe set to the locations at the time SP2 was installed since KB936305 is just anupdate to SP2 SQL Server 2005.Hope this helps someone in the future.Thanks,Larry :-)
Larry, thanks so much for this info! I searched and searched and couldn't find why I couldn't update from SP2 to SP3 and it was for this same reason. -Doug |
 |
|
|
|
|