Credit Card Authorization
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 | Comments Off
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.
eAuthorize 3.5 No Longer for Sale from our Website
Thursday, January 21st, 2010 | FAQ, eAuthorize 3.5 | Comments Off
Due to the recurring I/O exception error, and due to the recent changes to the PayPal gateway which render this product unusable on that gateway, we are removing this product for sale from our website.If you are a Windows user and using the Authorize.net gateway and need additional copies of the plug-in, please contact Sales.
eAuthorize 3.5 – I/O Exception Error
Thursday, January 21st, 2010 | FAQ, eAuthorize 3.5 | Comments Off
Over the last month we have been receiving more and more reports of an I/O Exception error which causes transactions to fail. The error seems to be limited to users running any Mac OS and using the Authorize.net gateway. The error appears to be occurring across versions of the Mac OS and compatible versions of FileMaker. Windows users on the Authorize.net gateway do not seem to be experiencing this error.We do not know what is causing this error. It could be a combination of a number of factors including but not limited to: product age, changes to the Mac OS or changes to the Authorize.net gateway.
We do know there appear to be two possible solutions for solving the problem.
1-Downgrade to version 3.0 of the plug-in. You can get the Mac version of the eAuthorize 3.0 plug-in by going to:
eAuthorize 3.0 Mac Download
Your existing 3.5 registration will work version 3.0. We are reasonable sure that this solution will work with up to version 7 of FileMaker and up to version 10 of the Mac OS. eAuthorize 3.0 will NOT work on an Intel Mac.
2- Upgrade to version 5.1 of the plug-in. Will eAuthorize 5.1 work for you? Yes, if you are using at least FileMaker 7 and a compatible Windows or Mac operating system. For more information on this product or to review requirements please see eAuthorize 5.1 Please be aware that there are some significant scripting changes that need to occur when upgrading from eAuthorize 3.5 to eAuthorize 5.1
