Wierd error 17883 after installing SP3

  • Ever since installing service pack 3 I am getting the error:

    The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x03760E28.

    and the message:

    The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x0375EA78.

    I have found the following information via the gift of the google:

    http://www.developersdex.com/sql/message.asp?p=580&ID=%3Cf0c4e9b8%2E0302120215%2E4fdd77f6%40posting%2Egoogle%2Ecom%3E

    Which references the following http://support.microsoft.com/?id=810885

    This doesn't seem to cover my situation as this error is oucuring after a scheduled full DB backup only onto a a couple software mirrored IDE disks (I know software mirroring is a bad idea). It doesn't happen after I backup the transaction log and the DB backups appear to be working although I haven't tried to restore one yet (gulp) though I will soon :). I only do a Full backup once a week and I have not had any problems yet other than the werd messages. Has anyone else seen these?

    Lionel

    Edited by - Lionel on 04/10/2003 05:43:17 AM

  • This was removed by the editor as SPAM

  • I had a problem similar to the knowledgebase article. I called Microsoft, they were helpful and gave me the patch.

    It is happening to me a lot when queries aren't using the right indexes or someone starts a table scan over 400,000,000 records. At least now I get alerted and can help minimize their impact.



    Michelle

  • quote:


    Ever since installing service pack 3 I am getting the error:

    The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x03760E28.

    and the message:

    The Scheduler 1 appears to be hung. SPID 0, ECID 0, UMS Context 0x0375EA78.

    I have found the following information via the gift of the google:

    http://www.developersdex.com/sql/message.asp?p=580&ID=%3Cf0c4e9b8%2E0302120215%2E4fdd77f6%40posting%2Egoogle%2Ecom%3E

    Which references the following http://support.microsoft.com/?id=810885

    This doesn't seem to cover my situation as this error is oucuring after a scheduled full DB backup only onto a a couple software mirrored IDE disks (I know software mirroring is a bad idea). It doesn't happen after I backup the transaction log and the DB backups appear to be working although I haven't tried to restore one yet (gulp) though I will soon :). I only do a Full backup once a week and I have not had any problems yet other than the werd messages. Has anyone else seen these?

    Lionel

    Edited by - Lionel on 04/10/2003 05:43:17 AM


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

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