Home All Groups Group Topic Archive Search About

insufficient memory availbele

Author
13 Nov 2007 2:46 PM
pcnetnet
Hi All,
       we have SQL server problem , i don't what reason ? the server is down
, i need restart the server and the event is "Error :17803 Severity :20
State :12 Insufficient memory available " ? i check many option on server ,
but the problem is not fix ???? i try open the SQL Profiler , but stop the
profiler when this error occur. i use PRTG monitor the data, SQL Server
Buffer manager :  page life expectancy . this value is decrease, in no  any
error the value around 200,000 , but occur error insufficient memory
availbele the value decrease to 0 ????? how to check what problem for this
?? not memory ???? HELP

Server : Windows 2003 Ent
Ram : 16GB (enable AWE)
SQL : SQL 2000 SP4

Author
13 Nov 2007 2:55 PM
pcnetnet
for ref. Thanks,


Show quote
"pcnetnet" <pcnet***@yahoo.com.hk> wrote in message
news:OLJv3PgJIHA.4044@TK2MSFTNGP02.phx.gbl...
> Hi All,
>       we have SQL server problem , i don't what reason ? the server is
> down
> , i need restart the server and the event is "Error :17803 Severity :20
> State :12 Insufficient memory available " ? i check many option on server
> ,
> but the problem is not fix ???? i try open the SQL Profiler , but stop the
> profiler when this error occur. i use PRTG monitor the data, SQL Server
> Buffer manager :  page life expectancy . this value is decrease, in no
> any
> error the value around 200,000 , but occur error insufficient memory
> availbele the value decrease to 0 ????? how to check what problem for this
> ?? not memory ???? HELP
>
> Server : Windows 2003 Ent
> Ram : 16GB (enable AWE)
> SQL : SQL 2000 SP4
>
>


[attached file: error.jpg]
Author
13 Nov 2007 2:59 PM
pcnetnet
for ref 2  , Thanks,

Show quote
"pcnetnet" <pcnet***@yahoo.com.hk> wrote in message
news:uARHnUgJIHA.5116@TK2MSFTNGP03.phx.gbl...
> for ref. Thanks,
>
>
> "pcnetnet" <pcnet***@yahoo.com.hk> wrote in message
> news:OLJv3PgJIHA.4044@TK2MSFTNGP02.phx.gbl...
>> Hi All,
>>       we have SQL server problem , i don't what reason ? the server is
>> down
>> , i need restart the server and the event is "Error :17803 Severity :20
>> State :12 Insufficient memory available " ? i check many option on server
>> ,
>> but the problem is not fix ???? i try open the SQL Profiler , but stop
>> the
>> profiler when this error occur. i use PRTG monitor the data, SQL Server
>> Buffer manager :  page life expectancy . this value is decrease, in no
>> any
>> error the value around 200,000 , but occur error insufficient memory
>> availbele the value decrease to 0 ????? how to check what problem for
>> this
>> ?? not memory ???? HELP
>>
>> Server : Windows 2003 Ent
>> Ram : 16GB (enable AWE)
>> SQL : SQL 2000 SP4
>>
>>
>
>
>
>

[attached file: error2.jpg]
Author
14 Nov 2007 6:13 AM
Ed Murphy
pcnetnet wrote:

> for ref. Thanks,

Side note:  Non-text files shouldn't be posted to newsgroups
unless they have "binaries" in the name (there are a handful of
exceptions, but these are not among them AFAIK).  The preferred
method is to post them somewhere else (e.g. web site, newsgroup
with "binaries" in the name) and then post a link here.
Author
13 Nov 2007 8:44 PM
TheSQLGuru
If your server is down may I suggest calling Microsoft Technical Support??
That is the most expedient means of getting back online.

--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.


Show quote
"pcnetnet" <pcnet***@yahoo.com.hk> wrote in message
news:OLJv3PgJIHA.4044@TK2MSFTNGP02.phx.gbl...
> Hi All,
>       we have SQL server problem , i don't what reason ? the server is
> down , i need restart the server and the event is "Error :17803 Severity
> :20 State :12 Insufficient memory available " ? i check many option on
> server , but the problem is not fix ???? i try open the SQL Profiler , but
> stop the profiler when this error occur. i use PRTG monitor the data, SQL
> Server Buffer manager :  page life expectancy . this value is decrease, in
> no  any error the value around 200,000 , but occur error insufficient
> memory availbele the value decrease to 0 ????? how to check what problem
> for this ?? not memory ???? HELP
>
> Server : Windows 2003 Ent
> Ram : 16GB (enable AWE)
> SQL : SQL 2000 SP4
>
>
Author
13 Nov 2007 10:26 PM
Erland Sommarskog
pcnetnet (pcnet***@yahoo.com.hk) writes:
>        we have SQL server problem , i don't what reason ? the server is
> down , i need restart the server and the event is "Error :17803 Severity
> :20 State :12 Insufficient memory available " ? i check many option on
> server , but the problem is not fix ???? i try open the SQL Profiler ,
> but stop the profiler when this error occur. i use PRTG monitor the
> data, SQL Server Buffer manager :  page life expectancy . this value is
> decrease, in no  any error the value around 200,000 , but occur error
> insufficient memory availbele the value decrease to 0 ????? how to check
> what problem for this ?? not memory ???? HELP

