Error 1705: "File access is denied" for an EVENTLOG file

The error message "Error 1705 file access is denied" occurs when the MYOB Exo Employer Services software is intending to use a file and it is being denied access to that file. This often occurs when Windows has not released a file correctly.

As the "error 1705" message is caused by the MYOB Exo Employer Services software being denied access to the Eventlog file that it is trying to use at the time of the error, the options below can be followed to get access to the file and stop the error occurring.

• When this error occurs, click on the "Exit Software" button. This will close the software so then restart the software and retry what was being done when the error initially occurred. If the error reoccurs then repeat this process about 4 - 5 times. This is because Windows can require several attempts before it releases the file that the software is wanting to use.
• If the error continues, close all programs on the pc then reboot the pc. Once the pc has completed the reboot then restart the software and retry what was being done when the error occurred.
• For those users that are running the software over a network, the "error 1705" message may continue to appear. If this is the case, click on the "Exit Software" button to close the software on that pc then get all other users to close any copy of the MYOB Exo Employer Services software running on their pc's. Once all copies of the MYOB Exo Employer Services software are closed on all pc's, restart the software on the pc that has been getting the error and retry what was being done when the error occurred.
• If the error continues then get all Payroll users to close all programs and reboot their pc's. After the pc's have been rebooted then restart the software and retry what was being done when the error occurred.
• At this stage, if the "error 1705" message continues to occur then close all copies of the MYOB Exo Employer Services software running on the users pc's. Once all copies of the software are closed then get a member of the IT department to go to the server that the software is installed on and close all files that are in use from the MYOB Exo Employer Services software directory, e.g. the default directory the software is installed in could be called Payrollv. After these files have been closed restart the software and retry what you were doing when the error occurred.
• If the MYOB Exo Employer Services software is being run on Terminal Services or Citrix environments, it is possible that a users session has not closed correctly. Request IT to check on the server for any sessions that have not closed and files that are in use from the MYOB Exo Employer Services software directory.

The EVENTLOG files comprise between three and five files. These files have extensions of .DBF, .FPT, .CDX, .BAK and .TBK, e.g. EVENTLOG.DBF. The EVENTLOG files can be deleted and the MYOB Exo Employer Services software will recreate the files next time the software is started.

• If the "error 1705" message is continuing to occur despite having tried all of the above options then deleting the EVENTLOG files can be tried. No user should have any copies of the MYOB Exo Employer Services software running when the deleting of the files is done.

When the EVENTLOG files are deleted, all of the information shown in the EVENTLOG section of the Support Diagnostics screen will be lost. This information contains details of events that have occurred during the use of the software such as errors that have occurred, when upgrades were done, etc.

Need more help? You can open the online help by pressing F1 on your keyboard while in your software.

You can also find more help resources on the MYOB Exo Employer Services Education Centre for Australia or New Zealand.