February 20, 2012 at 3:28 am
Hi guys......
2012-02-20 01:23:29.36 Server Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
2012-02-20 01:23:29.36 Server (c) Microsoft Corporation.
2012-02-20 01:23:29.36 Server All rights reserved.
2012-02-20 01:23:29.36 Server Server process ID is 7300.
2012-02-20 01:23:29.36 Server System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge T110'.
2012-02-20 01:23:29.36 Server Authentication mode is WINDOWS-ONLY.
2012-02-20 01:23:29.36 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\Log\ERRORLOG'.
2012-02-20 01:23:29.36 Server This instance of SQL Server last reported using a process ID of 11508 at 2/20/2012 1:20:36 AM (local) 2/20/2012 9:20:36 AM (UTC). This is an informational message only; no user action is required.
2012-02-20 01:23:29.36 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\DATA\mastlog.ldf
2012-02-20 01:23:29.38 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-02-20 01:23:29.38 Server Detected 4 CPUs. This is an informational message; no user action is required.
2012-02-20 01:23:29.41 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.
2012-02-20 01:23:29.42 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2012-02-20 01:23:29.44 spid6s Starting up database 'master'.
2012-02-20 01:23:29.50 spid6s 1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2012-02-20 01:23:29.50 spid6s 0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2012-02-20 01:23:29.50 spid6s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2012-02-20 01:23:29.54 spid6s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SHAREPOINT'.
2012-02-20 01:23:29.55 spid6s SQL Trace ID 1 was started by login "sa".
2012-02-20 01:23:29.55 spid6s Starting up database 'mssqlsystemresource'.
2012-02-20 01:23:29.58 spid6s The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2012-02-20 01:23:29.70 spid10s Starting up database 'model'.
2012-02-20 01:23:29.70 spid6s Server name is 'MC-SVR-SBS11\SHAREPOINT'. This is an informational message only. No user action is required.
2012-02-20 01:23:29.71 Server The certificate [Cert Hash(sha1) "2858F1C6FE2BFE08122195DBF7C78BBF3743BA46"] was successfully loaded for encryption.
2012-02-20 01:23:29.71 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SHAREPOINT ].
2012-02-20 01:23:29.71 Server Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SHAREPOINT\sql\query ].
2012-02-20 01:23:29.71 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2012-02-20 01:23:29.74 Server The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/MC-SVR-SBS11.modern.local:SHAREPOINT ] for the SQL Server service.
2012-02-20 01:23:29.74 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-02-20 01:23:29.78 spid10s Clearing tempdb database.
2012-02-20 01:23:29.86 spid10s Starting up database 'tempdb'.
2012-02-20 01:23:29.87 spid14s The Service Broker protocol transport is disabled or not configured.
2012-02-20 01:23:29.87 spid14s The Database Mirroring protocol transport is disabled or not configured.
2012-02-20 01:23:29.88 spid14s Service Broker manager has started.
2012-02-20 01:23:29.94 spid13s A new instance of the full-text filter daemon host process has been successfully started.
2012-02-20 01:23:29.96 spid6s Starting up database 'msdb'.
2012-02-20 01:23:30.21 Logon Error: 18401, Severity: 14, State: 1.
2012-02-20 01:23:30.21 Logon Login failed for user 'MODERN\spfarm'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. [CLIENT: <local machine>]
2012-02-20 01:23:30.53 spid6s Error: 3456, Severity: 21, State: 1.
2012-02-20 01:23:30.53 spid6s Could not redo log record (652205:375:26), for transaction ID (0:40920503), on page (1:1275), database 'msdb' (database ID 4). Page: LSN = (652186:109:18), type = 2. Log: OpCode = 3, context 19, PrevPageLSN: (652204:430:150). Restore from a backup of the database, or repair the database.
2012-02-20 01:23:30.53 spid6s Using 'dbghelp.dll' version '4.0.5'
2012-02-20 01:23:30.53 spid6s **Dump thread - spid = 0, EC = 0x000000008030AB20
2012-02-20 01:23:30.53 spid6s ***Stack Dump being sent to C:\Program Files\Microsoft SQL Server\MSSQL10_50.SHAREPOINT\MSSQL\LOG\SQLDump0052.txt
2012-02-20 01:23:30.53 spid6s * *******************************************************************************
2012-02-20 01:23:30.82 spid6s Error: 3313, Severity: 21, State: 2.
2012-02-20 01:23:30.82 spid6s During redoing of a logged operation in database 'msdb', an error occurred at log record ID (652205:375:26). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
2012-02-20 01:23:35.96 spid6s Error: 3414, Severity: 21, State: 1.
2012-02-20 01:23:35.96 spid6s An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2012-02-20 01:23:35.96 spid6s Error: 8355, Severity: 16, State: 1.
2012-02-20 01:23:35.96 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.
2012-02-20 01:23:36.63 spid6s Database 'master' is upgrading script 'sqlagent100_msdb_upgrade.sql' from level 0 to level 2.
2012-02-20 01:23:36.63 spid6s Error: 926, Severity: 14, State: 1.
2012-02-20 01:23:36.63 spid6s Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
2012-02-20 01:23:36.63 spid6s Error: 912, Severity: 21, State: 2.
2012-02-20 01:23:36.63 spid6s Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 926, 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.
2012-02-20 01:23:36.63 spid6s Error: 3417, Severity: 21, State: 3.
2012-02-20 01:23:36.63 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.
2012-02-20 01:23:36.63 spid6s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2012-02-20 01:23:36.67 Server The SQL Server Network Interface library successfully deregistered the Service Principal Name (SPN) [ MSSQLSvc/MC-SVR-SBS11.modern.local:SHAREPOINT ] for the SQL Server service.
Please reply...........thnx
February 20, 2012 at 3:59 am
have you tried to start the SQL Server service with -f startup parameter?
February 20, 2012 at 4:49 am
yes i have started thru -f start up parameters but its prompt the following error while connecting to SQL Management Studio:
TITLE: Connect to Server
------------------------------
Cannot connect to MC-SVR-SBS11\SHAREPOINT.
------------------------------
ADDITIONAL INFORMATION:
Login failed for user 'MODERN\saaz'. Reason: Server is in single user mode. Only one administrator can connect at this time. (Microsoft SQL Server, Error: 18461)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18461&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
thnx......
February 20, 2012 at 4:55 am
Saggy (2/20/2012)
Login failed for user 'MODERN\saaz'. Reason: Server is in single user mode. Only one administrator can connect at this time. (Microsoft SQL Server, Error: 18461)
Please make sure that all other services including SQL Agent are stopped. Then you will be able to connect with it.
February 20, 2012 at 5:00 am
All other services are stopped and SQL Server Agent is disabled.
thnx.......
February 20, 2012 at 5:08 am
Still you are not able to connect? Do you have any third party tool which continuously pings SQL Server? If yes, can you stop the services of that tool also? And could you try starting the SQL Server from CMD & immediately connecting it through the SQLCMD?
February 20, 2012 at 5:12 am
is the user MODERN\saaz a member of the local administrators group on the server?
February 20, 2012 at 5:12 am
Actually SQL Server is generating a file
i.e Current time is 04:06:05 02/20/12.
=====================================================================
BugCheck Dump
=====================================================================
This file is generated by Microsoft SQL Server
version 10.50.2500.0
upon detection of fatal unexpected error. Please return this file,
the query or program that produced the bugcheck, the database and
the error log, and any other pertinent information with a Service Request.
This is SQLDump file.
Saggy......thnx
February 20, 2012 at 5:52 am
These are the event viewer generated issues:
Log Name: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:29 AM
Event ID: 3417
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
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.
Log Name: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:29 AM
Event ID: 912
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
Script level upgrade for database 'master' failed because upgrade step 'sqlagent100_msdb_upgrade.sql' encountered error 926, 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: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:28 AM
Event ID: 8355
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
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.
Log Name: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:28 AM
Event ID: 3414
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
An error occurred during recovery, preventing the database 'msdb' (database ID 4) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
Log Name: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:24 AM
Event ID: 3313
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
During redoing of a logged operation in database 'msdb', an error occurred at log record ID (652205:375:26). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database.
Log Name: Application
Source: MSSQL$SHAREPOINT
Date: 2/20/2012 2:41:24 AM
Event ID: 3456
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: MC-SVR-SBS11.modern.local
Description:
Could not redo log record (652205:375:26), for transaction ID (0:40920503), on page (1:1275), database 'msdb' (database ID 4). Page: LSN = (652186:109:18), type = 2. Log: OpCode = 3, context 19, PrevPageLSN: (652204:430:150). Restore from a backup of the database, or repair the database
Reply..............thnx
February 20, 2012 at 6:45 am
If you are facing this issue just after you applied SP1 you may try to unistall the SP & see what happens. Otherwise, I think you will need to restore the Master from the backup (if you have).
February 21, 2012 at 4:32 am
We do not have any backup of system databases like master ,msdb,model.
Can we rebuild or we have to uninstall the sp1 and try to install it again?
Reply........
February 21, 2012 at 4:44 am
Didn't you perform a full backup of your databases prior to applying the service pack? You can first try to uninstall the service pack & check if you are able to restart the SQL Service after that.
February 22, 2012 at 7:43 pm
Judging from this portion of the log:
"2012-02-20 01:23:36.63 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."
I would go with what DF said and restore the master DB from a backup.
**Ignore this, I hadn't read the entire thread.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply