Getting Data In

Unable to start Splunk on Windows after upgrading - "Splunkd: Unable to start the service: The specified service does not exist as an installed service."

phadnett_splunk
Splunk Employee
Splunk Employee

We recently updated from Windows Server 2008 SP2 to 2008 R2 SP1 so we could upgrade from Splunk version 6.0 to 6.4. Now we are unable to start Splunk and we notice that the application isn't in the list of services.msc.

Starting splunk server daemon (splunkd)...

Splunkd: Unable to start the service: The specified service does not exist as an installed service.
E:\Program Files\Splunk\bin>
0 Karma
1 Solution

phadnett_splunk
Splunk Employee
Splunk Employee

I suggest that you manually install the Splunk service by running the following command from the /bin directory: splunk enable boot-start

You may have tried to upgrade Splunk with a user account that has does not have administrative privileges.

View solution in original post

phadnett_splunk
Splunk Employee
Splunk Employee

I suggest that you manually install the Splunk service by running the following command from the /bin directory: splunk enable boot-start

You may have tried to upgrade Splunk with a user account that has does not have administrative privileges.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...