Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

I'm trying to upload some files using a FileMaker script scheduled on the server. I'm getting an odd error though. Here are the details:

ERROR MESSAGE: Error uploading file. java.lang.IllegalStateException: SCPluginModel#setResource must be called from the EDT

DESTINATION PATH: attachments/000091

SOURCE_PATH: /tmp/mailmate_downloads/34/CIMG0257.JPG

FILE SIZE: 78606336

SystemVersion: 10.6.8 (OS X)

Java Version:

java version "1.6.0_15"

Java™ SE Runtime Environment (build 1.6.0_15-b03-219)

Java HotSpot™ 64-Bit Server VM (build 14.1-b02-90, mixed mode)

SuperContainer version 2.81

SuperContainer Companion Plugin version 2.81 (in .../Database Server/Extensions)

Files are loading just fine client-side (also using v2.81 of companion plugin). It's just server-side that's not working. I don't think it matters that FileMaker can't see that directory from a server-side script, because I'm pretty sure I've successfully loaded files from this directory before.

Does anyone have some advice?

Thanks in advance.

Donovan

  • Author

It appears that the server plug-in was actually not running v 2.81. I may have looked directly into the plug-in package to check its version. Restarting the database server changed its behavior, so it looks like this may have been due to a discrepancy in versions.

  • Author

Actually, I take that back. I just encountered the error again when attempting to upload files on a scheduled script. The changed behavior I referred to in my previous comment occurred when attempting to run the script via a daemon (but that's a separate issue).

  • Author

360Works helped me through a different avenue, so here's the solution for the record. I had "showProgress=true" set, which obviously wouldn't work when being run server-side. I am told that the next update will handle this issue for the user.

Create an account or sign in to comment

Important Information

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

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.