Thorsten Kaltenborn

Hi Alan, in my case client version 5.x works fine, too. Only the server version can't access the container. Regards, Thorsten

Hi John, did you find a solution for this? I'm struggling with this for a few months now. Using the function on a Windows server throws 106. Using it on the client works fine. Regards, Thorsten

Hi Ryan, I tried that. After restarting Filemaker SM downloads JRE 1.8.0_152. But I still can't access container fields. Maybe there is a hint in the log file (attached)? Regards, Thorsten 360Plug-ins_Server.log

Hi Ryan, is it possible to force the download of the needed JRE? Since I still have problems accessing container fields I was wondering if there is an old JRE blocking the function. Regards, Thorsten

Hi! Tried Version 5.06 on my Windows 2012 R2 server. Unfortunately still getting FmCalculationException 106 on fmpro.getContainerStream. Regards, Thorsten

Hi shmert, can you explain me, which extensions or java files I have to install and where to put them? If I try your script, it returns just "error". Regards, Thorsten

Hi Andries, did you find a solution? Was on vacation so I didn't had time to investigate any further.

Today I read, that FM 16 has new security options. Maybe I can find the answer there? @John: Did you test my file on your server? Did it work for you?

Dear John, thank you for your help. You are right, new File would not work with this path. Unfortunately this isn't my real problem because I still get error 106 even if I comment out the whole export part of the function leaving only // SaveContainerAsFile( fm_field )" ; try { inData = fmpro.getContainerStream ( fm_field ) } catch (e) { return e } return true So the error is somewhere else.

OK, I made a simple test file which only contains the faulty functions. I also enclosed the 360Plugins_Server.log Maybe you can see, what goes wrong. I work on Windows Server 2012 R2. The password for admin is admin SM-Test.zip BTW: I realized, that the last command in the groovy script is wrong, but this is not the real fault

This a Filemaker error number? Have not thought of that. Unfortunately I am using a layout of exactly that needed table. The server script switches to the layout and searches for the record which is passed a script parameter. If found it passes the name of the container field to the groovy script. The container field itself is part of the table, not a referenced one. As I mentioned before, the script worked fine before switching from Filemaker Server 14 to 16 (I had to change the server, too). I will try to make a new (and smaller) database in which I can show you the behavior.

Hi there! I have installed ScriptMaster to Filemaker Server 16 under Windows Server 2012 R2 If I use getContainerStream in a server script I get an exception: Returns com.prosc.fmkit.FmCalculationException: 106 The containerField is defined as external / open. Exporting the content using Export Field Contents works fine. This worked fine before updating from Filemaker 14. Am I missing something? Regards, Thorsten P.S.: Same error occurs on fmpro.getContainerFileName