Automic Community

Expand all | Collapse all

One of our File Transfer Job fails to rename the file, It does not fail everyday.

  • 1.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 10:15 AM

    The Job usually fails when the file size is greater, the job creates the .tmp file but fails while renaming.

    his job transfers file from a Unix Server to Windows Machine it uses Wildcard to transfer the file.

     

    This Job completed successfully when the file size is low – 47,913 KB (0.047 GB)

     

    However, when the file size is more the job fails – example 662,458 KB (0.66 GB).

    Can you please let me know why this happens?



  • 2.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 10:28 AM
    Have you taken a look at the respective agent log files already? Those might hold a clue.

    Best regards.


  • 3.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 10:53 AM
    Job report & Agent version would help as well...

    cheers, Wolfgang


  • 4.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 12:16 PM
    Job Report-  ERROR '0' bytes, incorrect transfer of '0' records for file.U00063039 FT '219821722': The temporary file  cannot be renamed to destination file . Error: '1359 - An internal error occurred. U00011409 FT '219821722': FileTransfer ended abnormally.


  • 5.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 12:25 PM
    Well. Error 1359 comes straight from the Microsoft API and is classified there also only as (drumroll ...)

    "An internal error occured"

    https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx

    I would begin by checking if there is any reason the user used in the LOGIN object can't write the file with the final name. Lack of permissions on target folder? Could the target drive have too little space left, or some sort of user quota? Any other software that might interfere, have you tried disabling anti-virus software temporarily? Could it be a matter of UAC? Is the destination some sort of special, OS protected folder?

    The unfortunate thing here is: The obvious problems have dedicated error codes. So 1359 can possibly be something arcane. Maybe try to log in as the user from the LOGIN object and try to rename the temp file in Windows Explorer or cmd.exe and see how that fares.

    Hth,


  • 6.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-14-2018 12:27 PM
    Furthermore, you didn't tell us about your agent version yet. If you're on a truly old agent, this may be a known issue in conjunction with newer Windows platforms, or a known bug. Unfortunately, the only advise there is to try an up-to-date agent (which, however, can not have a higher major version than the accompanying Engine), and see if that helps.


  • 7.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-16-2018 09:44 AM
    Agent version - '11.2.2+build.622' is the agent name.. Regarding the error "An internal error occurred" checked with the machine and everything seems to be working fine. The job does not fail everyday, it fails mostly when the file size is above 500 MB


  • 8.  One of our File Transfer Job fails to rename the file, It does not fail everyday.

    Posted 03-16-2018 09:51 AM
    Thanks. Regardless, you need to check for the things I mentioned above first, try to rule out any obvious (or less obvious) reasons why this may fail.

    Failing that, you could try to analyze that is happening by inspecting the actual sys calls (but that's an advanced topic that would, on Windows, probably involve the tools made by Mark Russinovich, e.g. process explorer and friends).

    Or alternatively, enable "tracing" of file transfers in the agent (via Agent properties or ini file), and see if the trace files have any information that points you and/or Automic support to the solution.

    But I'd definetly start by checking on permissions, disk space, renaming the file with the given account yourself etc., the stuff I wrote above.

    Hth,