Jump to content

Peter Wagemans

  • Content Count

  • Joined

  • Last visited

  • Days Won


Peter Wagemans last won the day on August 9 2018

Peter Wagemans had the most liked content!

Community Reputation

3 Neutral

About Peter Wagemans

  • Rank
    just passing through

Profile Information

  • Title
  • Gender
  • Location

Contact Methods

  • Website URL

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version

FileMaker Partner

  • Membership
    FileMaker TechNet
    FileMaker Business Alliance
    FIleMaker Platinum Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I downloaded the "a" variant, and now everything is OK. Same license cert file.
  2. Thanks Wim. I spent some time on my reply and missed your very helpful remark. I did install a fresh Catalina server with FMS 19 last week without any issues, I should have thought about this.
  3. Same here. FMS doesn't list the files using fmsadmin, not even the sample file, but it shows it in the web driven admin console. When trying to open a file, no log entry is generated in the event.log. No error. No nothing. The fact that the web admin console shows the files, and the fmsadmin command doesn't, is a clear indication that something is completely off. fmsadmin set serverprefs RequireSecureDB=false is not supposed to be necessary when you first start up FMS. As I wrote above, even the sample file does not open. It seems a bit strange to me that FMS19 would not even open up th
  4. Nick has codesigned the plug-in again and this resolves the issue. http://goya.com.au/files/beplugin/4.1.2/BaseElements.fmplugin.zip
  5. I've send an urgent mail to Mark and Nick, so they are aware of the issue.
  6. Got a call this morning from a customer, his solution started with a plug-in loading error. After some research, I discovered that pre-Catalina Macs did not load the plug-in anymore. FileMaker apps that remained running overnight had the plug-in loaded and functional, but when restarting FileMaker, the plug-in did not reload. My first thought was that some certificate expired, allthough a "codesign -dv --verbose=4 BaseElements.fmplugin" does not reveal any expiry date. Super strange. It had to be something expiring though. So I codesigned it again, with my own Mac developer cert
  7. 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.
  8. Hi Stephen - I initially thought this was a APFS thing, but trying it on a High Sierra VM, I saw the same behaviour. Windows does what is expected, and gives an error. Creating records, changing field definitions, saving a copy as you mention, exporting, everything continues to work. Even renaming your file in the Finder is possible, without any error. This is also a nice one: make a script, select the export records script step. FileMaker format, make sure you are in your file its directory and type in your current file name. FileMaker asks if it can replace your file name
  9. macOS Catalina. 1. Make a new file and save it to the desktop 2. While the file is open, move it to the trash 3. empty the trash The trash is emptied without any error. Weird. This does not seem right, in fact it seems VERY wrong. Can anybody reproduce?
  10. 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
  11. 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.
  12. 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.
  13. Got it and tested. It works indeed. On both machines. The LicenseCert file must still be in the downloads folder. Still not indicated in the installer. Poor FileMaker. http://fmdl.filemaker.com/esd/fms_18.0.3.319.dmg
  14. The link in that mail has long expired, Wim. Of course your advice is excellent, but I wonder why I need a sales person for technical support, and why the article https://support.filemaker.com/s/article/FileMaker-and-macOS-Catalina-Compatibility?language=en_US is not mentioning this problem, while it is simply happening when you try to install FileMaker Server on a Catalina machine. We do a lot of new installs, and I'm sure some collegue of mine recently did a fresh license install somewhere. So I will probably get this fixed somehow today... But... why does FIleMaker not provide full ins
  15. I am having the same issue here. On 2 separate machines, one is as good as a clean install. Problem: I have 18.01 and updaters, but I need a 18.03 installer, which... FileMaker does not provide. How to handle this?
  • Create New...

Important Information

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