I built a job in Talend for Real Time Big Data Platform and it ran successfully when running from the studio. but... It won't run when I use Target run from Job server, Both Dev server and Job server have similar java setup.
According to above link, it normally happens when you are not able to reach that port. If you are using a Cloud services like AWS, please verify whether your security group is allowing to connect to that port.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
Ok... are you facing this issue when you are trying to use the Job server from Studio only?
I mean, are you facing the same issue when you schedule the job through TAC? I am still thinking of possible network issues between your Studio and Job server. Did you verify whether all the relevant ports are open?
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
It seems you do not have sufficient user privileges in the Job server where the file is present.
Could you please try to go the location with same user you are trying to run the Talend jobs in TAC and try to modify or delete the file? Most probably you will not be able to do it due to permission issues. If you provide sufficient privileges at server user level, it should work fine.
You must be using different id when you are running the jobs directly from Studio and you have full permission to delete or archive them. So please give full file operating permissions and you should see the difference after that. If the issue still persists, I would recommend to create a support ticket so that they can remotely check your issue through Webex.
If you can share the screen shots, I can also check but considering the security aspect of sharing user details of server in public domain, I would suggest you to get hep of support team.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
JobServer service account have all permissions, I can do by logging on server with that account.
I hope there is a problem with tfilecopy component.
While iterating to the all files in the directory, Some where locking was happening.
This is the Error am getting
tFileCopy_4 - Server\TestFile_201905144-124364600.csv (Access is denied) tFileCopy_4 - The source file Server\TestFile_201905144-124364600.csv could not be removed from the folder because it is open or you only have read-only rights.
My scenario is very similar to the below topic td-p/145292, which you have idea earlier. td-p/145292
Since you have already checked the user privileges, the issue is occuring since file is in open state.
Could you please share the job flow so that I can understand the current flow?
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
I am just iterating files and placing them in to ftp server and after success full transfer am renaming file placed into archive folder. when transfer fails placing files into another directory and deleting from source directory.
I am facing hard time while renaming and removing source file and running from Jobserver.
I believe your subsequent processes are getting triggered in the middle of FTP Put. So could you please add a On SubJob Ok after tFTPPut and connect them to tJava. From tJava, you can add the if clause to verify your conditions.
Similarly, could you please add On SubJob Error instead of On Component Error for the failure clause? This may have an impact in the flow.
Warm Regards, Nikhil Thampi
Please appreciate our Talend community members by giving Kudos for sharing their time for your query. If your query is answered, please mark the topic as resolved 🙂
