Skip to main content

HandiTax - External Exception E0434352 in HandiTax

Steps to fix External Exception E0434352 when you lodge a return using the Australian Taxation Office embeddable client.

The Australian Taxation Office (ATO) provides an embeddable client that is integrated into HandiTax. It allows you to lodge using the Standard Business Reporting (SBR) Practitioner Lodgment Service (PLS) systems.

The embeddable client uses the Microsoft .NET Framework, which provides a run-time environment called the common language runtime. Exception code E0434352 is the code the common language runtime uses to represent most exceptions, so it can be difficult to troubleshoot. The exception can be related to the application or to your environment, such as your computer network.

This error is often caused by invalid characters in form fields, such as a minus symbol (-), or by issues with the application's configuration. Follow these steps to resolve it.

External Exception E0434352


Check for a minus symbol in the tax return

If the error only occurs on one tax return, a minus symbol (-) within the tax form may be triggering it. You can find and remove it using these steps:

  1. Select your tax return.

  2. Click the Errors button (or the SBR Errors button in any year before 2017).

  3. Close the return.

  4. Click Reports, then click Report Navigator, then click SBR Payload Files.

  5. Find the reference code of the return with the error, for example SAGE0001.

    Report Navigator
  6. On the right-hand side, you can view the details in the payload. Find the minus symbol (-) in the details.

  7. Close Report Navigator, then return to the return.

  8. Go into the form or worksheet that contains the data and remove the minus symbol (-).

  9. Click the Errors button again to see if this has resolved your issue.

🤓Tip: Click View File and use the search function to find the minus symbol (-) in the payload. The minus symbol may appear as 0 (zero) in the tax return. Double-click the field containing 0 to see if it displays as a minus symbol.


Check for errors in Admin mode

If the previous steps do not fix the issue, you can check HandiTax for further errors by running it as an administrator.

Take note of any errors when you close and re-open HandiTax in Admin mode. Right-click the application and choose Run as Admin.


SBR components error

If you get the error message 'SBR Components could not load', and the error only applies to your computer, you will need to run the SBR_DependencyCheck.exe application in your HSoft\Apps folder.


Refresh the configuration file

You may receive an application path error. You can resolve it by refreshing the configuration file, which regenerates when you next log in to HandiTax.

Application Path
  1. Ensure all users close all HandiSoft applications.

  2. Open File Explorer and go to the HSoft\Apps folder, then locate the file called HT1*exe.config, where * denotes the year, for example, Ht18.exe.config. Delete this file.

  3. If you are using the SQL version of HandiSoft, the file is called HT1*SQL.exe.config, where * denotes the year, for example, Ht17SQL.exe.config. Delete this file.

  4. Log in to HandiTax. The file will regenerate.

  5. Lodge a return to test if the error is resolved.


Rename the SBR folder

If the error continues, you can rename the SBR folder and reinstall the application.

  1. Ensure all users close all HandiSoft applications.

  2. Open File Explorer and go to the HSoft\Apps folder, find the SBR folder, then right-click the folder and rename it to SBROLD.

  3. Download the latest version of the application, taking into account that there is a separate download for the SQL version.

  4. Reinstall the application and complete any updates from the website.

  5. Open the application and lodge the return to test if the error is resolved.

    SBR Components could not load

General troubleshooting tips

You can help avoid this error and others like it by following these tips:

  • Regularly update Access HandiSoft to the latest version to ensure compatibility and error fixes.

  • Maintain accurate and complete data entry to avoid validation errors.

  • Back up your data before making significant changes or updates.

Did this answer your question?