Skip to main content
Skip table of contents

Error: "Licence Check Failed: Last Known Position is 9 Error 800f0034: Error read/write licensing TNF file"

This support note applies to:

  • AE Assets (AU)
Article ID: 30890

You may receive the error "Licence Check Failed: Last Known Position is 9 Error 800f0034: Error read/write licensing TNF file" when MYOB AE Assets is not pointing to the correct installation directory within the Windows Registry.

To correct this error, you'll need to know the installed location of System Release. For a step-by-step guide on finding this location, refer to Finding the SOL64 or Tax directory

Before you begin, we highly recommend taking a backup of the Windows Registry. Instructions can be found on the Microsoft support website. Other operating systems such as Citrix and Windows Server may have their own registry backup procedures. Please seek guidance from your IT professional as appropriate to your circumstances.

These steps make changes to your registry and can cause issues with your system if performed incorrectly. MYOB advises that someone proficient with the Windows Operating System makes the change. For more details regarding making changes to the registry, refer to Important information for making registry edits and file changes
To update your registry settings
  1. Right-click on the Start menu and select Run.
  2. In the Open field, type in Regedit then click OK.
  3. Within the Windows Registry, navigate to the following location:

    OS PlatformKey
    32-bitHKLM_LOCAL_MACHINE\SOFTWARE\Solution 6\Assets
    64-bitHKLM_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Solution 6\Assets
  4. Highlight the Assets folder on the left-hand pane, then double click on Sol64Path.
  5. In the Edit String window, change the Value to the correct System Release directory (For example, X:\SOL64 or X:\MYOBAE\AESQL\TAX)
  6. Click OK.

The registry is updated. You may now close out of the registry and run MYOB AE Assets again.

JavaScript errors detected

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

If this problem persists, please contact our support.