Bogus 17883 error messages still appearing in Windows Event Log

  • Sql 2K Sp4 Active/Active on Win 23K RTM

    We had an issue that started at 10:39am yesterday where we started getting the 17883 error on first 1 thread then eventually 5. I was unable to get the threads in question to die so I ended up moving the instance to the 2nd node (which in itself took a dogs age). This seemingly fixed the problems, however the Windows application event log is still (2 hours on) getting the same messages for the same threads with the same context on the same schedulers (the SPID’s however don’t exist – they were valid pre shutdown). I'm not seeing the messages now in the Sql Server Error Log (as I was pre-move), and the last minidump file was from 10:39am yesterday.

    All this leads me to believe that the messages are now bogus. Is it possible however that they've become somehow 'queued' and that's why they're still being written to the application event log?

    We can't reboot the physical servers until tomorrow night so I'm unable to ascertain if that will fix the problem. The other instance that was (and still is) active on the same node is seemingly just fine.

    TIA

    T

  • This was removed by the editor as SPAM

  • An update...

    Even after multiple restarts of the server instances and moving servers from one node to another we were still getting these same error messages. What's more impressive is that we were getting them even though Sql Server wasn't running! Only a reboot seemed to shut the thing up once and for all.

    Only thing I can think off is that there was a another entity (service or whatever) that had perhaps been told of the errors and it was that that was writing to the event log, not stopping even after the problem had been fixed because it hadn't received the correct notification.

    Granted I'm possibly grasping at some nano-sized straws here but I can't think of another explanation for this rather funky behavior...

    T

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

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