Please make sure to backup before you try repair your easyfile installation or errors.
Use Ctrl+F to search for keywords related to your issue.
easyfile Forms Viewer errors
If you get the error “Unable to locate e@yfile forms viewer, please make sure e@yfile forms viewer has been installed before attempting this operation again.” when you try to view your declaration.
Open easyfile & login, go to Utilities > System Configuration and then click Install bottom right next to the e@syfile Forms Viewer Application path
If it won’t install from above, you can run the easyFileFW_Setup.msi which should have downloaded to your desktop from the above install.
- Download 1.3.4 from the following link to a known location – easyfile forms viewer download
- Double-click to install the downloaded “easyFileFW_Setup-1.3.4.msi“
- When you run it Defender or your AntiVirus might squeal, Defender throws up a message “Windows protected your PC” click “More info” and then “Run anyway” and it will install.
- Then when you View your first Declaration you will get another notice to download, click Download then close Forms Viewer and click View again and your declaration should open.
The file should be 85MB, if it is smaller it is corrupt and needs to be downloaded again.
Forms Viewer install corruption
FV opens but is blank, no blue dots – uninstall Forms Viewer and then delete the “e@syfile Forms Viewer” folder under ..\AppData\Roaming\ and the folder ..\AppData\Local\Programs\easyfileFormsViewer and then reinstall.
Adobe Reader Issues
- Adobe Reader is detected, but the version is too old
- Set Adobe Reader as your default PDF Viewer
- Declarations & certificates do not open, starts to load and then nothing happens, even though you have the correct 32-bit version of Adobe Reader and it worked previously. Backup then follow my Tweaked Install
IT Reg Issues
- Unable to get the IT number when clicking on IT Reg button, if you complete the employee record, save it with the 10x zeros, and go back into the record, clear the zeros and retry the IT Reg
Errors getting easyFile running
- #1009: If you get this error when trying to open a specific company. That company has become corrupted, you can also see this from the file size in the easyfile Local Store which will be around 3kB. – The simplest fix is to restore a recent backup. Be aware you’ll lose any changes you made to any other companies since your last backup. It is not possible to restore a single company via easyfile’s restore function. You can however restore a single company manually. See if this helps https://www.handshake.co.za/2021/sars-easyfile-employer-backing-up // If it happens after you have opened the company it can be due to missing info or an incorrect characters in a field. Essentially easyfile is expecting something & getting an unexpected result & throws an error. – Check your employer details are correct. [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.]
- #2027: Employer Contact E-mail address (2027). Invalid email address (missing @ symbol) // try Ctrl + Shift then see if you get an @ symbol
- #2028 & 2029: “Payroll Provider Software (2028 or 2029) is mandatory” Solution is to choose ANY payroll system in the first drop-down box & then in the second drop-down box, choose “INHOUSE” or “MANUAL” – If that doesn’t work – In easyfile select Synchronise first, then under Utilities, select EMP501 Status Dashboard and then in the top right hand corner click “Download Employment Taxes Validation” with your e-Filing login. Then in the ETV column a view button will appear next to the company & submission in question. If you then save the viewed letter to Notepad it will give you the certificate numbers and employees in question. Go to the employee edit screen call up the employee in question and view the certificate, click on save and it will tell you the code etc that doesn’t balance. Once certificates have been saved go back to the declarations screen and click on “Revise” at the top right to check you declaration and resubmit – all should now be ok
- #2037: Functions called in incorrect sequence, or earlier call was unsuccessful. // Looks like an incorrect JAVA version issue
- #2063: Not sure what causes this. // I have as yet not had a chance to troubleshoot this code.
- #3003: Can’t find location, usually happens during IRP Generation // Try the fix for IRP Generation
- #3013: File or directory is in use. Reboot and try again
- #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.
- #3119: Database file is currently locked
- #3123: Database disk image is malformed. 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.
- #3124: You’ll get the following message: “e@syFile has detected that your encrypted login credentials are corrupt and need to be regenerated.” Click “OK” to continue, if you click “OK”, it shows “Creating Key” and easyfile usually doesn’t work after this or you get stuck in a loop. To fix, the simplest is to restore a backup from a period before credential issues. If it still gives the error your backup credentials are also corrupted. Try another earlier backup. It is possible to resolve this without data loss by copying your credentials from the DoNotDelete folder in Local Store or from an older backup. Copy the key.txt and li.txt files to the current Local Store folder manually
- #3125: Unable to open the database file. // Most likely a JAVA issue
- #3138: File opened is not a database file. 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. Backup and then delete any db-journal files in the Local Store.
- #3214: easyfile is looking for the Java runtime in the wrong place, and Adobe Air duly reports the 3214 error.
- #3219: The NativeProcess could not be started. ‘%1’ – Most likely an incorrect Java version. My fix usually works.
- ITA10011: Potential Java issue
- ITA20004: Potential Java issue
- ITA40010: You need to upgrade to the latest version
The program can’t start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer
Make sure that your Windows is updated. Run the System File Checker to replace potentially corrupted system files. Reinstalling easyfile may also help.
To run the System File Checker in Windows 11/10/8/7, type cmd in the Start search box. In the result, which appears, right-click on cmd and select Run As Administrator.
In the command prompt window which opens, type the following and hit Enter:
Can’t see a period in the View Edit Employees dropdown
Request your 2021208 declaration on the declaration screen. When it opens check on the bottom part of your last page for the ‘certificates’ total. If there are no figures in that line the file imported was not for the 202208 period. If there are figures on that line, you can go back to view/edit on your certificate page.
Top right corner where you choose your certificate period, click on the 202108, then click it again, and 1 last time. The 202208 will open after a few clicks on 202108.
Error message “Reference number does not exist or User does not have rights to taxpayer.”
- Make sure EMP501 is active under your Organisations, Tax Types on your efiling profile.
- Use the portfolio login, the one that has the EMP501 submissions successfully activated and the primary user password. Look under portfolio. It will tell you what the easyfile login name is, sometimes has an _1 or similar after it. Password will be your usual. Or in efiling check My Profile, Profile Management, Linked profiles and use the e@syFile login name displayed there with the Primary password.
- Try use the old efiling username with the current eFiling password.
- One of my clients had 3 users on the company efiling and said between the three of us we have sorted our profiles and permissions.
- Another client said, “I had the same problem with multiple efiling portfolios. I moved the emp501 portfolio to the main one and that solved it.”
- In my case I selected to have my personal login as primary. My business profile has the rights to submit the emp501. Logging onto Easyfile I use my business username but personal password. It resolved the “rights issue”
- Force an update under the Rights Groups>Manage Groups> Update Group Details – make sure your user is part of the group
- In easyfile Utilities>Sync application
Errors running easyFile
- 6010 – Go to the error log, it will tell you how many records you should have. Then in the upload file, right at the bottom by 6010 you change the number to what it should be
- 2083 SEZ // On page 1 of the emp501 there is a space for SEZ code, delete the ZAR and it should work otherwise go to update the employer details and remove there before you do the submission. There is something like 6 foreign countries. You must go to the top of the list, there are a few dots. Click on them to let it show the dots, then it will be fine to submit…
- When I created the IRP5’s, only the first X created on Easyfile. // When doing the export from easyfile leave easyfile open even though its says complete.
- “Country of Issue 3075 may not be ZAF” – This happens when you input both an ID number AND a Country of Issue. The solution is to not select a country of issue, when you use an ID number (select “…”). Country of issue, is only used when you use a passport number instead of an ID number.
- “The application cannot be installed due to a certificate problem. The certificate does not match the installed application certificate, does not support application upgrades, or is invalid. Please contact the application author.” // Install as per my troubleshooting pages Tweaked Installation.
- Error Code 624, Source Codes should be exactly 4 digits. Record Structure invalid. // Check under your employer details to see if you have any special characters like commas in the address which throw this error.
- Employee SSEZ Code (3264) is invalid ‘ZAR’ // Usually occurs when doing older resubmissions. Run through all employees use 10 zeros for employees without tax numbers. Easyfile did not use to require tax numbers but now does.
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 e@syFile
ETI Calculated & IRP5/IT3(a) does not balance
Somewhere there is a cents difference. Change a certificate a few cents up and a few cents down. Check on you ETI monthly reports – when you add them all up to what cents you get and then check what is on the EMP501 import from SARS – which will be an whole rounded Rand and then change a staff member certificate on ETI with that cents amount up or down and it will work.
Manually captured IT3a and when you want to save it says ”The following field(s) are incomplete or invalid Invalid code ‘ “Employee”; Source Codes should be exactly 4 digits. Record Structure invalid.” All other employees (51) certificates saved without error msg. Problem only with the last one.
Check under your employee / employer address details if there are any special characters like ,~`’;:” and remove them and then try again.
ETI Error Codes
You can find more on your error codes in the PAYE BRS Employer Reconciliation listed above.
- ETI 3026: Employment Tax Incentive Indicator (3026) must be ‘N’ if Employment date (3190) is not completed
- ETI 3180: Period Employed To Date cannot be greater than current date +30 days
IRP Generation Fails
When exporting IRP5’s you get “Generation Complete” but you cannot see any or only some generated PDF’s. Your path length is too long. That is the combination of your directories and file names exceeds your version of Windows’ maximum path length. // Fix this by saving your IRP’s to your desktop or another short path and then moving them to your final desired location.
This also occurs when trying to save to a OneDrive folder. Not all files are generated.
Long Path Name Hack – this is a hack to the registry to remove the limitation
- Adobe Air Error Codes
- SA Tax Source Codes
- PAYE BRS Employer Reconciliation version 20.0.2
- DIV-easyFile-G001 – A Guide to the Declaration of Dividends Tax via easyFile- External Guide
- IT-easyFile-G001 – Third Party Appointment AA88 easyFileEmployer User Guide – External Guide
- PAYE-easyFile-G001 – easyFile Employer User Guide – External Guide
- PAYE-easyFile-G003 – Requesting a Statement of Account on easyFileEmployer – External Guide
Questions & Answers
Q: My laptop with the backup drive was stolen, so my newest available backup is 2017. Any way that I can get my IRP5’s back for 2018? // A: No, make sure to have another backup in future in another location and if possible in the cloud.