Errors in getting easyFile running
- #3003 / #3004: while trying to load a backed up database, this is due to an invalid version of Java – follow the instructions to install easyFile properly
If easyFile Employer gets stuck on the “processing” message at start-up or after logging in, JAVA couldn’t successfully perform the decryption process. It’s also possible the incorrect versions could result in error messages (e.g. typical errors #3003 and #3004).
- #3214: easyfile is looking for the Java runtime in the wrong place, and Adobe Air duly reports the 3214 error. Make sure you have the 32-bit version of Java 22.214.171.124 installed
- #3115: Looks like a company database corruption – You will need to restore a backup. If you have more than 1 company, you will have to restore manually.
- #3123 & #3125: Looks like it is most likely corrupt easyfile.dbz, restore your most recent backup or another workaround is merging your company database file with a clean easyFile DB
- #3138: Happens when easyFile can’t read your data. This could be caused by a number of things, data corruption or incorrectly configured easyFile or security settings. Ensure you have installed as described above, that should sort out any Java issues. In Internet Explorer go to Internet Options and clicked on Advanced. Then under the security section turned off SSL 3.0 and turned on TLS 1.0.
- When trying to print out an old or new IRP5 easyFile gives the error “There was an error opening this document. This file cannot be found”. Uncertainty as to the cause but installing Adobe Reader 10.1.16 fixes it. Go here and click to download
- #1009: This is usually due to missing info or an incorrect character in a field. Essentially easyFile is expecting something and getting an unexpected result and throws an error. [If you are having the issue under Employees, make sure you have the country under the employee’s address details and then generate the certificate again.]
- #3119: Database file is currently locked
- #2037: Functions called in incorrect sequence, or earlier call was unsuccessful. – Looks like an incorrect JAVA version issue
Errors in running easyFile
On importing IRP5, file import fails and the message is displayed on the Import Payroll File Log Alternative Identification Number should have format CCYY/NNNNNN/NN when Alternate Identification Type is 1 – #3066
The certificate identified on the line which failed, is for a Personal Services Provider (PSP) company Possible Solution:
- When the record is a PSP, the gender is changed to “Company or CC” or “Trust”
- The ID number field will be changed to Company Number, which is the Company Registration number (CK number)
- Ensure the number is completed in the format CCYY/NNNNNN/NN
- Once corrected, export your IRP5 file again and import into [email protected]