License key conflict with FMServer

[PBainbridge]

We have a workgroup with FMP9 installed, all with unique license keys, on a mix of boxes running Mac OS X Tiger. All of them (bar one which would require a separate post) run FMP9 with no problem - for local (on same HD) databases. However, when attempting to connect to files hosted on FMSA8.0.4 over the LAN, several of them report a "License key conflict with user FMServer".

It does not appear to be a problem with the databases as this occurs even with an unaltered version of one of the FMP9 sample files.

The main thing these problem machines have in common is that FMP9 was installed under a different OS X user account than the one which is attempting to use it. The original user account can connect without a problem. This is regardless of whether the user has admin privileges or not - in one case the admin user cannot connect whereas the standard user can.

Deleting the Filemaker preferences for the problem user has no effect, but if a new user account is created, it is able to connect to the server. However, I would rather avoid this if at all possible.

Connecting to the server-hosted databases works fine with all machines/accounts using FMP8.

So my question is, what's going on? And more importantly, does anyone have any idea how to solve it?

[Steven H. Blackwell]

Well, first FileMaker Server should not be running under any logged on user account.

As a daemon or service it should be run at the log-out prompt. Presuming that the Account that installed it however had full administrative privileges to the server, these conflicts should not be appearing.

Also, it is important to ascertain whether or not there are any instances of a user remaining connected when a user thinks he or she has exited the files. This might cause a conflict with an individual license of FileMaker Pro. A volume license key would be a better approach.

Steven

[PBainbridge]

FM Server is NOT running under a logged on user account and the account that installed it has full admin privileges. "FMServer" is not even an account that I recognise (although the short name "fmserver" applies to the "fmserver User" system account).

Regarding the instances of a user remaining connected when thinking they have disconnected, if this is indeed happening, why should this cause a license key conflict with someone with a unique license key? And how do they ensure they are properly disconnected in future?

Incidentally, as our workgroup comprises only 10 users, of which five were upgrades and five were new installs, a volume license key seems to be overkill (unless Filemaker are offering some better deals now!).