File access, credentials, and native operations

File-access failures occur before or during a native FileMaker operation. Ask the coding agent to report the structured error code and FileMaker database error number, not only the surrounding sentence.

The file cannot be reached

Confirm that the connected target in adt.json matches the file:

  • A closed local file uses a direct path to its .fmp12 file.

  • A file open in FileMaker Pro must have peer-to-peer or network sharing enabled before another process can open it.

  • A file hosted by FileMaker Server uses its fmnet://<host>/<FileName> address.

Paths beginning with ~ are not expanded. Use a project-relative or absolute path instead.

Authentication failed

FileMaker error 212 means the account name or password was rejected. Confirm the account name and that it still has the necessary privilege set. Let ADT open the native credential prompt; do not send a password through chat or place it on a command line.

Do not repeat rejected passwords without checking them. FileMaker can temporarily lock an account after repeated failures.

Permission denied

FileMaker error 207 means the account authenticated but cannot open the schema for modification. Native schema, script, and layout reads and writes require a [Full Access] account, including dry runs. Changing the password will not fix this error.

The schema is locked

FileMaker error 303 means another session holds the schema lock. The report may identify that session. Close Manage Database, the relationships graph, or an open script editor in FileMaker Pro, then ask the agent to retry.

A lock acquired during a batch causes the batch to abort and roll back.

The operation is unsupported

An unsupported-operation result means ADT does not expose the requested FileMaker behavior. Ask the agent to show the limitation. Do not treat a nearby operation or manual workaround as the requested change.

See Errors and diagnostic messages for other common codes and FileMaker credentials for credential handling.