Hello!

I have a weird issue going on that is driving me nuts.

I want to use the RunShellScript command to open an application. When I use the command in the terminal or even call it via an Applescript (via the editor) it works just fine, the app launches and NO error code for loading the SM plugin shows.

HOWEVER, using the exact same code and running the RunShellScript function, the filemaker runtime will open fine, but I get an error that I need to have Java 1.5 or higher installed. And of course, once the runtime finishes loading, I get the SM error that the plugin may not have been installed properly. If I close the file and open it manually by clicking on it, it opens with no errors. If I use the script from within FileMaker, I get the Java and SM errors.

Any thoughts?

Thanks,

Stephen

PS - I have the current Java 1.7 and 1.6 installed, Mac OSX Lion 10.7.3, FMAdvanced 11, SM Plugin 4.132

Just as a follow-up...

No matter how I open the runtime solution via FM, I always get an error on the SM plugin. Other plugins load fine, but just this one has an error when I attempt to open a file (i.e Applescript, shell scrip, Open URL, etc.) Everything will open fine, outside of FM, as soon as I script it and run it, I get the error with ScriptMaster.

Any thoughts?

Thanks,

Stephen

I have exactly the same problem with two FM robots, one on 10.6.8 (Intel) and one on 10.5.8 (PPC).

An Apple Script is launched on close of the file, pauses for 120 sec, opens the robot.fp7 file again.

I already spend some time with 360Works support on this, they were really helpful but couldn't replicate the issue.

So we gave up.

I tried other ways opening the fp7 file via a script but I always receive this strange error.

Is the file opened by double-click, the problem never occurred.

Must be some AppleScript / Java conspiration

Alexander

I have exactly the same problem with two FM robots, one on 10.6.8 (Intel) and one on 10.5.8 (PPC).

An Apple Script is launched on close of the file, pauses for 120 sec, opens the robot.fp7 file again.

I already spend some time with 360Works support on this, they were really helpful but couldn't replicate the issue.

So we gave up.

I tried other ways opening the fp7 file via a script but I always receive this strange error.

Is the file opened by double-click, the problem never occurred.

Must be some AppleScript / Java conspiration

Alexander

Alexander,

Yeah, the only way for me to open up the file is to do an applescript that simulates the keyboard commands of cmd+o to open it. It's not elegant, and it doesn't always work as expected but it was the best solution for me to get around this error. I've tried different installations of Java and the SM plugin, but no go. Hopefully, we can figure out what's happening.

Stephen

I have exactly the same problem with two FM robots, one on 10.6.8 (Intel) and one on 10.5.8 (PPC).

An Apple Script is launched on close of the file, pauses for 120 sec, opens the robot.fp7 file again.

I already spend some time with 360Works support on this, they were really helpful but couldn't replicate the issue.

So we gave up.

I tried other ways opening the fp7 file via a script but I always receive this strange error.

Is the file opened by double-click, the problem never occurred.

Must be some AppleScript / Java conspiration

Alexander

 

Hey,

 

Any updates to your issue? I still need to do the applescript and open via keyboard commands to avoid this launching error with the ScriptMaster plugin.

 

Stephen

Hi Stephen,

 

indeed, just a few days ago:

 

display dialog "Restarting FileMaker Robot" giving up after 120

tell application "Terminal"

    do shell script "open '/Users/userfolder/Documents/myRobot.fmp12' -a '/Applications/FileMaker Pro 12/FileMaker Pro.app'; exit"

end tell

 

Now the trouble is gone.

Haven't tested it with prior versions of FileMaker 12 but I had the same issue on those computers after upgrading to 12.

 

Best,

Alexander

Hi Stephen,

 

indeed, just a few days ago:

 

display dialog "Restarting FileMaker Robot" giving up after 120

tell application "Terminal"

    do shell script "open '/Users/userfolder/Documents/myRobot.fmp12' -a '/Applications/FileMaker Pro 12/FileMaker Pro.app'; exit"

end tell

 

Now the trouble is gone.

Haven't tested it with prior versions of FileMaker 12 but I had the same issue on those computers after upgrading to 12.

 

Best,

Alexander

 

Great! I will write this into my application and see how it goes. I'll let you know. Thanks!

Alexander,

 

I tried the solution you mention but unfortunately I continue to receive the Java startup error. Unsure what could be causing this. The only option I have been able to get to work is the AppleScript key press workaround. That has been the only way.

 

Thanks,

 

Stephen

Stephen, 

 

too bad. Do you use the latest version of ScriptMaster?

This startup behavior is very erratic, the guys at 360works couldn't even reproduce the error then.

I think the AppleScript key press isn't a bad way.

 

Cheers,

Alexander

Stephen, 

 

too bad. Do you use the latest version of ScriptMaster?

This startup behavior is very erratic, the guys at 360works couldn't even reproduce the error then.

I think the AppleScript key press isn't a bad way.

 

Cheers,

Alexander

 

Yeah, I double-checked the version and I am running the current version. The AppleScript key press is working flawlessly at the moment, but just not as elegant as I would like. But hey, if it works, I am not changing it! With each new version of SM, I'll try again.