FileMaker Pro 10 crashes when saving Preferences

[Todd Weller]

Our company (in the IT department) has been testing FileMaker Pro 10 and FileMaker Pro 10 Advanced running on Max OS X 10.6 for several months with great success. We just upgraded the rest of the office users to 10.6 and are now experiencing a problem we've not encountered before. Whenever any setting is changed in the "Preference" dialog, FileMaker Pro immediately crashes, and cannot be reopened unless we delete the FileMaker Preferences folder/file from the OS X Library Folder.

The primary difference in the install from our test scenario to the production environment is the type of user account. In the IT office, we are primarily laptop users with local accounts. The rest of the office is iMac computers with networked accounts and Open Directory logins.

We have already tried making the user a local administrator on the computer. We've also created several brand new home directories and logins with no success. The file server, home directories and user logins authenticate against our 10.6 LDAP. The FileMaker logins continue to authenticate against our 10.5 LDAP system as we transition everything over to 10.6.

Any insight that can be offered would be greatly appreciated. As long as our users don't touch the preferences, FileMaker behaves and performs as expected.

System info is as follows:

Client:

Mac OS X - 10.6.2

FMP 10:

FM Server:

Mac OS X Server - 10.5.7

FM Server Adv. - 10.0.2.206

[Todd Weller]

After posting this problem here, I did some more searching and found a thread for this exact same problem at FileMaker Forum. This issue is related to networked home directories in Mac OS X 10.6.

At this point, it appears the only work around involves deleting the FileMaker Preferences folder/file from the Library folder before opening FileMaker Pro.

Again, if anyone has any additional insight, it would be greatly appreciated.

[Bill_misc_IT]

I have a small company with about 10 FM users and network home directories. We are also periodically experiencing this problem. I've been using the same work around, while searching for a solution.