SQLSERVER 2008 - SP2 Installation failed by Kevin Auch

Just to comment on the "work around". You can't "reapply" SP2. The installer prevents that. You have to uninstall SP2 first.

The uninstall requires the original media... Which, on a remote server, means I have to download it from MSDN. MSDN is currently offline for "maintenance" whatever the hell that means other than I'm currently hosed.

Can you guys stop screwing around and friggin test these products in real world scenarios? How could you possibly miss "filestream"? It's a pretty big feature. Further, couldn't you just tell people "hey, we see you have filestream enabled. This is going to really screw with your life, so you might not want it."

I have the same problem by upgrade from 9.3.4294 (2005 SP3 PatchSet 9) to 10.50.1600.1.

I found some threads about to deactivate the implicit transaction mode, but it should be allready deactivated. Is 'user options' = '0' correct?


2011-05-23 15:49:27.21 spid7s Error: 15002, Severity: 16, State: 1.
2011-05-23 15:49:27.21 spid7s The procedure 'sys.sp_dbcmptlevel' cannot be executed within a transaction.
2011-05-23 15:49:27.22 spid7s Error: 266, Severity: 16, State: 2.
2011-05-23 15:49:27.22 spid7s Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.
2011-05-23 15:49:27.22 spid7s Executing batch :
-- Allow updates to system catalogs so that we can fully manipulate our system objects
EXECUTE master.dbo.sp_configure N'allow updates', 1
2011-05-23 15:49:27.41 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-05-23 15:49:27.41 spid7s Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install.
2011-05-23 15:49:27.41 spid7s Executing batch :
RECONFIGURE WITH OVERRIDE
2011-05-23 15:49:27.42 spid7s Error: 574, Severity: 16, State: 0.
2011-05-23 15:49:27.42 spid7s CONFIG statement cannot be used inside a user transaction.
2011-05-23 15:49:27.58 spid7s Error: 912, Severity: 21, State: 2.
2011-05-23 15:49:27.58 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 574, state 0, severity 16. 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.
2011-05-23 15:49:27.60 spid7s Error: 3417, Severity: 21, State: 3.
2011-05-23 15:49:27.60 spid7s 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.

Hi,

We got same Issue on having our SP2 on SQl Server 2008.

"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"

Can someone Post the Work around Process.

Thanks in Advance,
Chow

Hi,

i try to desactivate FILESTREAM before to install the SP2 of SQL Server 2008, but i have always the same problem to restart the MSSQL Service.

"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."

Any ideas?

Thx for your help

Hi Robann,

"Please utilize the workaround provided"? I don't see it here.

Thanks,
Steve

Hello,

Thank your for your feedback. We have confirmed that this is a bug and will be fixed in the next release of Sql Server. In the meantime, please utilize the workaround provided. Let us know if you have any further issues.

Thanks
Robann Mateja
Microsoft PM Sql Server

Hi Dave.

I didn't remember we got it for the SP1 :)

So we'll try it soon, I post the result here.

Thanks a lot

Kevin

Let me guess, you have filestream enabled. If so, this is a known bug. Disable it temporarily using sqlservermanager10.msc (copy your mdfs/ldfs/filestream folders first). It should then start. Apply SP2 again. After that you should be OK. I can't find the link to the original issue but the rsfx drivers are mismatched. This happens with SP1 as well.