VERIFIED SOLUTION i
Resolve issue where input files are not getting picked from download path in EngageOne Vault
Files not getting picked for ingestion in Vault, without any error message in the loader (e2loaderd) log
Possible causes includes:
- Incorrect download directory
- User/login from which Vault loader (e2loaderd) is running does not have read permission on the download directory.
UPDATED: August 1, 2017
- Default download path is <vault_home>/server/download. However it can be overridden in server.ini file. Check server.ini for the same.
- User/login from which Vault loader (e2loaderd) is running, have read permission on the download directory.
- No Downloads