Check the Get Info (cmd-I) on your runtime solution file. If it is set to open with "Runtime (…)" then it will give you that message when you try to open it instead of opening your runtime.app.
By any chance did you:
• try to open your runtime solution instead of your runtime.app
• change the name of your runtime.app
• delete your runtime.app
• move your runtime.app to another folder?
Jade - thank you for taking time to respond. I have only made two runtime solution files before this, one in FMP 10 and another in 12, and didn't have problems. But I remember being confused which file is which (runtime.app vs runtime solution), and which one should be opened first. Anyway, I tried your suggestions: First, here are my solution files:
Info on FindKeys.fmpur shows it should be opened with Runtime (default) (13.0.9). I Tried renaming my Findkeys app file to that, but nada. But I notice that the icon for the app is a circle with a line through it (which I'm guessing isn't good). I also tried dragging the app to another folder, nada.
So, bottom line, I'm still stuck. Maybe the screen-shot will give you some more ideas. Thanks again for your looking into this.
Yep, your FindKeys.app doesn't look too healthy. (It might be an alias pointing to some other location—I can't tell since the image is a bit fuzzy) . Recommend you delete it. Then rebuild your runtime. Make sure you have no errors during the build process.
The Findkeys.app should be put into the same findkeys folder as Findkeys.fmpur.
Double click the Findkeys.app to open your runtime.
The Findkeys.fmpur should be set to open with Findkeys.app not Runtime (default) (13.0.9) using Get Info.
Hope this settles it for you.
Hi Jade ... I'm back. I reran the build and everything is in the same folder, but still no go. This time when I got the "File is Locked or In Use" message I dragged the window down to see the window behind it. It seemed to be working on info.plist when it bombed, but maybe not. Here is a screen shot.
Also, here is a screen shot that shows the icon on the findkeys app file
Thanks so so much for looking into this. You are indeed a cyber guardian.
Hi Schamblee - I'm getting ready to try a clean install, but I have one concern. After I installed FMPA 13, I got rid of the FMPA 12 app. The Library / preferences / com.filemaker.client.advanced12.plist etc. files are still there.
My concern is that i purchased an upgrade version to go from 12 to 13. Will the upgrade still install if the 12 app foler is missing?
Thanks - Bill
During the build, it looks like it is trying to access/write an info.plist into your user's library or system library. That file doesn't have the correct permissions or is damaged. This appears to be what is hosing your FindKeys.app.
Since your are on OS X 13.x , I recommend you use Disk Utilities (in your Applications/Utilities folder). See if you can verify and correct your disk's permissions using Disk Utilities.
Also, make sure you are logged into your Mac's administrator user account if you have more than one user account.
Yes, you will need license key from 12 and the license key for 13.
Here are the steps to build a runtime, if this is what you are doing then I will suggest the clean install.
1. Do not open your database, just open FM
2. Developer Utilities
3. Click Add then select your fmp12 database
4. Click Specify under Project Folder, then select the folder when the runtime should be placed.
My test I used Applications/SampleRuntime/
5. Click Specify under Solution Options.
6. Select Create Runtime
7. Enter a name in the Runtime Name field then select ok.
8. Click Create.
Thanks for responding. I am indeed doing the steps you list, so I guess I will try a rebuild. Fortunately I still have the key for fmp12
Hi Jon - The disk utility with El Capitan no longer does permissions. Apparently that is no longer needed (I remember reading something about that recently).
So, per schamblee's suggestions I will try a clean reinstall of fmp13
Thanks - Bill
Good luck with the reinstall, Bill.
Let us know how it goes.
Thanks so so much. I did a clean install of FMPA 13 and now it works fine. Kinda glad it wasn't something stupid that I was doing ... you know, for the old ego's sake.
Thanks for the follow-up Jon.. It went just fine. Everything is working just like it should, Hallelujah!