1 of 1 people found this helpful
According to FileMaker, FileMaker Pro 11 is not compatible with OS X 10.9.5. See this:
From the report, it looks like it stepped outside of it's allocated space in the OS.
Not sure if there is a fix. So that stated, you might try doing an install from the original media.
My apologies, I don't think this is very helpful.
I did install from "original media" (download). I was trying to keep my old PB alive for this reason and it just gave out. So, I'm hosed?
The script has a loop and works for about 4 records before crashing. I don't have anywhere else to test this.
Thanks for the link, Bruce!
1 of 1 people found this helpful
I'm not sure if that is a correct reading. According to the FM Support page "Version stated is the minimum requirement. The software may also work with later versions certified by FileMaker, Inc". Certainly I have no issues with running FM 11.0.4 on Mac OSX 10.9.5
Can you post a copy of the problem file? If so I'll try it on my 10.9.5 system and see if it will run. If you want contact me directly and we can provide a copy through dropbox if you don't want to post it.
I have a MacBook pro running 10.9.5 with FMA 11 and don't seem to have any problems running FMA 11. It actually has version 9,10,11, 12 and 13. All of which seem to run ok. Admittedly, I haven't had to do much work in 9,10 lately. I had some minor 11 updates for client recently.
The Notebook has been around a while and was recently updated to 10.9 because my FMS development server had to go into the shop. So I updated the OS so I could install FMS 13 on it. FMA 11 was already installed.
One last thought on this, is it possible that this is a hardware issue? You said this was a new system. Is it possible that you have a bad memory chip? You may want to take it in and have it checked.
As a test on my system, I have a database that runs through a series of fairly complex loops to setup meeting assignments. So I opened it up and had it run the script that did this. It ran without a problem.
Thanks! "get it checked" is 2 hrs away ( one way ) and not worth the trip until I have to travel there for clients.
No, I cannot post a copy of the file. Sorry, behind security. I'm hoping they upgrade (and they plan to) and this would not be a problem - but for now it is.
I had to get a new laptop because the old one would not install FM13 (& could not upgrade). It's working fine until this one script...
I hope I'm not driving you crazy with this, my guess is you already thought of all this...but.. A few last thoughts
Have you checked the file for corruption? Possibly something here could be the cause.
Does the script use recursion? Is it possible that it is going past the recursion limit?
Have you tried taking a copy and converting it to 13 and see if the script runs ok?
All things I thought about, thanks!
no file corruption
on VPN, secure, cannot make a copy to test.
oh joy! today the crash has this (no changes to script or other variables), but I did run through with debugger on :
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000fffffffc
Not having fun until client upgrades...
NOTE: this has been resolved. You may be seeing this as "new content"
1. because I moved it from my space to discussion
2. because I am posting this update