Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

FMS doesn't Find/Attach External FileMaker Data Source

Featured Replies

I’m quite a bit puzzled:

There is a FileMaker database A hosted on a FMS 18 (Mac mini), 10.13.0.10

Working with database A using a FM Pro client as well as running FMS Script Schedules (SSS) or Perform Script on Server (PSoS), everything works fine.

Database A has an external FileMaker FileMaker database B attached to it, which is hosted on another Mac mini 10.14.0.10

Opening database A in FileMaker Pro Client App on local network 10.13.0.1/24 on any computer and accessing database B (which is on fmnet:/10.14.0.10/B) works perfectly fine.

Using SSS or PSoS on database B fails. It’s as if database B is simply not there for FMS.

 

However, another External Data Source attached to database A, a MySQL ODBC data source (10.14.0.3) works super fine, both using a FM Pro client and using SSS and PSoS.


Of course, I have checked, if the other server is reachable:

1) using Terminal command logged in as the same Mac user that FileMaker Server uses (fms_a):

p=$(ping -c 1 10.14.0.1  | grep "64 bytes") ; u=$(whoami) ; echo $p $u

Output: 64 bytes from 10.14.0.1: icmp_seq=0 ttl=63 time=19.404 ms  fms_a

2) running the same command from a Filemaker shell plugin (bBox) in any FileMaker client (that has database A open) generates the same result.

3) running the same shell command in a SSS or PSoS generates also the same result. fms_b is available.

But still, when running a SSS or a PSoS trying to access database B, no external database B seems to exist.

An nmap-scan of 10.13.0.10 (fms_a) from fms_a:

PORT      STATE SERVICE
80/tcp    open  http
88/tcp    open  kerberos-sec
443/tcp   open  https
3283/tcp  open  netassistant
5003/tcp  open  filemaker
5013/tcp  open  fmpro-v6
5900/tcp  open  vnc
16000/tcp open  fmsas
16002/tcp open  gsms
49168/tcp open  unknown
49328/tcp open  unknown
50004/tcp open  unknown

An nmap-scan of 10.14.0.10 (fms_b) from fms_a:

PORT      STATE SERVICE
22/tcp    open  ssh
80/tcp    open  http
88/tcp    open  kerberos-sec
443/tcp   open  https
445/tcp   open  microsoft-ds
3283/tcp  open  netassistant
5003/tcp  open  filemaker
5013/tcp  open  fmpro-v6
5900/tcp  open  vnc
16000/tcp open  fmsas
16002/tcp open  gsms
50004/tcp open  unknown
52647/tcp open  unknown
64204/tcp open  unknown

One interesting note: SSS and PSoS on Database B has worked before, on the same hardware using the same OS and the same FMS version in use now.

But I needed to completely reinstall the whole machine and wiped out the ssd and installed a fresh OS (10.14) and FMS (18), same versions. Everything is the same, except for:

I installed the FMS not as the default daemon user «fmserver» but another daemon user «fms_a». I have given this user sudo privileges and I am able to log in as this user on the Mac. This is the only difference to the setup before.

Anyone has any idea what could be wrong?

Thanks a lot,

G.

 

  • Author

OMG  —  I mixed up credentials!

Everything is fine now and works as expected.

...never touch a running system…

 

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.