<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>EventMon: Stopping a Capture Based on an EventLog Event</title><link>http://blogs.technet.com/b/netmon/archive/2007/02/22/eventmon-stopping-a-capture-based-on-an-eventlog-event.aspx</link><description>Having worked in Product Support for many years, I’ve had many occasions where a specific Event Log error was showing up, and we wanted to understand how this event related to the problem we were t-shooting. And in some cases, the Event Log error was</description><dc:language>en</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Some batch files to take the pain out of capturing traces along with other relevant information</title><link>http://blogs.technet.com/b/netmon/archive/2007/02/22/eventmon-stopping-a-capture-based-on-an-eventlog-event.aspx#3044521</link><pubDate>Fri, 25 Apr 2008 00:37:58 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3044521</guid><dc:creator>Microsoft Enterprise Networking Team</dc:creator><description>&lt;p&gt;NetMon is a common tool which comes in handy in revealing behaviour of various problems. When Network&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3044521" width="1" height="1"&gt;</description></item><item><title>Santa’s Bag was Full</title><link>http://blogs.technet.com/b/netmon/archive/2007/02/22/eventmon-stopping-a-capture-based-on-an-eventlog-event.aspx#2686804</link><pubDate>Fri, 28 Dec 2007 20:45:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:2686804</guid><dc:creator>Network Monitor</dc:creator><description>&lt;p&gt;The Elves are working furiously on the next version of Network Monitor 3.2. But it seems that NM3.2 won’t&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=2686804" width="1" height="1"&gt;</description></item><item><title>Generating a memory dump when a particular event log message</title><link>http://blogs.technet.com/b/netmon/archive/2007/02/22/eventmon-stopping-a-capture-based-on-an-eventlog-event.aspx#1547476</link><pubDate>Wed, 18 Jul 2007 08:18:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1547476</guid><dc:creator>Blog du Tristank</dc:creator><description>&lt;p&gt;Building from Paul Long's post on stopping a Netmon3 capture on a particular event , we're going to re-jig&lt;/p&gt;
&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=1547476" width="1" height="1"&gt;</description></item></channel></rss>