<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Failed to write usn context in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13965#M1332</link>
    <description>&lt;P&gt;Glad to hear you got it fixed.&lt;BR /&gt;
How did it get to that state, do you know?&lt;/P&gt;</description>
    <pubDate>Tue, 01 Jun 2010 13:32:47 GMT</pubDate>
    <dc:creator>Ledio_Ago</dc:creator>
    <dc:date>2010-06-01T13:32:47Z</dc:date>
    <item>
      <title>Failed to write usn context</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13962#M1329</link>
      <description>&lt;P&gt;I am seeing the following errors over and over again in my splunkd.log file.  I'm not sure where to go to resolve this.  Any thoughts?&lt;/P&gt;

&lt;P&gt;05-20-2010 11:15:54.163 ERROR ExecProcessor - message from ""C:\Program Files\Splunk\bin\splunk-admon.exe"" splunk-admon - run: Failed to write usn context.
05-20-2010 11:15:54.163 ERROR ExecProcessor - message from ""C:\Program Files\Splunk\bin\splunk-admon.exe"" splunk-admon - main: Failed to run ADMonitor='NearestDC', targedDC='{FQDN of DC}'&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2010 00:22:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13962#M1329</guid>
      <dc:creator>srich</dc:creator>
      <dc:date>2010-05-21T00:22:11Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to write usn context</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13963#M1330</link>
      <description>&lt;P&gt;It sounds like Active Directory monitor program, splunk-admon.exe, couldn't save its checkpoint value, which is a USN string.&lt;/P&gt;

&lt;P&gt;Check and see if the checkpoint file is created under:&lt;/P&gt;

&lt;P&gt;Splunk\var\lib\splunk\persistentstorage\ADMon\NearestDC.ini&lt;/P&gt;

&lt;P&gt;For some reason we can't write to that file.&lt;/P&gt;</description>
      <pubDate>Fri, 21 May 2010 06:52:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13963#M1330</guid>
      <dc:creator>Ledio_Ago</dc:creator>
      <dc:date>2010-05-21T06:52:37Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to write usn context</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13964#M1331</link>
      <description>&lt;P&gt;The file was there but permissions were wrong.  Thanx.&lt;/P&gt;</description>
      <pubDate>Sat, 29 May 2010 04:12:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13964#M1331</guid>
      <dc:creator>srich</dc:creator>
      <dc:date>2010-05-29T04:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Failed to write usn context</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13965#M1332</link>
      <description>&lt;P&gt;Glad to hear you got it fixed.&lt;BR /&gt;
How did it get to that state, do you know?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Jun 2010 13:32:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Failed-to-write-usn-context/m-p/13965#M1332</guid>
      <dc:creator>Ledio_Ago</dc:creator>
      <dc:date>2010-06-01T13:32:47Z</dc:date>
    </item>
  </channel>
</rss>

