Results 1 to 5 of 5
  1. #1
    Join Date
    Dec 2004
    Posts
    2

    Unanswered: Not able to connet to SQLServer- Memory related messages in SQL Errorlog

    Hi
    I was not able to connect to SQL Server machine. On examining the Error log (which was huge 53MB), I found the following messages that filled 95% of the logfile. Is this something to do with memory allocation.

    Someone, please let me know what is going on. After the server reboot everything works fine.
    I am worrired that this message may occur again.

    Thanks
    Machilu

    2004-11-30 20:15:03.64 logon Login failed for user 'NT AUTHORITY\SYSTEM'

    2004-12-01 08:15:03.77 logon Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.


    2004-12-01 00:47:25.28 spid70 WARNING: Failed to reserve contiguous memory of Size= 65536.
    2004-12-01 00:47:25.31 spid70 Buffer Distribution: Stolen=127590 Free=4176 Procedures=182443
    Inram=0 Dirty=14180 Kept=0
    I/O=0, Latched=154, Other=10049
    2004-12-01 00:47:25.31 spid70 Buffer Counts: Commited=338592 Target=338592 Hashed=24383
    InternalReservation=357 ExternalReservation=0 Min Free=256
    2004-12-01 00:47:25.31 spid70 Procedure Cache: TotalProcs=66212 TotalPages=182443 InUsePages=88547
    2004-12-01 00:47:25.31 spid70 Dynamic Memory Manager: Stolen=310033 OS Reserved=38512
    OS Committed=38457
    OS In Use=38388
    Query Plan=332158 Optimizer=0
    General=15540
    Utilities=8 Connection=473
    2004-12-01 00:47:25.31 spid70 Global Memory Objects: Resource=10685 Locks=119
    SQLCache=4540 Replication=2
    LockBytes=2 ServerGlobal=45
    Xact=201
    2004-12-01 00:47:25.31 spid70 Query Memory Manager: Grants=0 Waiting=0 Maximum=92118 Available=92118
    2004-12-01 00:50:04.10 logon Login failed for user 'NT AUTHORITY\SYSTEM'.
    2004-12-01 00:50:04.32 logon Login failed for user 'NT AUTHORITY\SYSTEM'.
    2004-12-01 00:51:08.78 spid70 WARNING: Failed to reserve contiguous memory of Size= 65536.
    2004-12-01 00:51:08.82 spid70 Buffer Distribution: Stolen=138829 Free=5944 Procedures=169283
    Inram=0 Dirty=14431 Kept=0
    I/O=0, Latched=154, Other=9951
    2004-12-01 00:51:08.82 spid70 Buffer Counts: Commited=338592 Target=338592 Hashed=24536
    InternalReservation=360 ExternalReservation=0 Min Free=256
    2004-12-01 00:51:08.82 spid70 Procedure Cache: TotalProcs=67783 TotalPages=169283 InUsePages=76116
    2004-12-01 00:51:08.82 spid70 Dynamic Memory Manager: Stolen=308112 OS Reserved=38512
    OS Committed=38457
    OS In Use=38398
    Query Plan=330249 Optimizer=0
    General=15535
    Utilities=8 Connection=476
    2004-12-01 00:51:08.82 spid70 Global Memory Objects: Resource=10685 Locks=118
    SQLCache=4540 Replication=2
    LockBytes=2 ServerGlobal=45
    Xact=202

  2. #2
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    Do you use the sp_OA* procedures? Or a custom built ODBC driver?

    http://support.microsoft.com/kb/282229/EN-US/

  3. #3
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    Well, this relates only to a virgin built. I hope they are running at least 760. This may relate to memtoleave, but the poster didn't even mention the total memory size, nor what the built is, as well as edition of OS and SQL...Kinda sitting in the dark and trying to guess
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

  4. #4
    Join Date
    Dec 2004
    Posts
    2
    rdjabarov,

    Here is the SQL Server Machine configureation:
    OS: Windows 2000 5.00.2195 SP4, CPU intel Xeon 2.2 GHz , 8GB RAM
    DBMS: SQL Server 2000 Enterprise Edition + SP3a

  5. #5
    Join Date
    Jul 2003
    Location
    San Antonio, TX
    Posts
    3,662
    The default memtoleave for SQL2K is 256MB. You can increase it by starting the service with -g512 or higher. Make sure to enable AWE to ensure that this switch will not eat up your BPool memory as well.
    "The data in a record depends on the Key to the record, the Whole Key, and
    nothing but the Key, so help me Codd."

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •