Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 5135 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

I’ve got a multi file/Multi server deployment and a Server side scripting question. If you execute the script (ref attachment) via a server side schedule on the CT server FMS shows the script completed BUT.. the execution time was only 26 seconds and the data does not show up in the destination table as expected. None of the script steps show as client only, or hardware/network issues that would have abnormally terminated the script. Their were no backups running on the CA server at the time the sss was triggered.. Nearest thing I can figure is it’s a permissions issue… the script is set to run with username bob password 111111. The files on the CT server all have bob/111111 with full access permissions. Files on the CA server do NOT have bob/111111 with full access. All authentication is managed by Windows active directory "Help me Obi-wan your my only hope"

Drawing1.pdf

Edited by Guest
Posted (edited)

afaik, FMS cannot see a file on another server.

See: http://help.filemaker.com/app/answers/detail/a_id/7035/~/import%2Fexport-script-on-filemaker-server

Especially, "Important: In order to import/export to another FileMaker Pro file via a FileMaker Server scheduled script, the script would need to export the records from the FileMaker Pro file to one of the below valid paths and then import the records from this file into the other FileMaker Pro file."

If your goal is to synch the servers, check out SyncDek

Edited by Guest

This topic is 5135 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.