By any chance, is your database.fp7 still open in FileMaker Pro Advanced?
If so, quit FileMaker Pro Advanced and reopen it without opening your database. Then select Developer Utilities and add the database.fp7 to the solution files list.
The database is closed when I attempt.
If you make a NEW supersimple database, does it exhibit the same problem?
Win ver?? or Mac OSX ver??
Do you do monthly maintenance?
Has this EVER worked on another database?
This is OS X.
The database, as said, was originally created in FM Pro 7 and has been updated/maintained for (many) years.
We have finally updated to FM Pro 11. The database seems to work fine in FM Pro 11 Advanced, but fails when attempting to create the runtime. Runtime always worked in FM Pro 7.
I will try to make a simple, new database (I would expect this to work). Won't get to that until Monday.
A couple of things to check if you're still stuck:
• If you have copied this database over from another Mac, ensure that your user's privileges are Read/Write using Get Info.
• Also try verifying and repairing your Disk Permissions using Disk Utility
"This is OSX" is not very specific OSX 10.3, 10.4, 10.5, 10.6, 10.6.6?
May seem simplistic, but can make a difference.
Version of FMPA? Exactly?
OS X is 10.6.6
The legacy database is 6-10 years old (?), was originally created in FM Pro (3?), stable in FM Pro 7 Developer until now and has lived though just about every iteration of OS X in the meantime.
I just got FM Pro 11 Advanced (11v2; electronic version (via site license) from download named 'fmpa_18.104.22.168.dmg') and attempted a quick conversion before I was out the door for the weekend. This was the result.
Before posting to this board, I did attempt a search to see if this was a common problem. I only found this on a different forum, no solution posted:
They do mention a .plist file in v10 that is not present in v11. I am not sure where that .plist would be located and if it would apply to a legacy v7 file. Will follow up on that on Monday.
Permissions issues could be a part of this, I will explore that further come Monday too.
Thanks for the ideas so far.
FYI: The next solution file to be copied after info.plist is Xerces, FMP's XML translator.
Here's the workaround, the clue was in the thread I linked to previously (http://fmforums.com/forum/topic/71194-fmpa-11-runtime-error/)
I opened the package contents for both a legacy (v7) runtime and the new v11 runtime.
The v7 runtime indeed contained an 'Info.plist' file which was not present in the v11 runtime.
I copied the 'Info.plist' file into the v11 .app package and -- voila! -- it suddenly became an operational runtime.
So I indeed have a workaround for this. I'd prefer not to have to do this each time, so any ideas about actually fixing this are still welcome.
I had this same problem with a file that I just created in FM11Advanced. It occured in the same place while creating the runtime files.
After much searching, I found the solution below. I basically solved my "problem" by giving myself admin privs on my MAC.