Jump to content
Peter Wagemans

Unknown Error: 2055

Recommended Posts

Someone any idea why FileMaker does not know it's own error codes?


This happened when a customer with FileMaker 18 is trying to perform a scripted QuickFind. I cannot reproduce it.

Share this post

Link to post
Share on other sites

Probably an error reported by a plugin or something else that's not FM. Have you tried capturing details using Get(LastExternalErrorDetail)?

Share this post

Link to post
Share on other sites

Hi Olger,

No plug-ins, and as I mentioned, I could not reproduce it myself, so there is no way I can debug this. Just thought someone here would have a more intimate knowledge of Unknown Errors in FileMaker. Apparently and by definition, these things are just unknown errors, and should be accepted as one of the mysteries of life.

Share this post

Link to post
Share on other sites

Good catch. Thanks. The error number in the linked article is completely different. But I suppose the cause of the error has been unknowingly taken away - I will follow FIleMaker's lead here and call this  "Unknown Solution: 1001" 🙂.

Probably a whole bunch of errors with QuickFind haven't been mapped to text strings yet. Looking at the linked article, it seems to me that the QuickFind engine is still going through a number of changes throughout the versions of server and client and have as different behaviour on both on them. Good to know, even though I do not expect to code QuickFinds in FMSE.

QuickFind is very useable and therefore a great feature, but it still has a number of unresolved problems, which lead to this kind of trouble.

In current (v18) behaviour it is not possible to disable QuickFind for all elements in your layout by "Select All -> Disable QuickFInd", if they are embedded within other objects, they are ignored. I know you can disable QuickFind in the layout properties, but my point here is that developers do not expect FileMaker to ignore those extra fields, and since they are buried into other objects, this is hard to debug, and causes all kinds of problems with QuickFind. Increasing the problem, QuickFind has no "default field properties" behaviour, which makes every newly added field to the layout enabled for QuickFind. Which makes way to many fields enabled for QuickFind, as most mortal developers forget to uncheck the box.

11 minutes ago, Peter Wagemans said:

Good to know, even though I do not expect to code QuickFinds in FMSE.

That was a stupid comment. The OP said the QuickFInd behaves differently when the file was hosted ( by an FMS16 ) and that is not the same as a server side script, of course. It does maybe point to improvements and might work correctly when the file would be hosted by an FMS18.

Share this post

Link to post
Share on other sites

Here's another thread on this forum discussing QF issues (related to popovers).


Share this post

Link to post
Share on other sites


I am getting this error as well, but from a GTRR script step. I turns out the relationship was invalid as the field on the right side of relationship ( child ) was using an unstored calculation.

Hopefully, this is useful to someone.

Kind regards,




Share this post

Link to post
Share on other sites

Thanks for that Joost.

Now that we know these are QuickFind issues with improperly or unsearchable related fields, we can now help FileMaker turn there Unknown Error message into something like “QuickFind Error. Some related fields on this layout cannot be used with QuickFind.”.

They will be so happy when we bring them the news. Imagine making something, and having this weird error number from your search engine you just can’t get your finger on. I know I would be happy if someone told me.

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By St3v1e
      As a complete novice to FMP, I'm attempting my very first database. We rely on storing our contracts on Google & Dropbox. I've been trying to either embed the pdf's into a "tab", or (my preferred option) to have an "Add URL" button to link to the online pdf.
      I tried adding a field and copying and pasting the URL, but it's not clickable, and I'd need to add another field for each pdf/contract.
      Is there a better more efficient way to do this?
    • By johnmarcel
      I have setup a layer with web viewer. I can maneuver within the website just fine but, I would like it if when the website loads it would send 4 carriage returns to get to a specific field within the website.
      If anyone has any ideas on how I can accomplish this it would be greatly appreciated.
      Thank You
    • By john renfrew
      Have copied a shell script which works in other settings onto a new machine
      Changes paths - it zips a backup folder and does a ditto command to copy as a zip file to an external drive
      I worked out that I needed to change the sudoers file to allow no password access to the script. Running the shell script in terminal was requiring a password, now it doesn't 
      Added the fmserver user to that too.
      If I run the sh script from the admin console as fmserver it fails straight away, if I run it as the local user with its password it appears to run but in fact times out with a fail message, both of which are about invalid account name or password
      The script is working fine when run through terminal, doe not require password, just not when triggered from console.
      Does anyone have any light to shine on this???
    • By Otis
      Actually, I guess this could apply to macOS Mojave as well, but is there any way to get the Send Email script to work when creating a Runtime solution in macOS Catalina?
      I'm using FileMaker Pro Advanced 18 to create my runtime solution. I created a button on my main menu to send an email. When I click the button in High Sierra (and all previous macOS versions) it works. But in macOS Mojave and Catalina, nothing happens.
      I know that Apple placed security limits on applications, but there's no way to add my runtime to the list of allowable applications to execute a script. What is supposed to happen is that macOS is supposed to have a pop up that allows you to click to allow this application to run scripts and access mail.app. So this works in FileMaker Pro Advanced 18. However, when I covert my solution to a Runtime, it's no longer "FileMaker Pro Advanced" and instead is considered a Runtime app.
      In macOS Catalina, manually adding my runtime solution to this area didn't work: System Preferences > Security & Privacy > Privacy (tab) > Accessibility > (Allow these apps below to control your computer)
      Is there any way to allow a runtime to have a simple button to click Send Email in Catalina?
      I'm stumped.
    • By Faldo
      Good morning
      I was wondering if anyone had template for a basic home accounts sytem or the schema for the databases.
      Thanks again.
  • Who Viewed the Topic

    7 members have viewed this topic:
    thierryfl  PedroAlex  Randy Bennett  Stefano Parmeggiani  cat traveller  comment  Steve Martino 
  • Create New...

Important Information

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