Skip to main content
Skip table of contents

Error 2091: "xxxx has become corrupted" regarding the ttaudit.dbf file

"Error 2091" implies one or more Exo Payroll files have been damaged. This article covers repairing damage to one specific file, where the message occurs when importing selected leave requests in the MyStaffInfo management console.

The process described below involves finding and copying files within payroll company data folders.

Errors made when following this process could cause loss of data, and MYOB recommends seeking assistance from your IT support.

Similar messages relating to different files or actions need an alternative solution - check this knowledgebase for other "Error 2091" articles.

Errors occur for different reasons such as, but not limited to, slowness in the environment, lack of system resources or incorrect user rights.

To fix the error
  1. Objective is to replace the damaged "ttaudit.dbf" file in the "issue" company data folder with a copy of the same file from the "Demonstration" company (an undamaged file from a backup would also work). Do not use this process for other files.
  2. Locate the Payroll installation folder. This has a default name of Payrollv but may be different - can identify via start-up icon properties. Company data is stored in Payrollv sub-folders:
    • The Demonstration Company is stored in "DATABASE".
    • The issue company folder name will be capitalised, and probably an abbreviation of name shown at logon screen.
  3. Ensure nobody has the software running, and as a precaution, make a backup of the entire installation folder.
  4. Locate "ttaudit.dbf" in the DATABASE sub-folder, make a copy of this file, and use it to replace the same file in the issue company sub-folder.
  5. The leave import process should now work correctly.

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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.