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 |
agdavidson
Starting Member
17 Posts |
Posted - 2010-07-26 : 15:25:39
|
I have a database server running Server 2008 R2 x64, with SQL Server 2008 SP1 (build 10.0.2531). We have not applied any updates since SP1 and need to get the SQL build up to 10.00.2775 (using Cumulative Update 8 for Sql Server 2008 SP1 - http://support.microsoft.com/kb/981702). I have tried installing the update several times, and each time it fails with a vague error. (About to retry the install and comment with the exact error.) Any ideas? I've never had a problem installing a service pack or CU before and I am not sure what to do!? I will keep digging, but was hoping that maybe someone else had run into this same problem and already knows what to do about it... |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
agdavidson
Starting Member
17 Posts |
Posted - 2010-08-04 : 16:58:49
|
Sorry it's taken me so long to get back to this thread... Here is the exact failure text, though.After install, installer says that CU8 completed successfully and that I need to reboot. However... Windows Event Viewer shows two errors as a result of the installation attempt.Log Name: ApplicationSource MSSQLServerEventID: 912Level: ErrorUser: N/AGeneral:Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 598, state 1, severity 25. This is a serious error condition which might interfere with regular operation and the database will be taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database so that the script upgrade steps run to completion.Log Name: ApplicationSource MSSQLServerEventID: 3417Level: ErrorUser: N/AGeneral:Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL Server Books Online.In my experience, the server is screwed at this point. We've been trying these install attempts on a copy of our dev server, so we haven't felt the need to go as far as to attempt to repair or fix master (it's a VM with snapshots that allow us to roll everything back to a point in time before the install attempt)... we feel like we should never even encounter this problem, so no sense in trying to fix the aftermath of it. However, we have tried taking the same VM, uninstalling SQL Server 2008 and then reinstalling SQL Server 2008 again with the standard/default options . This works, which indicates that the install is failing because of some option we turned on, location we placed files, etc. ? Any ideas where to go from here? |
 |
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
agdavidson
Starting Member
17 Posts |
Posted - 2010-08-06 : 14:15:12
|
That's actually the route we ended up going. Unfortunately, they can't figure it out either. It's been several days of long calls with the engineer assigned to the case and we're still at square one - neither CU8 nor CU9 will apply. We have, however, been able to rule out the following possible causes:a) Default data directories do not exist on the server as they are listed in instance options, or data directory exists but does not match actual MDF storage location (three reg keys tie in here, tried all three)b) SA account renamedc) Implicit transactions turned on in server-level connection optionsI'll keep updating the thread as we find more... would hate for someone else to have to trudge through all this again! |
 |
|
|
|
|
|
|