Why can't I install Splunk on windows 7 64 bit and getting error "Splunk Enterprise Setup Wizard ended prematurely..."?

[mougeolle]

Hello
I'm newbie with Splunk. I would like to discover the product after a friend had talk to me about it. So I got the 64 bit msi for my windows 7 64 bits. Since my c: is already filled a lot, I made a mklink /d c:/pr...files/Splunk to e:/Splunk, and installation started but failed with the following message :

c:/program files/splunk/share : path too long

Ok, I clicked Setup Finish button, and purged the both directories "splunk" on c: and e: , verified there is enough space on c:,. I ran the installer a second time which seemed to work fine, but after the second status message "copying new files" and progress bar entirely filled, it decided to roll back without any explanation. Just this lethal message :

Splunk Enterprise Setup Wizard ended prematurely because of an error. Your system has not be modified. To install this program at a later time, run Setup Wizard again.

Same causes producing often same effects, I ran setup again with the same result. Any idea to help me to return on the right way ?
Thx a lot.

[joliveira]

Hi i have the same problem with Windows 10 in 64 bit. At the end of the installation its rooll back. There is a log file to test whats the problem.?

[ChrisG]

There are some Windows installation defects in the 6.2 release of Splunk Enterprise. Are you running on a non-English version of Windows? I am not sure why you need to install with the symlink. Can you try a basic installation within the directory you want?

[martin_mueller]

Based on the "Frenchiness" of the name I'd guess you're affected by this: http://answers.splunk.com/answers/177866/why-am-i-getting-splunk-enterprise-setup-wizard-en.html

As for your space issue, you could either mount a second volume into that path instead of linking, or install Splunk to C: as usual and redefine the $SPLUNK_DB to store the actual index data on D:.

[jclyde]

What did it say in the migration log under ..\var\log\splunk? It will give more info about the errors, hopefully.