Submit My Question - Recent Questions - Recent Answer

Msdn Tech >> SQL Server >> SQL Server Replication

sql 2005 Error: Unable to read local eventlog (reason: 87).

on the same machine both 2000 and 2005.
2000 replicate to 2005, then 2005 replicate to 2000.
I recieve the above error from 2005 instance.
The replicates (both) work fine, but the application EVL is full with this error.

Any Ideas?

[246 byte] By [TMF] at [2008-2-17]

«« Struggling with no touch deployment
»» VERY useful skillbut many people don't know

# 1

Could you please tell me the exact setup that you have?
Is SQL 2000 a publisher/distributor and SQL 2005 a subscriber which then republishes?
What kind of replication is this? Tran/Snapshot/Merge?

MaheshDudgikar at 2007-9-9 >

top of Msdn Tech,SQL Server,SQL Server Replication...

# 2

Hi,

This is a known issue with SQL server agent and should be fixed in the next release. But this message should be harmless.

Thanks,

-Peng

PengSong at 2007-9-9 >

# 3

First:
I recieved notif about note from "TheReverend", but can't retrieve it (delete?).
The note talk about merge reps.

My rep is Snapshot, the 2005 has its own distibute DB.

Any way I glad to heared MS fixed it, I notice it harmless msg (because the reps work just fine) but my log screemed me (I'm using the win log alot).

Thanks again,

TMF at 2007-9-9 >

# 4

Hi,

I am also seeing this error in the applications log in event viewer. In my case SQL01 instance is setup as a publisher with a remote SQL 2005 distributor.

Event Type: Error
Event Source: SQLAgent$SQL01
Event Category: Alert Engine
Event ID: 318
Date: 17/11/2005
Time: 15:01:16
User: N/A
Computer:
Description:
Unable to read local eventlog (reason: 87).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Cheers,
Priyanga

PriyangaKarunathilake at 2007-9-9 >

# 5

I'm getting this error when I'm trying to do a Maintenance cleanup plan. The backup works but when trying to delete any old backups it errors. This is on a brand new SQL 2005 server that has and isn't been used for anything else.

Thanks

Kris

Kris_H at 2007-9-9 >

# 6

Kris,

I have been advised that this issue has been fixed in SQL 2005 SP1 Beta.

Cheers

PriyangaKarunathilake at 2007-9-9 >

# 7

Has SP1 been released yet?

Kris_H at 2007-9-9 >

# 8

I have installed the March CTP of SP1 and I am still getting the "Unable to read local eventlog" error as before. Did the fix not make it in yet?

peterg99 at 2007-9-9 >

# 9

We're also seeing this error on our Windows Server 2003 x64 running SQL Server 2005 Standard RTM.

Any news on the fix? My logs are looking pretty messy now!

JoelMansford at 2007-9-9 >

# 10

I have been getting these messages since installing SQL Server 2005 x64 (service pack2) whenever a job runs.

It makes looking for genuine problems in the event logs a lengthy process. I cannot find a KB that addresses this issue, or any discussions that help any more than "it's harmless".

Does anyone have any updated information on this?

Thanks

Mark_CM at 2007-9-9 >

# 11

I have been experiencing the same error on a sql 2005 server with sp1 installed:

My log contains 32,000 entries over 24hrs with the following message exclusively.

It seems to have hijacked my log.

I have to restart SQL Agent every couple of days to stop it, then its starts up again a few days later.

Date 13/08/2007 10:28:26 AM
Log SQL Agent (Current - 10/08/2007 12:11:00 PM)

Message
[LOG] Unable to read local eventlog (reason: 87)

sandrop at 2007-9-9 >

SQL Server

SQL Server Replication

SQL Server Hot Topic

SQL Server New Topic

SQL Server

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech