After Migrating V24 one of job is failing with ENDED_EMPTY - nothing found.

[Amit Lande]

After Migrating V24 one of job is failing with ENDED_EMPTY - nothing found.

Files are present at source location but not sure why this error is getting

More logs:

2025-06-20 09:30:15 - U00011494 FT '18934986': Unable to delete StatusStore file '../temp/FT1FA62C.sts'. Error: 'No such file or directory'.

Agent Logs:

Could you please someone help on this matter.

Thanks & Regards

Amit

[Daryl Brown]

Is this the report from a restarted file transfer object?  (You typically don't see messages about the .sts files unless you're dealing with a restart.)

If this was from a restart, did you trying restarting it specifying 'Transfer all new' rather than the default 'From last restart position'?
And if this was from a restart, can you share the report from the original failure?

[Amit Lande]

Hi Daryl

Thanks for your response please find below new transfer log (when the job actually ran)

Problem is that same job is working on V21 agent but not on V24 agent:

Job Log:

Agent log:

[Daryl Brown]

I'm confused now...  Are these new screenshots from your v21 agent or your v24 agent?

It is saying 'Files selected: '0''....are there actually files in that location?

Is the source location a UNC path?  Perhaps one where the file transfer does not have valid credentials to access?

[Amit Lande]

Hi Daryl,

Logs are from V24 agents only

Yes files are present at source location and job is trying to access folder having full permission

Is the source location a UNC path?  - am not sure how to check

Perhaps one where the file transfer does not have valid credentials to access?- yes its having valid credentials

Thanks & Regards

Amit L

[Amit Sharma]

A job failing with ENDED_EMPTY - Nothing found can occur for several reasons. Here are some possibilities:

• The preceding task is empty.
• All Agents were inactive.
• The Agent Group filters did not supply results.
• The Agents had no resources.
• If the Agent Group is defined using the All Active mode, and there are no active Agents when a task is executed, that task ends with ENDED_EMPTY – Nothing found status.
• For File Transfers, it has the status ENDED_EMPTY if no file is available that complies with the filter specifications.

The system checks whether Agents are available and active at regular intervals that can be specified in the UC_SYSTEM_SETTINGS variable using the AGENTGROUP_CHECK_INTERVAL key.

[Daryl Brown]

To clarify my question about the UNC path...  Is your source something like "\\servername\path\filename", or is it a local path like "d:\path\filename"?  I've seen errors in the past where a file transfer object may not have the necessary credentials to access a particular UNC share, but it shouldn't be an issue if it's a local drive.

Actually, based on the direction of the slashes in your log, this is probably a unix agent rather than a windows one...

I still find it odd that it's reporting 'Files selected: '0''.  I believe you when you say there are files there, but I'm suspicious that some permission issue is blocking the file transfer from being able to see them.

I'm similarly puzzled by the messages about the StatusStore file...  Can you double-check to confirm the user you're executing this file transfer as (on the source server) has access to both the source file location as well as the agent's temp folder?

Can you also confirm that your agent binary is owned by root?  (Recall the agent install steps about 'chown root ucxjlx6' and 'chmod 4755 ucxjlx6' (linux example).)

[Amit Lande]

Hi Daryl

Yes we are using UNC Path

Please note we are using ec2-user for agent temp folder and to access source file location we are using different user xyz (Application user) this is creating issue..?

Yes we are having following permission- chown root ucxjlx6' and 'chmod 4755 ucxjlx6 

Thanks & Regards

Amit L

[Daryl Brown]

Ok, if your job is running as a different user than what your agent was installed as, I have seen that cause problems...  Could you check to see if your ec2-user has read/write access to the agent's temp folder?  (e.g., can you touch a file in that folder as that user?)  If not, then updating the agent's temp folder permissions (e.g., chmod 777) may help.

As far as the UNC path goes, make sure your ec2-user is able to access that path from a commandline, just to rule out an authentication issue.  (I don't think that's really what the error is complaining about here, but just throwing that out there.)