Error Reading Log Event
Contents |
Monitor an unlimited number of servers with $49/year With the current low prices for servers and the need for processing power, even a small company may end up with quite a few of
Error Reading Log Event Record. Handle Specified Is
them. If ten years ago it was still common to see an entire company error reading log event record. handle specified is 87 using just one server, these days that's no longer the case. New computers are added to the network with the event id 3006 exchange understanding that they will be taken care of by the admins. Keeping an eye on these servers is a tedious, time-consuming process. Even with 5 minutes per server (to check the logs and other
Evntagnt 3006 87
parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking on any of the servers. read more... Event ID: 3006 Source: EvntAgnt Source: EvntAgnt Type: Warning Description:Error reading log event record. Handle specified is 619064. Return code from ReadEventLog is
Return Code From Readeventlog Is 5
is only available to subscribers. An example of Our approach Comments: Anonymous In my particular case (SBS 2008) in the agent tab in the SNMP services the SERVICE (lower half of the agent property tab) in it of itself was not configured correctly. The service was configured for the Physical, Applications, Internet and End-to-End. The server was not functioning as an IP gateway (router)so by clearing the check mark for the Internet service the logging of EventID: 3006 stopped. x 13 Weedfreer Error code 87 - On a Windows server 2003, I looked at Task Manager found that the SNMP service was causing the 'Services' process to be ramped up to 20%. This resulted in the 3006 error being logged many times a second. Restarted the SNMP service and all returned to normal. x 21 EventID.Net As per Microsoft: "The log event record could not be read. Event Agent ignored the error and will continue to operate normally; however, some event-to-SNMP (Simple Network Management Protocol) trap translations might be duplicated or missed. This will not affect the operation of the system". See MSW2KDB for more details. From a newsgroup post: "I found a fix on Microsoft Support site with KB Ar
additional information might be available elsewhere. Thank you for searching on this message; your search helps us identify those http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=3006&EvtSrc=EvntAgnt areas for which we need to provide more information. If the product or version you are looking for is not listed, you can use this search box to search TechNet, the Microsoft Knowledge Base, and TechNet Blogs for more information. Enter the product name, event source, and event ID. For example: Vista Application Error 1001.
87. In my case, I configured the events logs error reading to "Overwrite events older than : .. " instead of"Overwrite events as needed" and the problem was fixedhttp://www.eventid.net/display.asp?eventid=3006&eventno=1219&source=EvntAgnt&phase=1 Posted by Teche error reading log at 2:13 PM Labels: Windows No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Favorites Virtual Appliance Security Tools SNIA Dictionary IP Tools MX Lookup 10 Minutes E mail Labels Backup Data Center Desktop Hardware HP Blade Server Hyper-V Linux Migration PowerShell SCCM Security Storage Virtualization VMware Windows Watermark template. Powered by Blogger.