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.

Plugins not updating on FMS11

Featured Replies

Hi,

I'm trying to auto update some plugins using FMPA11-XP and FMS11-Win2k3. It doesn't work. I tried multiple script examples without any success. There is no error when running the script.

I executed the same script from my FMPA11-Win7 machine and it works. The plugins are in the c:usersmyNameAppDataLocalFilemakerExtensions.

Here are the setup :

FMPA11 on Win7 : It works

FMPA11 on XP : Doesn't work

FMS on Windows 2003 : Plugins are set to autoupdate.

There is no error when running the script.

How are you trapping for errors? There are several error codes specific to the auto-update process so it should be giving you some feedback. It won't pop up a dialog to say that something is wrong, the function will return an error code but otherwise it will fail silently.

For instance, to update a plug-in the function "FMSAUC_UpdatePlugIn ( pluginName & " " & remoteVersion ) would be called. This function will return a numerical value which contains the error code. The codes are:


code = 0 ; "The update was successful." ; 

code = -1 ; "The file to be downloaded is missing from the temporary folder." ; 

code = -2 ; "The ExtensionsSaved folder to contain the backup of the outdated plug-in could not be created on the client computer." ; 

code = -3 ; "The file to be replaced couldn't be moved to the ExtensionsSaved folder." ; 

code = -4 ; "The file to be replaced couldn't be moved to the ExtensionsSaved folder." ; 

code = -5 ; "The downloaded file can't be copied to the Extensions folder." ; 

code = -6 ; "The download file must be a plug-in file." ; 

code = 3 ; "The Auto Update plug-in is disabled in the FileMaker Server Admin Console." ; 

code = 5 ; "The download file can't be found in the AutoUpdate folder on the FileMaker Server computer." ; 

code = 6 ; "An error occurred on the computer running FileMaker Server as the file was being downloaded." ; 

code = 100 ; "The external function definition for FMSAUC_UpdatePlugIn contains an invalid or empty parameter." ; 

code = 101 ; "The function call from the client computer to the computer running FileMaker Server failed. The server computer might be running a previous version of FileMaker Server." 

As you can see just about all contingencies have been allowed for.

Also note that the plug-in folder has changed over time: from memory they are in different folders for XP and Vista/7 since the user's folder path also changed.

Check for permissions on the plug-ins on both the server and the client.

  • Author

The value returned is 0. I've checked the extensions folder there was no new plugins. There was no filemaker folder in local settings.

Create a new user account on the computer (so you know it doesn't have any plug-ins installed) and test the script again. Something should happen.

Post your file with the script so it can be checked.

  • Author

Ok, I found the plugins I wasn't checking in the right folder. They were uploaded into local settingsapplication data...

But there is still a problem. The plugins don't load from that folder. I rebooted FM and the plugins don't load.

I attached the file. This is only a test file.

autoupdate_plugins.zip

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.