SQL SERVER2000 error

  • Just had a sql server instance die on me. Looking through the log I am seeing

    2008-10-14 10:46:06.21 spid3652 WARNING: Failed to reserve contiguous memory of Size= 65536.

    2008-10-14 10:46:06.23 spid3652 Buffer Distribution: Stolen=13507 Free=132 Procedures=4723

    Inram=0 Dirty=8976 Kept=0

    I/O=0, Latched=200, Other=7828

    2008-10-14 10:46:06.23 spid3652 Buffer Counts: Commited=35366 Target=208400 Hashed=17004

    InternalReservation=510 ExternalReservation=0 Min Free=128

    2008-10-14 10:46:06.23 spid3652 Procedure Cache: TotalProcs=382 TotalPages=4723 InUsePages=92

    2008-10-14 10:46:06.23 spid3652 Dynamic Memory Manager: Stolen=18230 OS Reserved=27728

    OS Committed=27693

    OS In Use=27654

    Query Plan=11183 Optimizer=0

    General=2279

    Utilities=7 Connection=32354

    2008-10-14 10:46:06.23 spid3652 Global Memory Objects: Resource=1898 Locks=60

    SQLCache=72 Replication=2

    LockBytes=2 ServerGlobal=43

    Xact=238

    2008-10-14 10:46:06.23 spid3652 Query Memory Manager: Grants=0 Waiting=0 Maximum=98212 Available=98212

    This just repeats for every spid and left the boxes completely unresponsive. When I look in event viewer I see

    Error: 17803, Severity: 20, State: 4

    Insufficient memory available.

    and

    Error: 17803, Severity: 20, State: 5

    Insufficient memory available

    This box has not had anything changed on it in well over a year and with in about 5 min of these errors appearing in the logs the entire instance became unresponsive. Any ideas of what could have caused this?

    Thanks,

  • jsph152 (10/14/2008)


    This box has not had anything changed on it in well over a year...

    Leaving a MS server alone for a year? There's your problem... 😀

    In any case, do you have SP4 installed?

    http://support.microsoft.com/kb/832674

    _______________
    bkDBA
    0.175 seconds -- 10 year average margin of victory at the Daytona 500
    212 Degrees

  • No this box doesn't have service pack 4. Will have to look into that.

  • this happend to me a few years back... this solved my problem. although we didn't change anything from the sqlserver end, the developement end (.NET) was upgraded.

    http://support.microsoft.com/kb/903002

    check it out.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply