<?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: Installing latest splunk on Windows Server 2008 CRASH! in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64917#M9328</link>
    <description>&lt;P&gt;In general, any time you see a hard crash like that, it's a good idea to open a support case directly with Splunk.&lt;/P&gt;

&lt;P&gt;That said, &lt;CODE&gt;midas32.dll&lt;/CODE&gt; seems to be associated with BitDefender -- are you by any chance running BitDefener for antivirus?  If so, it would be worth the experiment to disable/remove it, or try a different antivirus product, and see if the problem persists.&lt;/P&gt;</description>
    <pubDate>Wed, 06 Oct 2010 09:12:58 GMT</pubDate>
    <dc:creator>southeringtonp</dc:creator>
    <dc:date>2010-10-06T09:12:58Z</dc:date>
    <item>
      <title>Installing latest splunk on Windows Server 2008 CRASH!</title>
      <link>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64916#M9327</link>
      <description>&lt;P&gt;So ... I installed the app, but at the tail end of the install it gave an error about not being able to start the application.  A quick 'netstat -an' confirmed port 8000 wasn't listening, so I checked the Windows event log... which generated this:&lt;/P&gt;

&lt;P&gt;Faulting application splunkd.exe, version 0.0.0.0, time stamp 0x4c8210b4, faulting module midas32.dll, version 0.5.1633.2367, time stamp 0x4acc7167, exception code 0xc00000fd, fault offset 0x00023303, process id 0xea4, application start time 0x01cb640cca16855c.&lt;/P&gt;

&lt;P&gt;So, a re-start of the Splunk service actually opens up port 8000, but when I try to connect to it, I never actually get a page, just an infinite wait.&lt;/P&gt;

&lt;P&gt;What's going on?&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2010 08:03:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64916#M9327</guid>
      <dc:creator>RafalLos</dc:creator>
      <dc:date>2010-10-06T08:03:35Z</dc:date>
    </item>
    <item>
      <title>Re: Installing latest splunk on Windows Server 2008 CRASH!</title>
      <link>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64917#M9328</link>
      <description>&lt;P&gt;In general, any time you see a hard crash like that, it's a good idea to open a support case directly with Splunk.&lt;/P&gt;

&lt;P&gt;That said, &lt;CODE&gt;midas32.dll&lt;/CODE&gt; seems to be associated with BitDefender -- are you by any chance running BitDefener for antivirus?  If so, it would be worth the experiment to disable/remove it, or try a different antivirus product, and see if the problem persists.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2010 09:12:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64917#M9328</guid>
      <dc:creator>southeringtonp</dc:creator>
      <dc:date>2010-10-06T09:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: Installing latest splunk on Windows Server 2008 CRASH!</title>
      <link>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64918#M9329</link>
      <description>&lt;P&gt;Good point.  I AM running BitDefender on that box (it wouldn't shock me that the A/V is borking the Splunk install)...&lt;/P&gt;</description>
      <pubDate>Wed, 06 Oct 2010 10:48:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Installing-latest-splunk-on-Windows-Server-2008-CRASH/m-p/64918#M9329</guid>
      <dc:creator>RafalLos</dc:creator>
      <dc:date>2010-10-06T10:48:22Z</dc:date>
    </item>
  </channel>
</rss>

