Hi,
I set up an alert to notify me of failed login attempts and it worked fine
up until SQL Server was bounced yesterday. The messages are still going into
the error log but the alert count doesn't go up and so the notification
doesn't happen any more. The SQLServer agent is running, jobs are running on
schedule, but not these alerts. I'm using netsend and can successfully send a
test message.
I'm running Microsoft SQL Server 2000 - 8.00.194 Enterprise Edition on
Windows NT 4.0 (Build 1381: Service Pack 6)
Thanks for any help
Is the alert appearing in the Windows event log and is the
event log service running? If it's not in the event log,
check the properties for the event log, make sure the
service is running and that the log is not full if not set
to overwrite.
-Sue
On Thu, 7 Apr 2005 03:57:02 -0700, "John"
<John@.discussions.microsoft.com> wrote:
>Hi,
>I set up an alert to notify me of failed login attempts and it worked fine
>up until SQL Server was bounced yesterday. The messages are still going into
>the error log but the alert count doesn't go up and so the notification
>doesn't happen any more. The SQLServer agent is running, jobs are running on
>schedule, but not these alerts. I'm using netsend and can successfully send a
>test message.
>I'm running Microsoft SQL Server 2000 - 8.00.194 Enterprise Edition on
>Windows NT 4.0 (Build 1381: Service Pack 6)
>Thanks for any help
|||thanks for the quick response Sue,
the alerts are still appearing in the Windows event log
"Sue Hoegemeier" wrote:
> Is the alert appearing in the Windows event log and is the
> event log service running? If it's not in the event log,
> check the properties for the event log, make sure the
> service is running and that the log is not full if not set
> to overwrite.
> -Sue
> On Thu, 7 Apr 2005 03:57:02 -0700, "John"
> <John@.discussions.microsoft.com> wrote:
>
>
|||Check the Agent Error log for all messages. If you are set
up as an operator, check to see if you have any hours
restrictions.
There is also a troubleshooting article in books online:
Troubleshooting Alerts
-Sue
On Thu, 7 Apr 2005 06:31:06 -0700, "John"
<John@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>thanks for the quick response Sue,
>the alerts are still appearing in the Windows event log
>"Sue Hoegemeier" wrote:
|||doh! It's part of a failover cluster - I must have set up the alert on the
primary cluster but not on the secondary, so when the server was bounced it
would have failed over, hence the alert not firing! That's my theory anyway,
I can't test it just yet because I need to recycle once again to ensure that
the audit level is correctly set to 'failures' - how do you check that this
is set? I can see that I have set it in EM but that won't take effect until I
recycle - does sp_configure display the current setting?
"Sue Hoegemeier" wrote:
> Check the Agent Error log for all messages. If you are set
> up as an operator, check to see if you have any hours
> restrictions.
> There is also a troubleshooting article in books online:
> Troubleshooting Alerts
> -Sue
> On Thu, 7 Apr 2005 06:31:06 -0700, "John"
> <John@.discussions.microsoft.com> wrote:
>
>
|||No...the auditing setting is not available with sp_configure
The audit level is recorded in the AuditLevel key in the
registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer
3 = All, 2 = Failure, 1 = Success, 0 = None.
-Sue
On Fri, 8 Apr 2005 02:51:05 -0700, "John"
<John@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>doh! It's part of a failover cluster - I must have set up the alert on the
>primary cluster but not on the secondary, so when the server was bounced it
>would have failed over, hence the alert not firing! That's my theory anyway,
>I can't test it just yet because I need to recycle once again to ensure that
>the audit level is correctly set to 'failures' - how do you check that this
>is set? I can see that I have set it in EM but that won't take effect until I
>recycle - does sp_configure display the current setting?
>"Sue Hoegemeier" wrote:
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment