Results 1 to 6 of 6
  1. #1
    Join Date
    Sep 2003
    Location
    Assen, Nederland
    Posts
    55

    Thumbs down Unanswered: SQL 7 craches quiently since the cumulative patch 1094...

    Hi there,

    Os/SQL Version:

    Microsoft SQL Server 7.00 - 7.00.1094 (Intel X86)
    May 29 2003 15:21:25
    Copyright (c) 1988-2002 Microsoft Corporation
    Desktop Edition on Windows NT 5.0 (Build 2195: Service Pack 3)


    Now I'm having this trouble of error. There are 2 applications which communicate with this sql server.

    and since applying the cumulative patch/hotfix I'm having this trouble...

    for instance in this case(It crashed twice last week..I was unavailable attending a sql course, but not an admin so couldn't place my questions there but for the next one I will...)

    __________________________________________________ _____

    Using 'xpsql70.dll' version '2000.28.09' to execute extended stored procedure 'xp_msver'.

    /* here starts the trouble..*/

    Process 12 unlocking unowned resource: KEY: 7:309576141:1 (0403aa5b4f98)

    a dump is created then...

    SqlDumpExceptionHandler: Process 18 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

    /* and several of these... */

    Module(sqlservr+2e094a) (LockClass::ReleaseLocks+b0)

    SQL Server Assertion: File: <lckclass.cpp>, line=111
    Failed Assertion = 'm_status == ACTIVE || m_status == ORPHANED'.

    Error: 1203, Severity: 20, State: 1

    Process ID 12 attempting to unlock unowned resource KEY: 7:309576141:1 (0403aa5b4f98)..

    Process 12 unlocking unowned resource: KEY: 7:309576141:1 (0403aa5b4f98)

    Error: 1203, Severity: 20, State: 1

    /* and a series of log info...*/

    SQL Server is aborting. Fatal exception 0 caught.

    And then it crashes...

    I found out that the autoclose option turned on, I set it off and thought that I had solved the issue but this server crash keeps recurring.

    what is going on? Where exactly are the problems? Is the SQL ever going to be reliable to stay up? It's getting pretty hard to locate this issue?

    Thank for your help in advance...

    Tarry

  2. #2
    Join Date
    Sep 2003
    Posts
    522
    run dbcc checkdb('your_database_name') and see if it spits out any errors. if it does post them here for further consideration.

  3. #3
    Join Date
    Sep 2003
    Location
    Assen, Nederland
    Posts
    55
    Have done it several times in the past to no avail.(meaning dbcc checks worked fine)

  4. #4
    Join Date
    Sep 2003
    Posts
    522
    try to sp_lock when the error occurs and see what object is being referenced. you can also run profiler and correlate the time and spid with the av.

  5. #5
    Join Date
    Sep 2003
    Location
    Assen, Nederland
    Posts
    55
    Thanx for the tip. I'll try that but the only thing is the server goes down with out a warning. I can run a profiler but would know where to start and stop as it happens rather unprecedently. I'm configuring it to aviod the lock escalation issue and do all in serial. Using the sp_configure 'max degree', 1.
    Have also called up support for this issue and will be giving them the dump's.

    Thanx again(Will report back if/when issue resolved)

    Tarry

  6. #6
    Join Date
    Sep 2003
    Location
    Assen, Nederland
    Posts
    55

    Thumbs down Nothing worked!!

    It's rather disappointing. Coming form an oracle background I don't see a reason why a SQL server gives up on you.

    Server keeps crashing. Have applied for support already.


    Errors which my netiq trapped were these....

    ************************************************** ***
    Warning: Process status structure (PSS) found with open session descriptor (SDES). PSPID 15, PSUID -1, PCURDB 7, range entry 0, SDESP 0x42a72e0, object ID 949578421.



    Error 9/16/2003 2:43:20 PM MSSQLServer
    Kernel 17055 MSCMS
    17065 :
    SQL Server Assertion: File: <xdesmgr.c>, line = 1844
    Failed Assertion = 'FALSE' Invalid XDES state transition from IDLE to COMMITTING context: 2
    .
    ************************************************** **
    And the infamous locking error...


    17066 :
    SQL Server Assertion: File: <lckclass.cpp>, line=111
    Failed Assertion = 'm_status == ACTIVE || m_status == ORPHANED'.



    Error 9/17/2003 4:35:32 PM MSSQLServer
    Server 17052 MSCMS SQL02
    Error: 1203, Severity: 20, State: 1
    Process ID 12 attempting to unlock unowned resource KEY: 7:309576141:1 (0403aa5b4f98).


    Error 9/17/2003 4:35:32 PM MSSQLServer
    Server 17052 MSCMS SQL02
    Error: 1203, Severity: 20, State: 1
    Process ID 12 attempting to unlock unowned resource KEY: 7:309576141:1 (0403aa5b4f98).


    ************************************************** *****

    Error 9/24/2003 3:24:21 PM MSSQLServer
    Kernel 17055 N/A SQL02
    17066 :
    SQL Server Assertion: File: <lckmgr.cpp>, line=3872
    Failed Assertion = 'lockFound == TRUE'.



    Error 9/24/2003 3:24:21 PM MSSQLServer
    Server 17055 N/A SQL02
    18052 :
    Error: 3624, Severity: 20, State: 1.

    ************************************************** *******

    Or should I convice the management to dump SQL Server...

    anyone who has experience with this.
    Hope that helped...
    Visit My Website : http://www.oraflame.com
    _____________________________
    Tarry Singh

    OCP DBA 8i
    Currently: SQL Server DBA 7,2000
    Oracle, PHP Programmer

Posting Permissions

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