MountainNetworks
IS-IT--Management
- Apr 24, 2003
- 74
- 0
- 0
This is probably more of a rant, rather than a question.
I've got this client with a workstation that's been giving some problems. So what do you do? You check the event viewer. Now we all know that not all errors are really erros, and not all warnings are worth warning about. A standard case of too much information.
But what do you do with these obscure event ID errors that all searches turn up "not found"?
My latest example is this "Srv" error. Something about some non-paged pool crying about something. I don't have the actual event in front of me. But basically, it's Srv Event ID 2017. Tecnet had 2015 and other 201x errors that related to the same error, but not this specific ID.
Isn't there some database somewhere that catalogues these events? Somebody has to sit there and write them, and procedures to call them based on certain conditions. Where is this magical "phone book" of event log messages?
I've got this client with a workstation that's been giving some problems. So what do you do? You check the event viewer. Now we all know that not all errors are really erros, and not all warnings are worth warning about. A standard case of too much information.
But what do you do with these obscure event ID errors that all searches turn up "not found"?
My latest example is this "Srv" error. Something about some non-paged pool crying about something. I don't have the actual event in front of me. But basically, it's Srv Event ID 2017. Tecnet had 2015 and other 201x errors that related to the same error, but not this specific ID.
Isn't there some database somewhere that catalogues these events? Somebody has to sit there and write them, and procedures to call them based on certain conditions. Where is this magical "phone book" of event log messages?
