Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Runtime Trouble FMA12 MacOS X 10.8

169 views
Skip to first unread message

Bill

unread,
May 5, 2013, 10:15:23 AM5/5/13
to
Filemaker Adv 12 v 12.0v4, MacOS X 10.8.3

Unable to create working runtime file. Had no trouble creating runtime
solutions in earlier versions, but get an error and it does not work in
this setup.

I am able to create working runtime file of same database solution in
same version of FMA on Windows XP SP3. No problem. But it does not work
in Mac OS X 10.8.3

On the Mac OS, I get the error message during runtime creation:
<<The file is locked or in use>>

I acknowledge the error and the process continues.

Then when it finishes, I try to launch the runtime and it gives the
message:
<<The primary file "Debug" cannot be found and is required for this
application.>>

I have tried quitting and re-launching FMA 12, and restated the
computer. Same result.

What gives? Any idea?

David Stone

unread,
May 6, 2013, 10:19:38 AM5/6/13
to
In article
<bbcollins-81913...@70-3-168-216.pools.spcsdns.net>,
Bill <bbco...@earthlink.net> wrote:

> Filemaker Adv 12 v 12.0v4, MacOS X 10.8.3
>
> Unable to create working runtime file. Had no trouble creating runtime
> solutions in earlier versions, but get an error and it does not work in
> this setup.
>
> I am able to create working runtime file of same database solution in
> same version of FMA on Windows XP SP3. No problem. But it does not work
> in Mac OS X 10.8.3
>
> On the Mac OS, I get the error message during runtime creation:
> <<The file is locked or in use>>

Sounds like a file system flag got left in an odd state somewhere.
You could try repairing disk permissions using Disk Utility to see
if that fixes it. Also make sure that you don't have the DB files
open from elsewhere at the same time (e.g. via share), and that
you are logged in appropriately. Otherwise, I'm not sure!

Bill

unread,
May 6, 2013, 5:29:25 PM5/6/13
to
In article <no.email-B61D42...@news.eternal-september.org>,
Did repair disk permissions, then tried again to make a runtime in Mac
OS X. Still no dice.

Maybe I will reinstall FileMaker Adv 12 and try again.

David Stone

unread,
May 7, 2013, 9:28:33 AM5/7/13
to
In article
<bbcollins-66E32...@70-3-168-216.pools.spcsdns.net>,
A thought: is your DB set up with login permissions? If you are
logged in as a general user rather than administrator, that might be an
issue.

Bill

unread,
May 8, 2013, 1:00:40 AM5/8/13
to
In article <no.email-C68489...@news.eternal-september.org>,
Thanks for your thoughts about this.

The DB does in fact have login passwords. The DB is closed when I try to
make the bound runtime. However, it is the same situation on Windows
when I make the bound runtime, and that works fine.

But I also tried with a freshly created simple database with only an
Administrator account and no password. Failed the same way.

I've also posted the question on the FileMaker Technet and gotten a
couple of ideas about maybe FileMaker Server running in the background,
or maybe Windows running on the same machine at the same time. But I
have verified that neither of those conditions is true.

In fact, I even went so far as to try it on a different Mac running Mac
OS X 10.7.5, that does not have either FM Server or Windows installed,
and ran into the same problem.

I am beginning to wonder if it is a Mac Java problem. I wonder if FMA
needs Java to make a bound solution. I have really lost track of the
whole Java issue on the Mac.

Bill

unread,
May 8, 2013, 7:37:57 AM5/8/13
to
In article
<bbcollins-BBA6F...@70-3-168-216.pools.spcsdns.net>,
I installed the latest version of Java from the Apple web site. Still
have the same problem creating a FileMaker runtime solution.

Bill

unread,
May 8, 2013, 2:36:56 PM5/8/13
to
Turns out you have to logged in to an Admin account on Mac OSX in order
to create a Runtime solution using FileMaker Advanced 12 or FMA 11.

Found this out from FileMaker tech support.

This is not mentioned in the FileMaker Advanced 12 documentation or Help
file.

Turns out there is a FileMaker Knowledge Base article about this on the
FileMaker web site. I had looked for an article but did not find it. I
guess I used the wrong search terms.

Anyway, the issue is resolved.

Helpfull harry

unread,
May 8, 2013, 4:52:39 PM5/8/13
to
In article
<bbcollins-16D59...@70-3-168-216.pools.spcsdns.net>, Bill
I guess technically that makes sense since you are creating a new
"application", but realistically all they have to do is ask for an
administration password like any other sensible installer does.

Helpfull Harry :o)

Bill

unread,
May 8, 2013, 9:43:29 PM5/8/13
to
In article
<HelpfullHarry-0...@203-118-187-165.dsl.dyn.ihug.co.nz>,
Up through FMA 10, you could create a runtime without being logged in as
administrator, did not even need to put an admin password. That changed
with FMA 11, for reasons unknown to me, and continued in FMA 12.
0 new messages