Feature Request - filter on sql server errorlog
mipe10
Posts: 72 New member
Hi,
There are some errors with a severity level of for example 20 that one might want to exclude. For example
Error: 17806, Severity: 20, State: 14.
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: xxx.xxx.xxx.xxx].
Thanks
There are some errors with a severity level of for example 20 that one might want to exclude. For example
Error: 17806, Severity: 20, State: 14.
SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: xxx.xxx.xxx.xxx].
Thanks
Comments
This has been raised as an enhancement request (ref: SRP-4211). We could consider some kind of filtering similar to the long-running query alert.
Thanks for the feedback
Chris
Test Engineer
Red Gate