November 29, 2017 at 3:14 am
Hi All
I have a problem with my server , SQL can't start up.
when I check into error log :
2017-11-29 18:56:15.03 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2017-11-29 18:56:15.03 Server Detected 2 CPUs. This is an informational message; no user action is required.
2017-11-29 18:56:15.06 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.
2017-11-29 18:56:15.09 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2017-11-29 18:56:15.12 spid7s Starting up database 'master'.
2017-11-29 18:56:15.17 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2017-11-29 18:56:15.20 spid7s SQL Trace ID 1 was started by login "sa".
2017-11-29 18:56:15.20 spid7s Starting up database 'mssqlsystemresource'.
2017-11-29 18:56:15.20 spid7s The resource database build version is 10.50.6000. This is an informational message only. No user action is required.
2017-11-29 18:56:16.78 spid7s Error: 601, Severity: 12, State: 3.
2017-11-29 18:56:16.78 spid7s Could not continue scan with NOLOCK due to data movement.
2017-11-29 18:56:16.78 spid7s Error: 945, Severity: 14, State: 2.
2017-11-29 18:56:16.78 spid7s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2017-11-29 18:56:16.78 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2017-11-29 18:56:16.78 spid10s Error: 904, Severity: 16, State: 1.
2017-11-29 18:56:16.78 spid10s Database 4 cannot be autostarted during server shutdown or startup.
2017-11-29 18:56:16.79 spid10s Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information.
What I have done is as below :
1. I changed the service account for SQl FROM NT AUTHORITY\NETWORKSERVICE into LocalSystem -> it doesnt work
2. I assume this is due to CORRUPT mssqlsystemresource , so i replace it with mdf and ldf files taken from other server -> it is doesnt work either
What should I do ?
your feedback is much appreciated
thank you
November 29, 2017 at 3:20 am
Have you confirmed permissions on the mssqlsystemresource files and directory? Ensure NT Service\MSSQLSERVER has full control.
Did you change the service account via services.msc or the SQL Configuration Manager?
Was the copy of the mssqlsystemresource from another SQL 2008 R2 server at the same patch level?
What entries are recorded in the Windows event log also?
Do you have system state backups of the operating system?
November 29, 2017 at 3:33 am
What are the file growth settings and how much free disk space do you have?
😎
November 29, 2017 at 7:32 am
WhiteLotus - Wednesday, November 29, 2017 3:14 AM2017-11-29 18:56:16.78 spid7s Could not continue scan with NOLOCK due to data movement.
2017-11-29 18:56:16.78 spid7s Error: 945, Severity: 14, State: 2.
2017-11-29 18:56:16.78 spid7s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2017-11-29 18:56:16.78 spid7s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
2017-11-29 18:56:16.78 spid10s Error: 904, Severity: 16, State: 1.
2017-11-29 18:56:16.78 spid10s Database 4 cannot be autostarted during server shutdown or startup.
2017-11-29 18:56:16.79 spid10s Problems recording information in the msdb..suspect_pages table were encountered. This error does not interfere with any activity except maintenance of the suspect_pages table. Check the error log for more information.
All was well until the initial lines from your log above. Assuming that you replaced the resource database files from the same patch level , I suggest to check if the resources are exhausted , and permissions as others suggested above.
November 29, 2017 at 5:57 pm
Guys thanks for the responses !
I fixed up the issue . It turns out I restore the wrongmssystemresource db . location should be :
C:\Program Files\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\MSSQL\Binn
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply