April 18, 2007 at 7:38 am
Hi All,
We have a Production Server running with following configuration.
OS:Windows Server 2003 Enterprise Edition SP1 (Version 5.2.3790 Service Pack 1 Build 3790)
SQL Server:Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) SP4
CPU:4 x Intel Pentium 4 Xeon Processors with HT
RAM: 8GB
** /PAE switch not on boot.ini file but PAE Enabled and machine/OS detect 8GB RAM
** AWE is not switched ON at the moment
On the SQL Server Error Log and Windows Event Log following two errors appear very frequently
Error: 17805, Severity: 20, State: 3
Invalid buffer received from client.
Error: 17803, Severity: 20, State: 12
Insufficient memory available.
Very recently we're getting at least 40-50 such errors per day. Could anyone can shed light on this matter,
any help is greatly appreciate.
Thilina
April 18, 2007 at 8:31 am
Check the available memory for SQL Server.
For SQL server to take more than 4GB of RAM AWE should be enabled using'
sp_configure 'show advanced options', 1RECONFIGUREGOsp_configure 'awe enabled', 1RECONFIGUREGO
For AWE to take effect you should restart the SQL Server.
Next configure the memory.
sp_configure 'min server memory', <New Value>
RECONFIGUREGOsp_configure 'max server memory', <New Value>RECONFIGUREGO
April 19, 2007 at 3:20 am
Your problem appears to be lack of memory for client connections. How many concurrent connections do you need to support? You may be able to fix this by changing some of your memory parameters, or you may need specialist help from MS. If MS get your system stable, it will be worth the small amount they charge for opening a problem.
For an 8 GB box you should normally have /3GB and /PAE in boot.ini. Some hardware provides built-in PAE support, but it may be best to specify the flag in boot.ini. You should also turn on AWE in SQL, and configure max memory to use about 70% to 80% of your 8 GB. You should also look at the parameters governing connection memory, and adjust these as required.
If you are getting a very high (000s) of connections, it simply may not be able to fit in a 32-bit box, as all connection memory has to live below the 4 GB line. As your hardware seems to be recent, it should support 64-bit - you may need to go to W2003 64-bit and SQL 2005 64-bit to get your system stable.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
April 19, 2007 at 9:35 am
Hello,
It looks like you are running build 2039. IIRC that build (Base SP4) has the AWE bug. So it probably needs 2040 or later.
April 19, 2007 at 9:47 pm
But AWE is not enabled in my machine. Anyway I'm planning to enable it as suggested and see the way server is behaving. Is 2040 hotfix?
April 20, 2007 at 2:31 am
You can get an update to SP4 that just includes the 2040 hotfix. However you should also consider moving to the latest post SP4 hotfix rollup (build 2187). Google will find you articles describing the contents of 2040 and 2187, and you can decide what option is best for your installation. (We run 2187 and have had no issues.)
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply