Results 1 to 5 of 5
  1. #1
    Join Date
    Feb 2007
    Posts
    71

    Unanswered: Fatal exception c0000005 caught / EXCEPTION_ACCESS_VIOLATION

    Hi,

    I want to share an experience

    Here are our server specs:
    Intel Xeon 3.40Ghz [Duo]
    4 Gb Memory
    Raid 1 120Gb HDD
    Windows 2000 Server
    SQL Server 2000 Enterprise Edition


    we tweaked the configuration in sp_configure

    changed the following parameters
    sp_configure 'max server memory (MB)',3000
    go
    reconfigure with override
    go
    --old value: 2002


    sp_configure 'min server memory (MB)', 2500
    go
    reconfigure with override
    go
    --old value: 2048

    sp_configure 'open objects', 2147000000
    go
    reconfigure with override
    go
    --old value: 2147483647

    sp_configure 'awe enabled', 1
    go
    reconfigure with override
    go
    --old value: 0

    sp_configure 'max worker threads', 255
    go
    reconfigure with override
    go
    --old value: 255

    shutdown the database and out came this:

    * Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION
    * Access Violation occurred writing address 00000008
    *
    ************************************************** *****************************
    * -------------------------------------------------------------------------------
    * Short Stack Dump
    * 00408E8B Module(sqlservr+00008E8B)
    * 00408F5E Module(sqlservr+00008F5E)
    * 00409056 Module(sqlservr+00009056)
    * 00408E5E Module(sqlservr+00008E5E)
    * 004020A8 Module(sqlservr+000020A8)
    * 00401FCB Module(sqlservr+00001FCB)
    * 00572114 Module(sqlservr+00172114) (SQLExit+0000A61D)
    * 005655FD Module(sqlservr+001655FD)
    * 7C2DCF43 Module(ADVAPI32+0000CF43) (GetNamedSecurityInfoW+000000E6)
    * -------------------------------------------------------------------------------
    2007-02-27 13:08:53.43 server Stack Signature for the dump is 0x0323EE71
    2007-02-27 13:08:53.43 server SQL Server is aborting. Fatal exception c0000005 caught.

    -------------------------------------------------------------------------------



    database won't start, what we did was to start the sql server with -f parameter and went back to the old settings

  2. #2
    Join Date
    May 2004
    Location
    Seattle
    Posts
    1,313
    are you up to date on service packs? if so I would report this to ms. if not, you might try bringing both sql server and the OS up to date.

    it appears from the callstack that the AV is occuring in advapi32.dll, which is part of the OS.

  3. #3
    Join Date
    Feb 2007
    Posts
    71
    oh sorry, forgot about that ...

    our OS and DB had been updated to SP4

    When I asked my friend about this, he told me that setting the open objects to a high value has caused it to terminate abnormally.

  4. #4
    Join Date
    May 2004
    Location
    Seattle
    Posts
    1,313
    well, that may be, but an AV is unacceptable. any time a server app is AV'ing it's a serious issue, I think MS would want to know about it.

  5. #5
    Join Date
    Feb 2007
    Posts
    71
    ok, i'll take that in mind. thank you very much

Posting Permissions

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