I recently installed SP on my local 64 bit developer instance of SQL Server 2008 R2. All the install steps reported success, but when I try to start my instance, it will not start. I checked the error log and it seems to be having trouble with one of the upgrade scripts. I'm posting the tail end of the error log contents below. Any help would be much appreciated.
2012-08-31 12:01:05.11 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2012-08-31 12:01:05.11 spid7s Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
2012-08-31 12:01:05.11 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2012-08-31 12:01:07.01 spid7s Signing sps ...
2012-08-31 12:01:07.01 spid7s Dropping existing Agent certificate ...
2012-08-31 12:01:07.02 spid7s DBCC TRACEON 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.
2012-08-31 12:01:07.02 spid7s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2012-08-31 12:01:07.18 spid7s DBCC TRACEOFF 4606, server process ID (SPID) 7. This is an informational message only; no user action is required.
2012-08-31 12:01:07.18 spid7s DBCC execution completed. If DBCC printed error messages, contact your system administrator.
2012-08-31 12:01:07.18 spid7s Error: 537, Severity: 16, State: 3.
2012-08-31 12:01:07.18 spid7s Invalid length parameter passed to the LEFT or SUBSTRING function.
2012-08-31 12:01:07.18 spid7s Error: 912, Severity: 21, State: 2.
2012-08-31 12:01:07.18 spid7s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 537, state 3, 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.
2012-08-31 12:01:07.18 spid7s Error: 3417, Severity: 21, State: 3.
2012-08-31 12:01:07.18 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.
2012-08-31 12:01:07.18 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2012-08-31 12:01:07.65 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/ADAMA-LAPTOP.nrccua-hq.local ] for the SQL Server service.
