Results 1 to 2 of 2

Thread: Error 17883

  1. #1
    Join Date
    Jul 2005

    Unanswered: Error 17883

    I have read the other threads that discuss error 17883. I have a SQL 2000 server with SP 3a on a Windows 2000 server SP4. I get the following error in my SQL log...

    Process 429:0 (ad4) UMS Context 0x06BA8D30 appears to be non-yielding on Scheduler 0.

    Then ...

    Error: 17883, Severity: 1, State: 0

    When this error occurs my users are forced to close and reopen the application. Once the users log back in they are good to go.

    I just started getting this error 2 weeks ago about 1 error a week. Now I am getting them everyday...At first I thought it was due to a database Log file autogrow, but my log files haven't gotten autogrown in the last week.

    Has anyone else seen this specific version of Error 17883?

  2. #2
    Join Date
    Dec 2002
    Did you see this article?

    I have never encountered encountered the error myself. I ran on SP3a for quite some time before upgrading to SP4.


    Have you hugged your backup today?

Posting Permissions

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