Good day Sage Community!
This seems to be a common message experienced by a lot of users when installing the new e@syFile software and launching it for the first time. It could take a few minutes to connect as it is starting up the connection to the server. You can close the application, wait about 15 minutes, and then try again, but in many instances that does not resolve the issue.
There is some data out there explaining aspects around the installation, so I have compiled it here which seems to be the route cause of the issue and once applied, resolves the error.
The new version of e@syFile uses a Chromium browser exclusive for the application. It has two components, it has the browser application and the actual application that runs on the browser. Most of the challenges are simply due to restrictions on the folder, host file and the server that's installed in the task manager. The user installing the program must have access or rights to install the program. When running the installation file, it installs EasyfileEmployer v2.5.8 which includes EasyFileServer, as well as EasyScan 2.0.0. Then installs e@syFileTC v1.0.2 and it should open e@syFileTC once installed. The software creates firewall rules to open port 42690 and it does this when in the DOS prompt during the install. EasyFileServer runs as a service and you can see if it is running by typing services.msc into the search bar and hitting enter. Search for EasyFileServer.
Check your Hosts file as the install adds a line but does not always add it correctly: 127.0.0.1 easyfile.sars.gov.za should be at the bottom of the file
Make sure it’s on its own line. To locate the information (Windows 10 and 11)
- Press the Windows key
- Type Notepad in the search field
- In the search results, right-click Notepad and select Run as
administrator - From Notepad, open the following file: C:\Windows\System32\Drivers\etc\hosts
- Make the necessary changes to the file and then select File>Save to save your changes
Check now if the EasyFileServer service is running. The application should then launch successfully.
