Until Big Sur came out, FileMaker 19 was certified by Claris to run on two: MacOS 10.14 Mojave and MacOS 10.15 Catalina. Now, just like usual, Claris supports 2-3 MacOS versions at a time. And they’ve been working great on 19.2 and Big Sur 11.1. And, I also do run “old” not mission critical things – like backup copies directly on my M1 Air. I am careful on these things, so have opened anything precious over the network on my current FileMaker Server 18 running Mac mini 2018. It has happened on several computers now, too (all of which have almost identical hardware and are set up similarly).Lucky me, Claris released FileMaker Pro 19.2 about a week ago and tweaked it to work even better on Big Sur than it did on 19.1.

which makes it even more difficult to diagnose.

I am having trouble reproducing this error, too. Trying to print from any printer results in the same error message showing up. but it usually decides to happen while I'm out of the office and a customer is waiting on an invoice. There are no issues with any of the printers in any other applications, and this only happens once in awhile. I can print from any other application when this happens, and a restart of FileMaker seems to clear up the issue. Regardless of whether the print job is called from a script or from clicking File -> Print, and regardless of which printer is selected, on occasion an error message will appear that reads something likeįileMaker cannot print, because this printer is not connected to a port. Seemingly at random, FileMaker will decide not to print.

FileMaker Server Advanced 11 on OSX 10.6.

Several computers running FileMaker Pro 9 on Windows 7 Professional 圆4.

Filemaker pro server 11