FMS is NOT a client. FMS cannot connect to files located on another FMS. It can only connect to files on itself.
I suggest using a 'robot' Client running this update.
stupid question: does FMserver B have the correct rights to modify File B ?
My first (perhaps obvious) question is whether you are able to run any PSOS scripts on Table A. If not the problem may have to do with other scripts that run on opening File A.
I had problems running a PSOS script on a particular file until I realized that, when the file was opened, a OnFirstWindowOpen script was run which had steps that weren't server-compliant; setting things up so that those steps didn't run on the server allowed the other desired script to run.
PSOS works file on File A
Found note by Matt Petrowski that says " There is a bug with Perform Script on Server where it will not pass authentication information to another file which is linked via EDS (external data source). The only solution around this is to call the script from within the file where it exists."
That dont help me solve tho
If this is true i'm up the creek. This would suggest so...
– A server-side FileMaker script that is running on one FileMaker server cannot open a database that is hosted on a different FileMaker server
Actually, adding to that:
it can be called from the main file but the EDS file needs to be already open by the client upon calling the PSoS script.
The EDS file is not always "active" after opening the main file, unless it is, at some point referred to.
The bug workaround is to call an Open File script first to make sure that it's open first, then run the script.
Another "workaround" is that it will be accessible if the EDS file has hardcoded credentials in the "Login using..." option in File Options. Not really encouraging, must say. But would get around the limitation of Server Scheduled scripts where Open File command is not available.
Edit: had to correct some grammar
That's the end-all-and-be-all of it. It just does not work that way.
Drop the data you need to an non-FM file format and transfer it over to the other server to be imported. Or use the XML/CWP interface to push data into the other server.
Could you elaborate on the XML/CWP solution?
You can create records and run scripts through the XML API, all you need to do is construct the correct URL. A server-side script on one server can use that to manipulate data and run scripts in a file on another server.
If you are talking about a lot of data then it would still be best to find an OS-level way to transfer the file over to the other server and put it in the other server's Docs folder. You can then tell the other server to import the file through one of those XML API urls...
Update in case anyone needs to know:
I followed the trail of this thread Remaining issue in FileMaker Server 13.0v2 with... . Report an issue . Bug Report . FileMaker Forums
And found that setting the previously inaccessible file to auto login with 'hard coded" account name and password works. Seems like PSOS or SSS does not pass credentials between servers.
As stated above, two servers cannot "see" each other to exchange data or run scripts on each other's tables. Historically FileMaker was mostly a client based database solution and slowly has become more and more of a server based solution. By this I mean traditionally all scripts were run on the User Interface and not the Server. And FM is now focusing on clients that do not have the ability to process data and totally rely on the server (e.g., WebDirect) and making use of technologies like Perform Script on Server, which has done a lot to improve end user performance.
If FM is bringing more technologies like PSOS and WebDirect to the Server, maybe it is about time that FileMaker bring the ability for one FileMaker Server to see tables in another FileMaker server, just like Coherentkris would like here and I would like it to work on my servers too. There are some workarounds described above and I've done them, but they are workarounds and not elegant. I think it is about time that FileMaker make this improvement.