SplunkD never starts successfully. This is the first time Splunk has ever been installed on this machine. The machine is running Windows XP service pack 2. The Splunk version installed is splunk-4.1.6-89596-x86-release.msi. Below I've pasted the last log entry in SplunkD.log before the crash and the crash file that is produced when you try to manually start the SplunkD Service.
SplunkD.log databasePartitionPolicy - Adding C:\Program Files\Splunk\var\lib\splunk\audit\db\hot_v1_0 because it was not in the manifest for metadata.
Crash log [build 89596] 2011-01-14 11:07:48 C++ exception: object@[0x0217F154], type@[0x00D1312C] Exception is Non-continuable Exception address: [0x7C812AFB] Crashing thread: MainTailingThread ContextFlags: [0x0001003F] Dr0: [0x00000000] Dr1: [0x00000000] Dr2: [0x00000000] Dr3: [0x00000000] Dr6: [0x00000000] Dr7: [0x00000000] SegGs: [0x00000000] SegFs: [0x0000003B] SegEs: [0x00000023] SegDs: [0x00000023] Edi: [0x059CFA48] Esi: [0x0217F144] Ebx: [0x027FA96C] Edx: [0x00000001] Ecx: [0x00000000] Eax: [0x0217F0BC] Ebp: [0x0217F10C] Eip: [0x7C812AFB]
Please do the following:
grep ERROR $SPLUNK_HOME/var/log/splunk/splunkd.log
(or the equivalent command on windows)
There was nothing in the log at the ERROR level...the most severe error in the splunkd.log was WARN: databasePartitionPolicy - Adding C:\Program Files\Splunk\var\lib\splunk\audit\db\hot_v1_0 because it was not in the manifest for metadata.