After months of sufficient performance FileMaker doesn't launch anymore
(Beachball, then "FM doesn't react).

Deleting "com.filemaker.client.pro.plist" helps but for one term only.

Somewhere people were speculating re Java.

What could cause this?
What could I do?

Thank you in advance.

Regards

Peter

In article <E678ACF1-08AB-4BBB-89A8-C0AC1933A456%pfackelmann (AT) gmx (DOT) net>,
Iwan <pfackelmann (AT) gmx (DOT) net> wrote:

Need more info.

You don't say what platform, but from the sentence about the plist, it
seems to be MacOS X. What version?

Are you trying to launch from an alias, including an alias in the Dock?
Maybe the alias is broken. Trash it and make a new one direct from the
FileMaker icon in the Application folder.

If you are trying to launch it direct from the Application folder but it
is not working, that suggests something corrupted about your FileMaker
application. You could reinstall FileMaker, maybe delete it first, then
install. Use your original FileMaker install disk for these operations.

If that does not fix it, maybe there is something wrong with your Mac
user account. If everything else works OK, that is probably not the
problem, but you can check it out fairly easily: Create a new user
account on your machine, and see if Filemaker works correctly with that
new user account. If it does, but still does not work right with your
original user account, then you probably have a preferences problem
somewhere in your original user account. If trashing preferences does
not fix it, then you might think about transferring all your data files
to the new user, then trash the old user.

--
Bill Collins

On 9/04/11 4:06 AM, Iwan wrote:
Last this happened to me was c. 4 months ago; it was font based issues.
Clearing the plist did not resolve it. resetting default fonts, and
clearing font caches (Titanium Onyx or other tools) fixed it as I recall.

105 <cortical (AT) internode (DOT) on.net> schrieb:


Thank you for all the hints.
The problem had nothing to do with Filemaker.
It was a general lack of memory caused by Sophos' Intercheck.
I found out when trying the new iTuneUp.

Thanks again.

Peter