Remote connect with NFS network home dirs (2 Comments)

Issue report by Robert Fakes

Product

FileMaker Pro

Version

12

Operating system version

OS X 10.6

Description of the issue

Cannot connect to a database running on FMP 12 server from a client running FMP 12 on OS X 10.6 when using network home directories over NFS instead of AFP.

Steps to reproduce the problem

Mac server using NFS for it's home directories automount.

Expected result

To be able to connect to the db remotely.

Actual result

You cannot connect remotely.

Exact text of any error message(s) that appear

The file "Database name" could not be opened. Either the host is not available, or the file is not available on the host.

This is after manually typing in the correct path, as the bonjour list does not populate on it's own as it does on my laptop.

Also this is produced in the system log:


Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: omniORB: sslContext.cc : error:02001002:system library:fopen:No such file or directory
Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: omniORB: Assertion failed. This indicates a bug in the application
Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: using omniORB, or maybe in omniORB itself.
Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: file: /Users/alexchen/Projects/KillerRabbit/Shared/OmniORB/4.1.6/MacOS/../src/lib/omniORB/orbcore/giopStreamImpl.cc
Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: line: 646
Aug 28 16:01:44 it1-spare [0x0-0x3a03a].com.filemaker.client.pro12[575]: info: implHead == 0

Workaround

The only way around this for me is to

1. Change back to AFP for network homes
2. Change user's network home to the AFP option in Workgroup Manager.
3. Login as user on client, start FMP 12 and it connects fine.
4. Go back and set everything back to NFS.

I don't want to have to do this for every user. We use NFS as it is more reliable.


This breaks again if I go and delete the ~/Library/Application Support/FileMaker Pro/12.0/root.pem file, until I go back to AFP and it works.