Hi There.
I am struggling to get past this problem. There doesnt seem to be much information on the net about this. The last thing i want to do is rebuild the master because there is an awful lot of configuration that i am unaware of. Our sql server 2008 operates in VMWare on a 32 bit instance of windows server version 5.2.3790
The sql server is running visual studio team foundation server 2010.
When the update was rolled ut from WSUS the SQL server SP install failed.
The service starts and stops amost immediately, any connection attempt is futile. Please advise on the best course of action.
The root cause is an unfinished update script
PREINSTMSDB100.SQL
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 5835
Error 5835 is Failed to start CPUs with the mask 0x4 on the system
I made a opy of the Master and performed rebiuld on the master, which worked but lost everything, from Users, through Databases, to jpbs and all custom tweaks are gone. There is no backup to roll back to (dont ask why, its a touchy subject). All i need to do is somehow bypass this upgrade script or fix the issue related to the error. Im almost certain its not a serious one, but i dont know enough about the Core of sql to make the necessary changes.
Any help would be greatly appreciated !
Here is he log
2010-12-16 12:22:16.39 Server Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (Intel X86)
Sep 16 2010 20:09:22
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2)
2010-12-16 12:22:16.39 Server (c) 2005 Microsoft Corporation.
2010-12-16 12:22:16.39 Server All rights reserved.
2010-12-16 12:22:16.42 Server Server process ID is 3476.
2010-12-16 12:22:16.42 Server Authentication mode is MIXED.
2010-12-16 12:22:16.42 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG'.
2010-12-16 12:22:16.42 Server This instance of SQL Server last reported using a process ID of 3612 at 16/12/2010 12:16:53 (local) 16/12/2010 12:16:53 (UTC). This is an informational message only; no user action is required.
2010-12-16 12:22:16.43 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10.SQL2008\MSSQL\DATA\mastlog.ldf
2010-12-16 12:22:16.48 Server initconfig: Warning: affinity mask specified is not valid. Defaulting to no affinity. Use sp_configure 'affinity mask' or 'affinity64 mask' to configure the system to be compatible with the CPU mask
on the system. You can also configure the system based on the number of licensed CPUs.
2010-12-16 12:22:16.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2010-12-16 12:22:16.48 Server Detected 2 CPUs. This is an informational message; no user action is required.
2010-12-16 12:22:16.74 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2010-12-16 12:22:16.93 Server Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only.
No user action is required.
2010-12-16 12:22:17.05 spid6s Starting up database 'master'.
2010-12-16 12:22:17.16 spid6s 6 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2010-12-16 12:22:17.17 spid6s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2010-12-16 12:22:17.17 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2010-12-16 12:22:17.28 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-12-16 12:22:17.35 spid6s SQL Trace ID 1 was started by login "sa".
2010-12-16 12:22:17.37 spid6s Starting up database 'mssqlsystemresource'.
2010-12-16 12:22:17.43 spid6s The resource database build version is 10.00.4000. This is an informational message only. No user action is required.
2010-12-16 12:22:17.64 spid10s Starting up database 'model'.
2010-12-16 12:22:17.66 spid6s Server name is 'VMLCEDEV'. This is an informational message only. No user action is required.
2010-12-16 12:22:18.30 Server A self-generated certificate was successfully loaded for encryption.
2010-12-16 12:22:18.40 spid10s Clearing tempdb database.
2010-12-16 12:22:19.90 Server Server is listening on [ 'any' <ipv4> 1433].
2010-12-16 12:22:19.91 Server Server local connection provider is ready to accept connection on [\\.\pipe\SQLLocal\MSSQLSERVER ].
2010-12-16 12:22:19.91 Server Server named pipe provider is ready to accept connection on [\\.\pipe\sql\query ].
2010-12-16 12:22:19.93 Server Server is listening on [ 127.0.0.1 <ipv4> 1434].
2010-12-16 12:22:19.93 Server Dedicated admin connection support was established for listening locally on port 1434.
2010-12-16 12:22:20.05 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2010-12-16 12:22:20.07 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/vmlcedev.LCE.local ] for the SQL Server service.
2010-12-16 12:22:20.07 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/vmlcedev.LCE.local:1433 ] for the SQL Server service.
2010-12-16 12:22:20.08 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2010-12-16 12:22:20.22 spid13s Starting up database 'msdb'.
2010-12-16 12:22:20.23 spid14s Starting up database 'ReportServer'.
2010-12-16 12:22:20.25 spid15s Starting up database 'ReportServerTempDB'.
2010-12-16 12:22:20.27 Logon Error: 18401, Severity: 14, State: 1.
2010-12-16 12:22:20.27 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2010-12-16 12:22:20.31 spid16s Starting up database 'WSS_Config'.
2010-12-16 12:22:20.32 spid17s Starting up database 'WSS_AdminContent'.
2010-12-16 12:22:20.33 spid18s Starting up database 'WSS_Content'.
2010-12-16 12:22:20.40 spid20s Starting up database 'Tfs_Warehouse'.
2010-12-16 12:22:20.40 spid19s Starting up database 'Tfs_Configuration'.
2010-12-16 12:22:20.40 Logon Error: 18401, Severity: 14, State: 1.
2010-12-16 12:22:20.40 Logon Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: 192.168.5.17]
2010-12-16 12:22:20.46 Logon Error: 18401, Severity: 14, State: 1.
2010-12-16 12:22:20.46 Logon Login failed for user 'LCE\TFSREPORTS'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: 192.168.5.17]
2010-12-16 12:22:20.80 spid10s Starting up database 'tempdb'.
2010-12-16 12:22:21.12 spid21s The Service Broker protocol transport is disabled or not configured.
2010-12-16 12:22:21.12 spid21s The Database Mirroring protocol transport is disabled or not configured.
2010-12-16 12:22:21.17 spid15s Starting up database 'Tfs_DefaultCollection'.
2010-12-16 12:22:21.28 spid21s Service Broker manager has started.
2010-12-16 12:22:21.42 spid18s Starting up database 'Tfs_The Low Carbon Economy'.
2010-12-16 12:22:21.42 spid14s Starting up database 'ProdMailer'.
2010-12-16 12:22:21.56 spid17s Starting up database 'LCE'.
2010-12-16 12:22:21.60 spid16s Starting up database 'DynamicsMigration'.
2010-12-16 12:22:21.61 spid13s 1 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2010-12-16 12:22:21.66 spid13s 0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2010-12-16 12:22:21.66 spid13s Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2010-12-16 12:22:21.82 spid13s Starting up database 'ProdSecurity'.
2010-12-16 12:22:24.44 spid6s Error: 8355, Severity: 16, State: 1.
2010-12-16 12:22:24.44 spid6s Server-level event notifications can not be delivered. Either Service Broker is disabled in msdb, or msdsb failed to start. Event notifications in other databases could be affected as well. Bring msdb
online, or enable Service Broker.
2010-12-16 12:22:26.45 spid6s Database 'master' is upgrading script 'sqlagent100_msdb_upgrade.sql' from level 0 to level 3.
2010-12-16 12:22:26.46 spid6s ----------------------------------------
2010-12-16 12:22:26.46 spid6s Starting execution of PREINSTMSDB100.SQL
2010-12-16 12:22:26.46 spid6s ----------------------------------------
2010-12-16 12:22:26.85 spid6s Setting database option COMPATIBILITY_LEVEL to 100 for database msdb.
2010-12-16 12:22:27.00 spid6s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2010-12-16 12:22:27.00 spid6s Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.
2010-12-16 12:22:27.00 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2010-12-16 12:22:27.01 spid6s Error: 5835, Severity: 16, State: 1.
2010-12-16 12:22:27.01 spid6s Failed to start CPUs with the mask 0x4 on the system.
2010-12-16 12:22:27.01 spid6s Error: 912, Severity: 21, State: 2.
2010-12-16 12:22:27.01 spid6s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 5835, state 1, 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.
2010-12-16 12:22:27.02 spid6s Error: 3417, Severity: 21, State: 3.
2010-12-16 12:22:27.02 spid6s 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.
2010-12-16 12:22:27.02 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2010-12-16 12:22:27.10 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/vmlcedev.LCE.local ] for the SQL Server service.
2010-12-16 12:22:27.10 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/vmlcedev.LCE.local:1433 ] for the SQL Server service.