Job Works Properly in Talend but not when built, deployed

[DarinAfni]

Hello,

I have a very simple Talend Open Source DI project that uses two different tFileList components to search a directory for a couple of file masks to copy them from one directory to another. (I separate the 2 so that I can identify which type of spreadsheet was found and copied more easily) Really no frills or tricks. I do have some context variables that define some dev/prod file directories to DEV and QA the process but the default (prod) context variables are used when the job is built. Once I build and then extract all the files and run the .bat from Task Scheduler on the ETL host - the job runs without error but the file masks that we know are present in the source directory are not recognized so no files get copied.

When we open the job in Talend to troubleshoot and run in the Default (prod) context then Talend recognized the files from the filemasks and copies the appropriate files over.

I don't understand how the job can perform as expected in Talend but not when built and deployed. I use TOS Data Integration for a number of our database ETLs and I've never encountered this. I've rebuilt the job from scratch and both versions perform the exact same. It's almost like the built, deployed version is looking in the wrong source directory but even if it were looking in the DEV directory there are test/sample sheets that meet the filemasks that it should pick up in that case so I don't understand what's happening.

Thanks,

Darin

[gjeremy1617088143]

hi Darin, is see you write log in a file can you Send it ?

Send me Love and Kudos

[DarinAfni]

All that's going to that log are the outputs from the tSetGlobalVar components. Basically - I grab the name of the file being copied and and timestamps for when the job starts/ends. The log is strictly for items that I've deemed important to glean from the result of the proc.

[DarinAfni]

I figured this out.

The service account being used to run the job via windows task scheduler did not have sufficient privileges to the specified source directory.