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!
Today I updated FM Server from 17.02 to 17.05. After this update WebDirect refuses to start.
When I click on the slider, it says "Enabled", but when I go back again it's Disabled.
I have looked for Java updates, but I already have the latest update applied.
I'm on macOS 10.13.6 with all security patches applied.
I haven't installed SSL yet, but it worked before this update so....
Where should I look more?
Please help! 😩
Im running Server 17 and have a number of scripts configured to run. Recently, some have stopped executing. What I mean is I select it to run (or the server runs it as scheduled) and then when I run it manually, there are records that have not been processed. So I checked logs log. "Last Scripting Error (802)"
Any recommendations how to resolve this?
Who Viewed the Topic