The system cannot find the path specified.

It's working for \vboxsrvDocumentsLogauswertungenLogs now, I must have forgotten to check this option after the reinstall.

To add some knowledge: Services must not access network drives through drive mappings, they have to use the UNC names. See INFO: Services and Redirected Drives for more information.

Ahh... ! Now i got the problem, that the splunk service isn't able to index the files in the network drive link described here Windows Mapped Drives and Light Forwarding. Here is the link given in that Thread: How to map a network drive to be used by a service.

I will try the solution given there.

Interesting to add: When I choose to "Upload and index" a file instead of "Continuously index data from a file or directory this Splunk instance can access" or "Index a file once from this Splunk server" it works from every path.

Using "Continuously index data from a file or directory this Splunk instance can access" gives a slightly different error:

Encountered the following error while trying to save: In handler 'monitor': Parameter name: Path does not exist.

Anyone there to help?

I checked the splunkd.log, the only thing I could find a couple times is this. Must be from the time a were able to add such a monitoring link:

TailingProcessor - Insufficient permissions to read file='\\VBOXSVR\Documents\Logauswertung\Logs\14.SystemOut.log' (hint: Incorrect function.).

I also tried your oneshot in cmd, this is the message I got:

C:\Program Files\Splunk\bin>splunkd.exe add oneshot E:\Logauswertung\Logs\SystemOut
Couldn't open log file configuration "\etc\log.cfg": The operation completed successfully.
Error loading logging config file

Does this help us?

I tried some other things (one-by-one and all of them together):

1. Removing the "read only" from all folders and files in the Splunk directory (there were some restrictions)
2. Turning off the WinXP-Firewall
3. Disable avast Antivirus

Still no change.

Good morning everyone. :)

I should be able to access files and directories no matter if I installed Splunk as a local user or in a domain, right? My Splunk is set up as local user.

Didn't anybody ever got this issue, I can't figure out any solution on my self...

I reinstalled Splunk and now I'am able to index files, which are in the guest system.

Unfortunality I still get the error "Encountered the following error while trying to save: In handler 'monitor': Parameter name: Path does not exist." when I am trying to add a network path.

I am using VirtualBox and its guest additions to access files on the host system. These files are to be found via this links fro the guest system:

E:\Logauswertungen\Logs\
\\vboxsrv\Documents\Logauswertungen\Logs

Everytime I try to add this folders I get the error.

Its working for

\\vboxsrv\Documents\Logauswertungen\Logs

now, but Splunk isn't indexing the files there. There must be a connection to this:

How to map a network drive to be used by a service

Service Running as System Account Fails Accessing Network

I am still checking the options. Thought this might be important for other guys too, so I post it here.