It's difficult to say for sure with this small amount of information,
but my guess is that you have a memory leak somewhere. Now, there are
not that very many possbilities to cause a memory leak in SQL Server,
but there are a few:

o  Poorly written extended stored procedures. They live in the same
   memory space as SQL Server, and if they have a memory leak, that
   affects SQL Server as well.
o  The same can be said about OLE objects invoked with sp_OAmethod.
o  Failure to call sp_xml_removedocument to match up with   
   sp_xml_preparedocument.

Since it is very difficult to diagnose this state on a distance, opening
a case with Microsoft, may be faster way to a solution.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
14 Nov 2007 3:11 AM
Pcnetnet
opening a case with Microsoft ??? how to open the case ??? i need pay money
!
Thanks

Show quote
"Erland Sommarskog" <esq***@sommarskog.se> wrote in message
news:Xns99E7EFAB5EB7CYazorman@127.0.0.1...
> pcnetnet (pcnet***@yahoo.com.hk) writes:
>>        we have SQL server problem , i don't what reason ? the server is
>> down , i need restart the server and the event is "Error :17803 Severity
>> :20 State :12 Insufficient memory available " ? i check many option on
>> server , but the problem is not fix ???? i try open the SQL Profiler ,
>> but stop the profiler when this error occur. i use PRTG monitor the
>> data, SQL Server Buffer manager :  page life expectancy . this value is
>> decrease, in no  any error the value around 200,000 , but occur error
>> insufficient memory availbele the value decrease to 0 ????? how to check
>> what problem for this ?? not memory ???? HELP
>
> It's difficult to say for sure with this small amount of information,
> but my guess is that you have a memory leak somewhere. Now, there are
> not that very many possbilities to cause a memory leak in SQL Server,
> but there are a few:
>
> o  Poorly written extended stored procedures. They live in the same
>   memory space as SQL Server, and if they have a memory leak, that
>   affects SQL Server as well.
> o  The same can be said about OLE objects invoked with sp_OAmethod.
> o  Failure to call sp_xml_removedocument to match up with
>   sp_xml_preparedocument.
>
> Since it is very difficult to diagnose this state on a distance, opening
> a case with Microsoft, may be faster way to a solution.
>
> --
> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Author
14 Nov 2007 11:10 AM
Tibor Karaszi
> how to open the case ???

Check the link in the upper right corner of:
http://support.microsoft.com/ph/2855

Show quote
"Pcnetnet" <pcnet***@yahoo.com.hk> wrote in message news:uAxpXwmJIHA.5400@TK2MSFTNGP04.phx.gbl...
> opening a case with Microsoft ??? how to open the case ??? i need pay money !
> Thanks
>
> "Erland Sommarskog" <esq***@sommarskog.se> wrote in message
> news:Xns99E7EFAB5EB7CYazorman@127.0.0.1...
>> pcnetnet (pcnet***@yahoo.com.hk) writes:
>>>        we have SQL server problem , i don't what reason ? the server is
>>> down , i need restart the server and the event is "Error :17803 Severity
>>> :20 State :12 Insufficient memory available " ? i check many option on
>>> server , but the problem is not fix ???? i try open the SQL Profiler ,
>>> but stop the profiler when this error occur. i use PRTG monitor the
>>> data, SQL Server Buffer manager :  page life expectancy . this value is
>>> decrease, in no  any error the value around 200,000 , but occur error
>>> insufficient memory availbele the value decrease to 0 ????? how to check
>>> what problem for this ?? not memory ???? HELP
>>
>> It's difficult to say for sure with this small amount of information,
>> but my guess is that you have a memory leak somewhere. Now, there are
>> not that very many possbilities to cause a memory leak in SQL Server,
>> but there are a few:
>>
>> o  Poorly written extended stored procedures. They live in the same
>>   memory space as SQL Server, and if they have a memory leak, that
>>   affects SQL Server as well.
>> o  The same can be said about OLE objects invoked with sp_OAmethod.
>> o  Failure to call sp_xml_removedocument to match up with
>>   sp_xml_preparedocument.
>>
>> Since it is very difficult to diagnose this state on a distance, opening
>> a case with Microsoft, may be faster way to a solution.
>>
>> --
>> Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se
>>
>> Books Online for SQL Server 2005 at
>> http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
>> Books Online for SQL Server 2000 at
>> http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
>
>
Author
14 Nov 2007 10:41 PM
Erland Sommarskog
Pcnetnet (pcnet***@yahoo.com.hk) writes:
> opening a case with Microsoft ??? how to open the case ??? i need pay
> money

To answer the second part, yes it is very likely that it will cost you
money. If the issue is due to a bug in SQL Server you will be refunded,
but I would not hold it as likely.

And, yes, it costs the money. But having a system that is not running
can also be expensive.

--
Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

AddThis Social Bookmark Button