I have FMS17 running a system shell script that does the following:
Tar the latest backup folder and leave it into a specific 'tar' folder Mount an external volume share rsync external share and tar folder The script was running twice a day without any problem until last week when I upgraded the server OS from High Sierra to Catalina.
FMS event log just shows the following:
Schedule "schedule-name" aborted; aborted by user. Possibly it's a problem with permissions but how to fix it?
Browsing through my event logs, I am finding weird scripting errors, like:
... Information 645 ...local Schedule "Import Main (every minute 8-20)" scripting error (401) at "Import : Import Main : 36 : Perform Find". How can a simple «Perform Find» script step (which works just fine in the server scheduled script, btw.) generate a scripting error? Occasions where the FoundSet = 0 should be considered «normal».
I also have found other errors, that shouldn't be errors, like «Go to Record/Request/Page [ Next ; Exit after last ]», when there is no next Record.
What is the best way to prevent this? It’s clogging the log files.
Thanks a lot for any insight!
My users like using a FTP client as they can upload files "in the background" and keep working in FM. When I want them to upload the files straight through FM, I get compliance issues because of this (files could be 500Mb). If the file is already on the FMS I do PSoS, but when it's on the client desktop using FM will block them from working in FM during upload.
Is there a good way to achieve uploading from the client in the background, without blocking FM?
Who Viewed the Topic