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

Failed to map 8388608 bytes of contiguous memory Expand / Collapse
Author
Message
Posted Tuesday, December 11, 2012 4:23 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, September 18, 2014 11:16 PM
Points: 363, Visits: 1,321
My customer is running a small e-commerce site on a SQL Server 2008 R2 SP2 Workgroup Edition x64. The SQL Server runs on a Windows Server 2008 R2 Standard x64 SP1 having 12GB RAM. I've allocated a max memory of 5GB to SQL (the min memory is o) and the account used by the SQL Server service has been granted the "Lock pages in memory" right. The database and the site (.NET 2.0 ) are situated on the same machine. The machine has 2 NUMA nodes. I've set the processor affinity to one node for SQL and to the other node for IIS.
Apart from CPU spikes due to a piece of sloppy programming, there seems to be no other area where things are going wrong.
However, this message appears every few days in the SQL error log : "Failed to map 8388608 bytes of contiguous memory". I've found no related error message in the Windows or application logs.
Where should I begin investigating in order to find the cause of this error?
Thank you...
Post #1395026
Posted Tuesday, December 11, 2012 5:31 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, December 13, 2013 4:35 AM
Points: 386, Visits: 211
This was for v2000/2005 - don't know if it still applies
http://support.microsoft.com/kb/903002



Cursors never.
DTS - only when needed and never to control.
Post #1395066
Posted Wednesday, December 12, 2012 6:46 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 9:00 AM
Points: 4,359, Visits: 6,196
dmoldovan (12/11/2012)
My customer is running a small e-commerce site on a SQL Server 2008 R2 SP2 Workgroup Edition x64. The SQL Server runs on a Windows Server 2008 R2 Standard x64 SP1 having 12GB RAM. I've allocated a max memory of 5GB to SQL (the min memory is o) and the account used by the SQL Server service has been granted the "Lock pages in memory" right. The database and the site (.NET 2.0 ) are situated on the same machine. The machine has 2 NUMA nodes. I've set the processor affinity to one node for SQL and to the other node for IIS.
Apart from CPU spikes due to a piece of sloppy programming, there seems to be no other area where things are going wrong.
However, this message appears every few days in the SQL error log : "Failed to map 8388608 bytes of contiguous memory". I've found no related error message in the Windows or application logs.
Where should I begin investigating in order to find the cause of this error?
Thank you...


Usually this is something seen on 32 bit machines and MemToLeave, but you state you are on x64 which usually doesn't have a problem there. But you do have a VERY low max memory set too. I note however that only about twice in 15 years of consulting have I seen valid reasons for messing with processor affinity and something could be screwy with that (and the fact that you have NUMA hardware too).

Are you getting any other errors? Please post the ENTIRE error message. Is this repeatable at/near the same time of day or random? Is this a virtual machine by any chance?

I would watch memory usage of all items on the box and see if you can't increase that max mem setting for SQL Server. You may also want to set up a profiler trace to local disk with rollover files to capture activity during the event. Be sure to delete the files as they stack up to avoid filling up a drive (and do NOT do STMT COMPLETED!!!).

Do you use a lot of XPs, CLR, Full Text, etc?

You may want to consider getting a professional on board for a few hours to give your system a quick review. Lots of potential issues here and it could take you days or weeks of hunt-and-peck forum stuff and still not isolate a cause.


Best,

Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru at GMail
Post #1395643
Posted Thursday, October 31, 2013 1:57 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 19, 2014 7:57 AM
Points: 986, Visits: 1,327
Has there been a definitive resolution to this? I just started getting the same error message. The SQL box is a VM with 8gb memory SS2K8R2 Enterprise SP2 64 bit.

Kurt


Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY

http://www.linkedin.com/in/kurtwzimmerman
Post #1510414
Posted Thursday, October 31, 2013 2:11 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 2:07 PM
Points: 39,883, Visits: 36,230
Are you using the trace flag to enable large pages?


Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1510418
Posted Thursday, October 31, 2013 2:29 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 19, 2014 7:57 AM
Points: 986, Visits: 1,327
No.

Here is the start up:
-dC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf;
-eC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG;
-lC:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf



Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY

http://www.linkedin.com/in/kurtwzimmerman
Post #1510426
Posted Friday, November 1, 2013 12:52 PM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 19, 2014 7:57 AM
Points: 986, Visits: 1,327
Greetings all;
Just an update. I was experiencing issues with the entire application stack so I was able to take advantage of rebooting the SQL Server. It appears to have resolve the "Failed to map 8388608 bytes of contiguous memory" issue.

Kurt


Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY

http://www.linkedin.com/in/kurtwzimmerman
Post #1510764
Posted Monday, November 4, 2013 4:28 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Friday, March 21, 2014 9:46 AM
Points: 387, Visits: 1,078
I am not sure. But could it be a virtual memory related error? Due to disk fragmentation, large memory area for page file can not be allocated!!!!!
Post #1511046
Posted Monday, November 4, 2013 8:32 AM


SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Friday, September 19, 2014 7:57 AM
Points: 986, Visits: 1,327
I'm not sure exactly what the actual cause of the problem was. I presumed that it had to do with the way the VM environment allocated memory.

In the future if I need to make any changes to the maximum server memory I will insure I do it during a maintenance window where I can restart the server.

Thanks for your response.

Kurt


Kurt W. Zimmerman
SR DBA
Lefrak Organization
New York, NY

http://www.linkedin.com/in/kurtwzimmerman
Post #1511138
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse