Splunk Universal Forwarder 7.x setup ended prematurely on Windows Server 2012 R2 Datacenter edition

kutlusensoy — Thu, 14 Feb 2019 13:06:36 GMT

Hi everyone,

I've read lots of articles for that issue, but I can't find any solutions.

Here is the premature splunk-utility.log content

2-13-2019 11:56:48.198 +0300 INFO  ServerConfig - Found no hostname options in server.conf. Will attempt to use default for now.
02-13-2019 11:56:48.198 +0300 INFO  ServerConfig - Host name option is "".
02-13-2019 11:56:49.983 +0300 INFO  loader - Running utility: "check-transforms-keys"
02-13-2019 11:56:49.983 +0300 INFO  loader - Getting configuration data from: c:\Program Files\SplunkUniversalForwarder\etc\myinstall\splunkd.xml
02-13-2019 11:56:49.983 +0300 INFO  loader - SPLUNK_MODULE_PATH environment variable not found - defaulting to c:\Program Files\SplunkUniversalForwarder\etc\modules
02-13-2019 11:56:49.983 +0300 INFO  loader - loading modules from c:\Program Files\SplunkUniversalForwarder\etc\modules
02-13-2019 11:56:49.999 +0300 INFO  loader - Writing out composite configuration file: c:\Program Files\SplunkUniversalForwarder\var\run\splunk\composite.xml

And also, I can read that Setup Failed because of Error code 1603 from log files in C:\TMP

Do you have any suggestion to solve this problem.

Thanks.

Re: Splunk Universal Forwarder 7.x setup ended prematurely on Windows Server 2012 R2 Datacenter edition

ddrillic — Sun, 17 Feb 2019 23:58:42 GMT

How does the splunkd.log end?

topic Re: Splunk Universal Forwarder 7.x setup ended prematurely on Windows Server 2012 R2 Datacenter edition in Deployment Architecture

Splunk Universal Forwarder 7.x setup ended prematurely on Windows Server 2012 R2 Datacenter edition

Re: Splunk Universal Forwarder 7.x setup ended prematurely on Windows Server 2012 R2 Datacenter edition