FileMaker fmxdbc error - (212): No such account

FileMaker fmxdbc error

Users trying to access FileMaker database hosted on FileMaker Server using ODBC/JDBC method might face the error “(212): No such account” due to following reasons.

1.      ODBC/JDBC sharing not enabled for the FileMaker database

2.      Incorrect authentication details (FileMaker account and/or Login Password details) used in connection string (of client application) or FileMaker DSN configuration settings to create connection with FileMaker database hosted on FileMaker Server

3.      The account might not have appropriate fmxdbc permissions in defined privilege set

4.      In case of “External Server” account type group, appropriate fmxdbc permissions might not be assigned to that group.

5.       “External Server” account might not be present in appropriate Windows active directory group

6.      “External Server” account authentication details mismatch between centrally-managed authentication server and authentication details used to connect FileMaker database

7.      All external authenticated accounts are not at the top of the list (when checked through FileMaker Pro using "Viewed By" option keeping "Authentication Order" selected in File à Manage à Accounts & Privileges

8.      No password is set for any of the existing FileMaker authenticated accounts (for e.g. Default Admin might have no password)

9.      Intermittent network issue between client application and FileMaker database

If the error “(212): No such account” occurs only for domain\group name type external authenticated accounts, as a workaround, such account can be created as FileMaker account with same credentials.