I searched the info.plist in the contents folder of the Runtime.app application.
I find some files of that name but none of them were not locked.
I also have fmpa 11 and fmpa 12 installed.
The Logfile.txt is very informative: ;)22.04.2014 19:52:46 Log Started...22.04.2014 19:52:48 2040222.04.2014 19:53:08 ...Ending Log.
I had similar experiences with FM 12 and later which I always could avoid by quitting FM first and Restart FM before performing runtime binding. Looked like some wrong informations in the cache let FM believe that some of the RT-Ressources are still in use.
I found a solution after searching the web another time (searching and sorting are not so useful in this forum but I found the answer in this forum by using google).
I changed my OSX user to admin mode (restart) and after that I was able to bind the runtime!
That was no nice solution because I have to change the OSX user again to non-admin-mode and have to restart again…
after that I had another problem:
I want my runtime database to have the extension "fmp12" but that did not work.
after accepting "fmpur" everything works.
You can't specify .fmp12 as that is the file extension for the full up licensed copies of FileMaker Pro and Advanced. You have to use a different extension so that the OS opens your runtime "crippled" copy of the FileMaker Pro application that comes with your solution folder instead of a licensed full up application that your user likely does not have. (If they had that, they don't need the runtime, just the database file.)