From: johnm on
Hi

We constently get the same following 3 messages appear in our event logs as
well as a note in the daily 'server' report under critical errors:-

25/04/2008 17:03:23 SQLAgent$SBSMONITORING Warning Alert Engine 312 N/A
JCMSBS1 Successfully re-opened the local eventlog - NOTE: Some events may
have been missed.
25/04/2008 17:03:23 SQLAgent$SBSMONITORING Information Alert Engine 311
N/A JCMSBS1 Attempting to to re-open the local eventlog...
25/04/2008 17:03:23 SQLAgent$SBSMONITORING Error Alert Engine 318 N/A
JCMSBS1 Unable to read local eventlog (reason: The event log file has
changed between read operations).

Can someone please suggest a possible fix? I've searched various MS tech
sites but as yet cannot find a solution.

TIA, John


From: Larry Struckmeyer on
Hi John:

Either post up the event id and source, or look up the errors yourself on:

www.eventid.net

--
Larry

Please post the resolution to
your issue so that all can benefit.


"johnm" <jmorton(a)jcm-polo.com> wrote in message
news:er2rRvHqIHA.672(a)TK2MSFTNGP02.phx.gbl...
> Hi
>
> We constently get the same following 3 messages appear in our event logs
> as well as a note in the daily 'server' report under critical errors:-
>
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Warning Alert Engine 312 N/A
> JCMSBS1 Successfully re-opened the local eventlog - NOTE: Some events may
> have been missed.
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Information Alert Engine 311
> N/A JCMSBS1 Attempting to to re-open the local eventlog...
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Error Alert Engine 318 N/A
> JCMSBS1 Unable to read local eventlog (reason: The event log file has
> changed between read operations).
>
> Can someone please suggest a possible fix? I've searched various MS tech
> sites but as yet cannot find a solution.
>
> TIA, John
>


From: Bill Sanderson on
Does this look applicable?

http://support.microsoft.com/kb/926612


"johnm" <jmorton(a)jcm-polo.com> wrote in message
news:er2rRvHqIHA.672(a)TK2MSFTNGP02.phx.gbl...
> Hi
>
> We constently get the same following 3 messages appear in our event logs
> as well as a note in the daily 'server' report under critical errors:-
>
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Warning Alert Engine 312 N/A
> JCMSBS1 Successfully re-opened the local eventlog - NOTE: Some events may
> have been missed.
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Information Alert Engine 311
> N/A JCMSBS1 Attempting to to re-open the local eventlog...
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Error Alert Engine 318 N/A
> JCMSBS1 Unable to read local eventlog (reason: The event log file has
> changed between read operations).
>
> Can someone please suggest a possible fix? I've searched various MS tech
> sites but as yet cannot find a solution.
>
> TIA, John
>

From: Paul Shapiro on
I see these events logged by any running SQL Server Agent whenever the
Windows event log file has been cleared. I forget but it's either the System
or Event log being cleared. It's normal, and doesn't constitute an error. If
you read the error text, it kind of makes sense, although it's certainly not
clear. If no one is manually clearing the Windows event log, maybe it's set
to clear automatically at some time, or roll over to a new log file?

"johnm" <jmorton(a)jcm-polo.com> wrote in message
news:er2rRvHqIHA.672(a)TK2MSFTNGP02.phx.gbl...
> Hi
>
> We constently get the same following 3 messages appear in our event logs
> as well as a note in the daily 'server' report under critical errors:-
>
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Warning Alert Engine 312 N/A
> JCMSBS1 Successfully re-opened the local eventlog - NOTE: Some events may
> have been missed.
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Information Alert Engine 311
> N/A JCMSBS1 Attempting to to re-open the local eventlog...
> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Error Alert Engine 318 N/A
> JCMSBS1 Unable to read local eventlog (reason: The event log file has
> changed between read operations).

From: John Morton on
Hi Paul
It appears in the events log -> Applications and no it's not carried over -
just re-apperas each time the log is cleared. Actually I don't think it's
important but as it appears every day in my server report it's sort of
annoying...

Bill has pointed me to an MS fix - I'll take a look at that and see what
that offers
Thanks to all
John
----------------------------
"Paul Shapiro" <paul(a)hideme.broadwayData.com> wrote in message
news:ewLaH1JqIHA.4292(a)TK2MSFTNGP04.phx.gbl...
>I see these events logged by any running SQL Server Agent whenever the
>Windows event log file has been cleared. I forget but it's either the
>System or Event log being cleared. It's normal, and doesn't constitute an
>error. If you read the error text, it kind of makes sense, although it's
>certainly not clear. If no one is manually clearing the Windows event log,
>maybe it's set to clear automatically at some time, or roll over to a new
>log file?
>
> "johnm" <jmorton(a)jcm-polo.com> wrote in message
> news:er2rRvHqIHA.672(a)TK2MSFTNGP02.phx.gbl...
>> Hi
>>
>> We constently get the same following 3 messages appear in our event logs
>> as well as a note in the daily 'server' report under critical errors:-
>>
>> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Warning Alert Engine 312 N/A
>> JCMSBS1 Successfully re-opened the local eventlog - NOTE: Some events may
>> have been missed.
>> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Information Alert Engine 311
>> N/A JCMSBS1 Attempting to to re-open the local eventlog...
>> 25/04/2008 17:03:23 SQLAgent$SBSMONITORING Error Alert Engine 318 N/A
>> JCMSBS1 Unable to read local eventlog (reason: The event log file has
>> changed between read operations).
>