Jump to content

Installation on Big Sur - "child process" error


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

Recommended Posts

  • Newbies

Brief report on the following problem: fresh installation of FMPA 19 on Big Sur will not allow the Scriptmaster plugin to initialize.

Of note, prior installations (e.g. FMP18 running on Catalina upgraded to Big Sur) work fine.

The solution (not sure which of the following did it):

- allow Full Disk Access for "Terminal" and "Filemaker Advanced" in the Security preference pane

- enable "Programming Tools", for good measure

- make sure your Startup Disk name is ASCII-compliant (mine was originally in unicode Greek)*

Restart and profit.

Hope this helps someone!

 

*I suspect that this is critical, as the java run-time (created on-the-fly by ScriptMaster) probably throws errors when a non-ASCII path is in the java HOME variable (check console for that)

Edited by xenophon61
forgot most important detail re non-ASCII startup disk name
Link to comment
Share on other sites

This topic is 1192 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.