Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 2157175 - Last Review: April 17, 2012 - Revision: 3.0
Virtual Address Space (VAS) errors can occur on 32bit SQL Server Editions with a large 'network packet size' configuration
If you configure 'network packet size' to a value of 8060 or greater on a 32bit SQL Server, you may encounter errors related to Virtual Address Space (VAS) pressure such as:
Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 65536
or
2007-09-13 14:53:53.21 Logon      Error: 17189, Severity: 16, State: 1.
2007-09-13 14:53:53.21 Logon      SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: <local machine>]
SQL Server allocates memory for incoming and outgoing network buffers based on the 'network packet size' setting. A value of 8060 or greater causes SQL Server to use multi-page allocations for these buffers. Multi-page allocations on a 32bit SQL Server will consume memory outside the normal buffer pool allocations and requires direct virtual address space allocation. One computers with 2Gb of more of physical memory, virtual address space memory can be a limited resource. If a large number of concurrent connections exist with a large 'network packet size', it will consume this limited resource causing other mulit-page allocations from SQL Server to fail (or in the case of Error 17189 a failure to create a thread).
Consider using a lower 'network packet size' than 8060 or use the -g startup parameter to increase the amount of memory available to SQL Server for mulit-page allocation.
Some applications may set a 'network packet size' value that will override the server configuration value as found in sys.configurations. You can find the value of 'network packet size' for any SQL Server connection by running the following query:
select session_id, net_packet_size from sys.dm_exec_connections
For more information about the products or tools that automatically check for this condition on your instance of SQL Server and on the versions of the SQL Server product, see the following table:
Collapse this tableExpand this table
| Rule software | Rule title | Rule description | Product versions against which the rule is evaluated |
SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA)
| Non-Default network packet size in use
| The SQL Server 2008 R2 Best Practice Analyzer (SQL Server 2008 R2 BPA) provides a rule to detect the use of a large 'network packet size'. The SQL Server 2008 R2 BPA supports both SQL Server 2008 and SQL Server 2008 R2.
If you run the BPA tool and encounter a Warning with the title of Engine -Non-Default network packet size in use , then your SQL Server 2008 or SQL Server 2008 R2 installation has a 'network packet size' as found in sys.configurations (the "value_in_use") greater than 8060 (BPA uses SMO to find the run value of this configuration). This rule will only be checked on 32bit SQL Server Editions (even those running in 64bit operating systems). | SQL Server 2008
SQL Server 2008 R2
|
SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA)
| Non-Default network packet size in use
| The SQL Server 2012 Best Practice Analyzer (SQL Server 2012 BPA) provides a rule to detect the use of a large 'network packet size'.
If you run the BPA tool and encounter a Warning with the title of Engine -Non-Default network packet size in use , then your SQL Server 2012 installation has a 'network packet size' as found in sys.configurations (the "value_in_use") greater than 8060 (BPA uses SMO to find the run value of this configuration). This rule will only be checked on 32bit SQL Server Editions (even those running in 64bit operating systems). | SQL Server 2012
|
APPLIES TO
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Workgroup Edition
- Microsoft SQL Server 2008 Developer
- Microsoft SQL Server 2008 Enterprise
- Microsoft SQL Server 2008 Express
- Microsoft SQL Server 2008 Express with Advanced Services
- Microsoft SQL Server 2008 R2 Datacenter
- Microsoft SQL Server 2008 R2 Developer
- Microsoft SQL Server 2008 R2 Enterprise
- Microsoft SQL Server 2008 R2 Express
- Microsoft SQL Server 2008 R2 Express with Advanced Services
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate