S3/FTP Real Time Sync

[Luc23]

I suppose I could have told you this too, but it does not create a log file. It only creates it when I manually start the profile. Its almost as if I am missing some elementary checkbox to tell it that this is a profile that runs every 5 minutes even though the Next Run field updates correctly.

I'm creating a new profile now. I'll let you know how that goes.

[superflexible]

Hi,

it sounds like the scheduler is not having the necessary access rights to the log folder and INI file and maybe other folders. Are you running it as a service? Maybe you can try the standard Background Scheduler first, rather than the service.

[Luc23]

I recreated the profile and it seems to be running as it should now. The only differences I can find between the two profiles are Job-- Run As User-- I took out the domain of my Active Directory account and left it blank and under Job-- Use Unattended Mode-- I changed from the default of When Running Scheduled to Always.

Its possible that there are some other differences I didn't pick up on because I was messing with the first profile quite a bit to try and get it to work.

Another question related to this particular profile. Is there a way when moving files from left to right to get it to wait a certain time for a file to become stable? I just need to make sure that the file on the left side has been completely uploaded at the source before moving it to the destination.

Thanks for your help!

[superflexible]

Hi,
yes, "Run as user" usually causes only problems. For example, the log files probably went to some user-specific folder that you didn't see, and the user was not able to write to the INI file. Usually this option is not even needed. You can specify a user account when installing the scheduler as a service.

For local files, the program can wait until a file is closed by other processes. To use this feature, turn on "Database-safe copying: require exclusive access" on the File Access tab sheet.

Unfortunately this is not possible on the FTP side. If the file is on the FTP side, you need to get the program that creates the file to use a temporary filename until the file is complete. For example, if you use Super Flexible File Synchronizer to upload files, you can use the "Auto-Resume" feature which will cause it to use a temporary filename with .incomplete extension until the upload is complete. That way, you can exclude *.incomplete from other jobs.