Skip to main content
Skip table of contents

Performing a System Services Data File Rebuild

This support note applies to:

  • AO Tax (AU)
  • AE System Release (NZ)
  • AE System Release (AU)
  • AE Tax (AU)

These instructions require technical expertise

Make sure you know what you're doing and are using one of the products listed. If you're not sure, ask your IT professional or MYOB.

Article ID: 27078

If you use MYOB Accountants Enterprise (AE) or Accountants Office (AO) applications, these use System Services data files and structures to store the data.

You may need to perform a System Services data file rebuild when error messages appear relating to the DS6OP010. The DS6OP010 will generally need to be restored from a previous backup replacing the current file located in the SOL64 or TAX directory. System Services data is stored in the file DS6OP010 located in your System Release program directory. 

A System Services data file rebuild may be necessary to correct the following problems, which prevent you from using System Services:

  • "DS6OP010 corrupt" message.
  • "System Services control record is missing" message.
  • "Bad link in DS6OP010" message.
  • System Services hangs on the splash screen with no error messages on all workstations.

    To fix the issue perform the steps below:

  • Contact your network administrator or network support if you require help restoring the DS6OP010 file.
  • You must ensure that the SR Dal Server is stopped and that VizPost/Background process is closed on the SQL server. To do this, go to Control Panel on Server, select System Release DAL and select Stop once all users logged out of Tax if using SQL tax. Once the rebuild has completed, will need to restart both services.
  • Ensure that all users are logged out of System Release before proceeding.

For details on identifying your System Release program location refer to Finding the SOL64 or Tax directory

To rename the DS6OP010
The DS6OP010 file resides in the System Release folder. 
  1. Open Windows Explorer or Computer and navigate to the System Release folder.
    MYOB AE: x:\sol64\
    MYOB AO: x:\MYOBAO\AOSQL\Tax\
    Where x:\ is the drive where System Release is installed. The files and folders appear.
  2. Right-click on the DS6OP010 and select Rename. The file name activates and is highlighted.
  3. Press END. The cursor flashes at the end of the file name.
  4. Type .OLD and press ENTER. The file name changes to DS6OP010.OLD.

    OLD is not a compulsory name change. There may already be a file with this name. OLD can be replaced with other character sequences such as YYMMDD representing the year, the month, and the day for example 140201 being 1st February 2014.
To restore the DS6OP010 from a backup

The DS6OP010 file will need to be restored to the System Release installation folder from a backup that occurred the previous day or before the error messages started to occur on the DS6OP010.

For more information on backing up MYOB files refer to Backup recommendations for MYOB program and data files 

To check the size of the DZZOP010
The DZZOP010 file resides in the \S6 sub folder of the System Release folder.
  1. Open Windows Explorer or Computer and navigate to the System Release sub folder.
    MYOB AE: x:\sol64\S6
    MYOB AO: x:\MYOBAO\AOSQL\Tax\S6
    Where x:\ is the drive where System Release is installed. The files and folders appear.
  2. Right-click on the DZZOP010 and select Properties. The DZZOP010 Properties window appears.

    If the size is greater than 20Kb, 20,480 bytes, then continue with step 6.


    If the size is less than or equal to 20Kb, 20,480 bytes, then proceed with How to perform a rebuild on the DS6OP010.

  3. Click Close. The DZZOP010 Properties window closes.
  4. Right-click on the DZZOP010 and select Delete. The Confirm File Delete window appears.
  5. Click Yes. The DZZOP010 is deleted and the Windows Explorer screen appears.
  6. Reinstall the current version of System Release.
To perform a rebuild on the DS6OP010
Do not interrupt any of the following routines while in progress. Interruption of the data file rebuild or EPRESET routines may cause data corruption and require a restore from backup.

Ensure all users have logged out of System Services and remain out for the duration of the procedure.

Run this process from the System Release folder.  For details on identifying your System release program location refer to Finding the SOL64 or Tax directory
  1. From the Start menu, select Run. The Run window appears.
  2. Type the following command for your application in the Open field and press ENTER:
    MYOB AE: x:\sol64\SR EPREBLD,
    MYOB AO: x:\MYOBAO\AOSQL\Tax\SR EPREBLD
    Where x:\ is the drive where System Release is installed. The System Services rebuild procedure window opens.

    EPREBLD must be in UPPERCASE.
  3. Click Rebuild. The Security Gateway window appears and requests a password.
  4. Type KYRZONES in the Password field. The rebuild routine starts. Once the rebuild is complete, System Services automatically launches.

    Do not cancel the Rebuild operation while it is in progress.
  5. From the File menu, select Exit. System Services closes.
  6. From the Start menu, select Run. The Run window appears.
  7. Type the following command for your application in the Open field and press ENTER:
    MYOB AE: x:\sol64\SR EPRESET
    MYOB AO: x:\MYOBAO\AOSQL\Tax\SR EPRESET
    Where x:\ is the drive where System Release is installed. The Reset Routine Warning box appears.

    EPRESET must be in UPPERCASE.
  8. Click Yes. The process commences.
  9. If the message "Do you wish to clear logged in status for <username> " appears, click Yes. This user is automatically logged out of System Services. The routine now updates the user database and resets the item count. Once complete, the system exits and returns you to the Windows Desktop.

    More than one user may be logged into System Services. Repeat step 10 for each user prompt.
  10. Log into System Release as the user SUPERVIS. Verify that operation is normal and all data including users, printer configurations and templates are present.
JavaScript errors detected

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

If this problem persists, please contact our support.