Prev: ntbackup with nas - xfs
Next: Can't receive mail from a external particular sender
From: John Morton on 28 Apr 2008 04:26
Hi Bill
Ahhh... That fix you have pointed me to refers to SQL2005 and not SQL2000 -
might me a bid fool hardy to apply it to SQL2000?

Acually, is everyone else on SBS2003 seeing this same issue? as I think the
issue is related to the SQL installed with SBS2003 (SQLAgent$SBSMONITORING )
and not the full SQL2000 installed with Premium.

Any more thoughts would be apprecieted.

Larry, the error code in the event log is 318 (it was there on theoriginal
post)

John
-----------------------------------
"John Morton" <johnm(a)jcm-polo.com> wrote in message
news:u2sMSIQqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
> 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).
>>
>
>


From: Larry Struckmeyer on 28 Apr 2008 05:13
Hi John:

My reply was offered in the spirit of: "Teach a man to fish......."

Yes, I could have tried the numbers in your message at www.eventid.net. But
I have done hundreds of those searches and am not excited about doing more
without the firm knowledge of the Event Id and the Source. The numbers with
the error might be the necessary info, or they may be internal numbers that
are not indexed at www.eventid.net.

Do you know what is clearing the log every day to generate this log entry
and the subsequent item in the SBS daily/morning report? If you could
figure that out, perhaps the morning report would stop giving you this
entry.

--
Larry

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


"John Morton" <johnm(a)jcm-polo.com> wrote in message
news:ujIZXmQqIHA.4476(a)TK2MSFTNGP04.phx.gbl...
> Hi Bill
> Ahhh... That fix you have pointed me to refers to SQL2005 and not
> SQL2000 - might me a bid fool hardy to apply it to SQL2000?
>
> Acually, is everyone else on SBS2003 seeing this same issue? as I think
> the issue is related to the SQL installed with SBS2003
> (SQLAgent$SBSMONITORING ) and not the full SQL2000 installed with Premium.
>
> Any more thoughts would be apprecieted.
>
> Larry, the error code in the event log is 318 (it was there on theoriginal
> post)
>
> John
> -----------------------------------
> "John Morton" <johnm(a)jcm-polo.com> wrote in message
> news:u2sMSIQqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
>> 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).
>>>
>>
>>
>
>


From: John Morton on 28 Apr 2008 09:17
Hi Larry

Yep I figured that's what you were getting at ;-)

But do you know, I emailed those eventid people (in Canada I think) over 2
weeks ago asking for an update on the license I already own - as they appear
to have changed their method of retrieval since I last used the sware. Now
it appears that if you want the software solution you also have to subscribe
to their monthly updates as well...

I'm clearing it out myself and I can stop doing so of course - just don't
like to be beaten by a little issue like this...
Best, John
----------------------------------------------------

"Larry Struckmeyer" <lstruckmeyer(at)mis-wizards(dot)com> wrote in message
news:u8SnXARqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
> Hi John:
>
> My reply was offered in the spirit of: "Teach a man to fish......."
>
> Yes, I could have tried the numbers in your message at www.eventid.net.
> But I have done hundreds of those searches and am not excited about doing
> more without the firm knowledge of the Event Id and the Source. The
> numbers with the error might be the necessary info, or they may be
> internal numbers that are not indexed at www.eventid.net.
>
> Do you know what is clearing the log every day to generate this log entry
> and the subsequent item in the SBS daily/morning report? If you could
> figure that out, perhaps the morning report would stop giving you this
> entry.
>
> --
> Larry
>
> Please post the resolution to
> your issue so that all can benefit.
>
>
> "John Morton" <johnm(a)jcm-polo.com> wrote in message
> news:ujIZXmQqIHA.4476(a)TK2MSFTNGP04.phx.gbl...
>> Hi Bill
>> Ahhh... That fix you have pointed me to refers to SQL2005 and not
>> SQL2000 - might me a bid fool hardy to apply it to SQL2000?
>>
>> Acually, is everyone else on SBS2003 seeing this same issue? as I think
>> the issue is related to the SQL installed with SBS2003
>> (SQLAgent$SBSMONITORING ) and not the full SQL2000 installed with
>> Premium.
>>
>> Any more thoughts would be apprecieted.
>>
>> Larry, the error code in the event log is 318 (it was there on
>> theoriginal post)
>>
>> John
>> -----------------------------------
>> "John Morton" <johnm(a)jcm-polo.com> wrote in message
>> news:u2sMSIQqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
>>> 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).
>>>>
>>>
>>>
>>
>>
>
>


From: Bill Sanderson on 28 Apr 2008 12:24
Agreed - that's why I asked whether it made sense in your environment.

I haven't seen this, but I don't clear my logs, and I'm running Premium,
so...



"John Morton" <johnm(a)jcm-polo.com> wrote in message
news:ujIZXmQqIHA.4476(a)TK2MSFTNGP04.phx.gbl...
> Hi Bill
> Ahhh... That fix you have pointed me to refers to SQL2005 and not
> SQL2000 - might me a bid fool hardy to apply it to SQL2000?
>
> Acually, is everyone else on SBS2003 seeing this same issue? as I think
> the issue is related to the SQL installed with SBS2003
> (SQLAgent$SBSMONITORING ) and not the full SQL2000 installed with Premium.
>
> Any more thoughts would be apprecieted.
>
> Larry, the error code in the event log is 318 (it was there on theoriginal
> post)
>
> John
> -----------------------------------
> "John Morton" <johnm(a)jcm-polo.com> wrote in message
> news:u2sMSIQqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
>> 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).
>>>
>>
>>
>
>

From: John Morton on 29 Apr 2008 00:59
Bill
We are running Premium also, but I think this error message relates to
SBS2003's cut back version of SQL which is installed on every new
installation of SBS2003.

Sounds like it cannot be got rid of - so don't clear log is the answer -
then the only time then you will see the message is on a re-boot.

---------------------------------

"Bill Sanderson" <bill_sanderson(a)msn.com.plugh.org> wrote in message
news:A20504E9-A085-4300-BBFA-B9AFA64694B4(a)microsoft.com...
> Agreed - that's why I asked whether it made sense in your environment.
>
> I haven't seen this, but I don't clear my logs, and I'm running Premium,
> so...
>
>
>
> "John Morton" <johnm(a)jcm-polo.com> wrote in message
> news:ujIZXmQqIHA.4476(a)TK2MSFTNGP04.phx.gbl...
>> Hi Bill
>> Ahhh... That fix you have pointed me to refers to SQL2005 and not
>> SQL2000 - might me a bid fool hardy to apply it to SQL2000?
>>
>> Acually, is everyone else on SBS2003 seeing this same issue? as I think
>> the issue is related to the SQL installed with SBS2003
>> (SQLAgent$SBSMONITORING ) and not the full SQL2000 installed with
>> Premium.
>>
>> Any more thoughts would be apprecieted.
>>
>> Larry, the error code in the event log is 318 (it was there on
>> theoriginal post)
>>
>> John
>> -----------------------------------
>> "John Morton" <johnm(a)jcm-polo.com> wrote in message
>> news:u2sMSIQqIHA.2256(a)TK2MSFTNGP05.phx.gbl...
>>> 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).
>>>>
>>>
>>>
>>
>>
>


First  |  Prev  | 
Pages: 1 2
Prev: ntbackup with nas - xfs
Next: Can't receive mail from a external particular sender