Upgrade SQL Server 2K to SP4

One of our windows service logged following events

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
17066 :
SQL Server Assertion: File: <rowset.cpp>, line=3260
Failed Assertion = 'm_cILockBytesOpen == 0'

==================================================================

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
18052 :
Error: 1203, Severity: 20, State: 1
Process ID 53 attempting to unlock unowned resource KEY: 11:2041058307:1 (8e02b4254032)

=================================================================

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 1/31/2006
Time: 7:56:04 AM
User: N/A
Computer: blah blah
Description:
Error: 1203, Severity: 20, State: 1
Process ID 53 attempting to unlock unowned resource KEY: 11:2041058307:1 (8e02b4254032)

=================================================================

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:09 AM
User: N/A
Computer: blah blah
Description:
17066 :
SQL Server Assertion: File: <proc.c>, line=1576
Failed Assertion = 'm_activeSdesList.Head () == NULL'.

=================================================================

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17055
Date: 1/31/2006
Time: 7:56:09 AM
User: N/A
Computer: blah blah
Description:
17310 :
SqlDumpExceptionHandler: Process 692 generated fatal exception c000001d EXCEPTION_ILLEGAL_INSTRUCTION.
SQL Server is terminating this process.
=================================================================

I upgraded my SQL 2K instance with SP4 ( previously it was SP 3a) and the problem was resolved.

After few days one of over client's encountered the same problem. I ran SP4 on our client DB server too and problem got resolved.

This problem is not consistant and our other client are not facing this problem (they have SP 3a). Please help me what is the issue.

Thanks in advance



Answer this question

Upgrade SQL Server 2K to SP4

  • JesterSoftware

    Did you ever get these problems resolved

    I am also getting both errors 17066, and 18052.

    As for the L:\ Drive problem, that is not referring to anything from your machines, that is where the source was located when it was compiled by Microsoft.


  • PromemoreX

    One of our customers has also had this problem after an upgrade to SP4 from SP3a.

    Errors:

    Process 115 unlocking unowned resource: KEY: 2:3:1 (1300b341b778)
     
    Error: 1203, Severity: 20, State: 1
     

    Process ID 115 attempting to unlock unowned resource KEY: 2:3:1 (1300b341b778)..

     
    Process 115 unlocking unowned resource: KEY: 2:3:1 (1300b341b778)
     
    Error: 1203, Severity: 20, State: 1
     
    Process ID 115 attempting to unlock unowned resource KEY: 2:3:1 (1300b341b778)..
    *  t e m     $        74 00 65 00 6d 00 00 00 00 00 24 10 10 00 00 00 00 00
     
    Then the service seemed to have tried to start itself again after which the following errors occurred:
     
    Problem creating stack dump file due to internal exception2006-04-05 12:03:09.47 spid88    SQL Server Assertion: File: <L:\sql\ums\inc\umslist.h>, line=311
    Failed Assertion = 'el->m_next == 0'.
     
     
    Problem creating stack dump file due to internal exception2006-04-05 12:03:09.49 spid88    SQL Server Assertion: File: <L:\sql\ums\inc\umslist.h>, line=311
    Failed Assertion = 'el->m_next == 0'.
    --------------------------- 
    One interesting thing is that the L drive referred to in those errors, doesn't exist and their IT guy isn't aware of any time that drive was used.

     



  • Upgrade SQL Server 2K to SP4