FREE / FILESOFT DEVELOPER TOOLS
FileMaker error troubleshooter
Look up common FileMaker errors, choose the context and get a focused checklist. Keep HTTP statuses and FileMaker error codes separate.
Works in your browser. No account, uploaded inputs or saved work.
Start with the code and its source.
View the text checklist
Capture the failure, then narrow it down.
This is a curated starter set of 16 common codes, not the full Claris catalog. Search by number or a keyword such as “record”, “find” or “JSON”. Unknown codes link you to the complete reference rather than guessing a cause.
- Capture
Get ( LastError )immediately after the step you are checking. Later operations can change it. In an API response, inspect the FileMaker messages separately from HTTP status. - Choose the context and read the starting check. Reproduce the issue with a small, non-production example.
- Save the version, exact failing operation, expected result and actual response. Remove credentials and customer data before sharing diagnostic notes.
- Verify the fix with both a successful case and the original failure case.
Complete Claris error-code reference · Get ( LastError ) reference · Script error-handling walkthrough ↗
Filesoft counts page loads and selected button clicks in aggregate. Your criteria, error searches and colors are not included. Browser privacy signals and the analytics-off preference disable these counts.
STEP-BY-STEP GUIDE
Work through an example.
FileMaker error 401: an empty find or an authentication problem? ↗