Re: Event log error messages
- From: "John Morton" <johnm@xxxxxxxxxxxx>
- Date: Tue, 29 Apr 2008 06:59:36 +0200
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@xxxxxxxxxxxxxxxxx> wrote in message
news:A20504E9-A085-4300-BBFA-B9AFA64694B4@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxx> wrote in message
news:ujIZXmQqIHA.4476@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxx> wrote in message
news:u2sMSIQqIHA.2256@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ewLaH1JqIHA.4292@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxx> wrote in message
news:er2rRvHqIHA.672@xxxxxxxxxxxxxxxxxxxxxxx
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).
.
- References:
- Event log error messages
- From: johnm
- Re: Event log error messages
- From: Paul Shapiro
- Re: Event log error messages
- From: John Morton
- Re: Event log error messages
- From: John Morton
- Re: Event log error messages
- From: Bill Sanderson
- Event log error messages
- Prev by Date: Re: Unable to send email to some recipients - Rejected as spam
- Next by Date: Re: Replacing SBS: Advice on choosing new servers
- Previous by thread: Re: Event log error messages
- Next by thread: Backup Email Feature in SBS 2003
- Index(es):
Relevant Pages
|