Registration Errors/Permission Errors

Tuesday, February 16th, 2010 | Events 3.0, Events 4.0, Events 4.5, FAQ, eAuthorize 3.5, eAuthorize 4.0, eAuthorize 5.0 | No Comments

Registering your plug-in by entering your license information in the plug-in configuration screen will sometimes fail due to permission issues (i.e. forgets the registration or cannot create registration) file on the installation computer. When this happens, typically it can be resolved by logging in with an account that has administrative permissions and then conducting the registration.

However, in cases of a networked computing environment that uses centralized authentication and application servers, there can still be problems with the permissions that prevent the plugin from storing and retrieving the necessary license info. The best resolution in such a case it to register the plug-in by using the plug-in’s built in registration function call.

From a startup script in your database, simply call the plug-in with the registration function and pass the necessary license code parameters. That way every time the database is opened the plug-in will be automatically registered.

Tags: Credit Card Authorization, eAuthorize, Events, FileMaker plugins, permission errors, registration errors

Events 3.0 and FileMaker Pro 7

Saturday, December 30th, 2006 | Events 3.0 | No Comments

No. If you are planning to use the Events plug-in in FileMaker Pro 7, you must upgrade to Events 4.

Events 3.0 licenses

Thursday, November 30th, 2006 | Events 3.0 | No Comments

The User License allows the purchaser of the plug-in to use the plug-in, within one company, at the number of computers specified in the License. The User License does not include rights to sell the plug-in, nor to distribute it or its activation code outside of the purchasing company.

The Developer License, however, allows the purchaser to include the plug-in in one or more solutions that the purchaser is selling or distributing to one or more of their customers. If a limited Developer License is distributed, then the limit on the number of users applies to each client company, but separately to each company.

The Developer License may only be used by FileMaker consultants and product developers, and not by in-house developers. Only the licensed purchaser may have access to the activation code; it must be inaccessible to the developer’s customer and to the end users. The Developer License does not include rights to sell or distribute the plug-in alone, nor to release its activation code.

Events 3.0 installation

Monday, October 30th, 2006 | Events 3.0 | No Comments

You need to install it for each FileMaker Pro client which is going to make use of the functionality of the plug-in. The files can be single user or shared with others.

On a Macintosh, go to the FileMaker Pro application folder. Once there, you will see a folder named ‘FileMaker Extensions.’ Place the plugin file in the ‘FileMaker Extensions’ folder and restart FileMaker for the plugin to load.

On Windows, go the the FileMaker Pro application folder (installed under Program Files by default). Once there, you will see a folder named ’system.’ Place the plugin file in the ’system’ folder and restart FileMaker for the plugin to load.