Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server 2012 running on Windwos 2012 won't start Expand / Collapse
Author
Message
Posted Sunday, June 30, 2013 3:56 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, July 10, 2014 11:23 AM
Points: 77, Visits: 123
I've made 2 changes to SQL Server 2012 running on Windows 2012:

Enabled Named Pipes

Changed the max amount of memory allocated to SQL Server from 256 to 240GB.

And now SQL Server won't start. I get the error stating "SQL Server started and then stopped>

The error log reads:

2013-06-30 02:40:36.83 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )

2013-06-30 02:40:36.83 Server (c) Microsoft Corporation.
2013-06-30 02:40:36.83 Server All rights reserved.
2013-06-30 02:40:36.83 Server Server process ID is 1128.
2013-06-30 02:40:36.83 Server System Manufacturer: 'Dell Inc.', System Model: 'PowerEdge R815'.
2013-06-30 02:40:36.83 Server Authentication mode is MIXED.
2013-06-30 02:40:36.83 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2013-06-30 02:40:36.83 Server The service account is 'WORKGROUP\SUPERSCR-300$'. This is an informational message; no user action is required.
2013-06-30 02:40:36.83 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2013-06-30 02:40:36.83 Server Command Line Startup Parameters:
-s "MSSQLSERVER"
2013-06-30 02:40:36.98 Server SQL Server detected 4 sockets with 8 cores per socket and 16 logical processors per socket, 64 total logical processors; using 40 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2013-06-30 02:40:36.98 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2013-06-30 02:40:36.98 Server Detected 262118 MB of RAM. This is an informational message; no user action is required.
2013-06-30 02:40:36.98 Server Using locked pages in the memory manager.
2013-06-30 02:40:36.99 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.00 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.01 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.02 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.03 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.04 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.05 Server Large Page Allocated: 32MB
2013-06-30 02:40:37.06 Server Large Page Allocated: 32MB
2013-06-30 02:40:38.66 Server This instance of SQL Server last reported using a process ID of 5576 at 6/30/2013 2:37:16 AM (local) 6/30/2013 9:37:16 AM (UTC). This is an informational message only; no user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 1: CPU mask: 0x000000000000ff00:0 Active CPU mask: 0x000000000000ff00:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 2: CPU mask: 0x0000000000ff0000:0 Active CPU mask: 0x0000000000ff0000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 3: CPU mask: 0x00000000ff000000:0 Active CPU mask: 0x00000000ff000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 4: CPU mask: 0x000000ff00000000:0 Active CPU mask: 0x000000ff00000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 5: CPU mask: 0x0000ff0000000000:0 Active CPU mask: 0x0000000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 6: CPU mask: 0x00ff000000000000:0 Active CPU mask: 0x0000000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 Server Node configuration: node 7: CPU mask: 0xff00000000000000:0 Active CPU mask: 0x0000000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2013-06-30 02:40:38.66 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.
2013-06-30 02:40:38.66 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2013-06-30 02:40:43.71 Server Failed allocate pages: FAIL_PAGE_ALLOCATION 1
2013-06-30 02:40:43.71 Server
Process/System Counts Value
---------------------------------------- ----------
Available Physical Memory 260836831232
Available Virtual Memory 8412996153344
Available Paging File 295601201152
Working Set 778735616
Percent of Committed Memory in WS 94
Page Faults 202070
System physical memory high 1
System physical memory low 0
Process physical memory low 1
Process virtual memory low 0
2013-06-30 02:40:43.71 Server
Memory Manager KB
---------------------------------------- ----------
VM Reserved 373542104
VM Committed 1654144
Locked Pages Allocated 67620
Large Pages Allocated 800768
Emergency Memory 1024
Emergency Memory In Use 16
Target Committed 245784
Current Committed 1721768
Pages Allocated 65920
Pages Reserved 0
Pages Free 0
Pages In Use 1721256
Page Alloc Potential -1487784
NUMA Growth Phase 2
Last OOM Factor 6
Last OS Error 0
2013-06-30 02:40:43.71 Server
Memory node Id = 0 KB
---------------------------------------- ----------
VM Reserved 373312536
VM Committed 1424608
Locked Pages Allocated 56180
Pages Allocated 54480
Pages Free 0
Target Committed 28496
Current Committed 1480792
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 1 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1640
Pages Allocated 1640
Pages Free 0
Target Committed 28496
Current Committed 34432
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 spid11s Error: 701, Severity: 17, State: 123.
2013-06-30 02:40:43.71 spid11s There is insufficient system memory in resource pool 'internal' to run this query.
2013-06-30 02:40:43.71 Server
Memory node Id = 2 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1632
Pages Allocated 1632
Pages Free 0
Target Committed 28496
Current Committed 34424
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 3 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1632
Pages Allocated 1632
Pages Free 0
Target Committed 28496
Current Committed 34424
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 4 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1632
Pages Allocated 1632
Pages Free 0
Target Committed 28496
Current Committed 34424
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 5 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1640
Pages Allocated 1640
Pages Free 0
Target Committed 34432
Current Committed 34432
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 6 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1632
Pages Allocated 1632
Pages Free 0
Target Committed 34424
Current Committed 34424
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 7 KB
---------------------------------------- ----------
VM Reserved 32768
VM Committed 32788
Locked Pages Allocated 1632
Pages Allocated 1632
Pages Free 0
Target Committed 34424
Current Committed 34424
Foreign Committed 0
Away Committed 0
Taken Away Committed 0
2013-06-30 02:40:43.71 Server
Memory node Id = 64 KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 20
Locked Pages Allocated 0
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLGENERAL (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 1856
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLBUFFERPOOL (node 0) KB
---------------------------------------- ----------
VM Reserved 103975052
VM Committed 524288
Locked Pages Allocated 132
SM Reserved 0
SM Committed 0
Pages Allocated 8
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLQUERYEXEC (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 536
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLOPTIMIZER (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 1120
2013-06-30 02:40:43.71 Server Error: 17300, Severity: 16, State: 1.
2013-06-30 02:40:43.71 Server SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLUTILITIES (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 24
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLSTORENG (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 2080
2013-06-30 02:40:43.71 Server Error: 17312, Severity: 16, State: 1.
2013-06-30 02:40:43.71 Server SQL Server is terminating a system or background task Lockmonitor Task due to errors in starting up the task (setup state 1).
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 48
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 1) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 24
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 2) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 3) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 4) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server SQL Server Audit failed to record the SERVER SHUTDOWN action.
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 5) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 6) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (node 7) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 16
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCONNECTIONPOOL (Total) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 168
2013-06-30 02:40:43.71 Server
MEMORYCLERK_SQLCLR (node 0) KB
---------------------------------------- ----------
VM Reserved 0
VM Committed 0
Locked Pages Allocated 0
SM Reserved 0
SM Committed 0
Pages Allocated 8
Post #1468850
Posted Sunday, June 30, 2013 11:02 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 12:47 AM
Points: 7,005, Visits: 8,451
not from my own experience, but this blog seems to address the same issue, but with SQL2008.
http://mssqlwiki.com/tag/failed-allocate-pages-fail_page_allocation-1/


Johan


Don't drive faster than your guardian angel can fly ...
but keeping both feet on the ground won't get you anywhere

- How to post Performance Problems
- How to post data/code to get the best help


- How to prevent a sore throat after hours of presenting ppt ?


"press F1 for solution", "press shift+F1 for urgent solution"


Need a bit of Powershell? How about this

Who am I ? Sometimes this is me but most of the time this is me
Post #1468878
Posted Sunday, June 30, 2013 12:08 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Thursday, July 10, 2014 11:23 AM
Points: 77, Visits: 123
Thank you. I fixed the issue by reinstalling SQL Server and reattaching databases. I believe the problem was caused by entering the max memory parameter (240MB instead of 240GB) incorrectly.
Post #1468885
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse