We have a version of AccountEdge Pro that works on Catalina and Big Sur (and Apple M1 chips) without requiring a virtual machine. Learn More.

Please visit our COVID-19 Resources page for useful payroll and reference information. If you are teleworking, check out Working Remotely with AccountEdge.

  • Section: Troubleshooting
  • Last updated: June 18, 2019, 12:05 p.m.

Errors Opening AccountEdge (Windows OS)

This support article covers possible issues when attempting to open the AccountEdge application on Windows OS.

If you are having trouble opening AccountEdge on macOS, click here.

If you are having trouble logging into your company file, click here.

For errors received when attempting to install the software, click here.

For errors received while using the software, click here.

Microsoft Runtime Error Messages

If you receive a Runtime Error message when you click on the password box to log in to AccountEdge, most likely your system is set to a language other than English for non-Unicode programs. AccountEdge currently does not handle UNICODE (Universal Character Set) character codes. As a result, AccountEdge cannot handle input from keyboards that transmit UNICODE character codes such as Chinese or Japanese, multi-byte character codes.

Attempted usage of UNICODE, multi-byte character sets may result in AccountEdge quitting with Runtime Error.

You can resolve the issue by setting your system language for non-Unicode programs to English. You can do this in the Control Panel.

  1. Open the Control Panel
    • Windows 7: Click Start and then Control Panel
    • Windows 8 and 10: Press the Windows key on your keyboard and type "control panel"
  2. Click on Region and Language
  3. Click the Administrative tab
  4. Click "Change System Locale" and change it to one of the English locales

Also, Microsoft has a utility named AppLocale, available from http://www.microsoft.com/en-us/download/. This utility allows you to run applications without changing language of non-Unicode applications (system locale).

MFC140.DLL Error Message or Side-by-Side Configuration Error Message

During the installation, AccountEdge will install the Microsoft Visual C++ library.

If this installation fails or the Microsoft Visual C++ 2015 Redistributable is uninstalled, you will receive this error message when attempting to open AccountEdge:

This error can be resolve by manually installing the redistributable for Microsoft Visual C++ which is available from the Microsoft website.

PLEASE NOTE: If you are using AccountEdge Pro 2020 or earlier, you need the 32-bit version of the Microsoft Visual C++ redistributable (even if you have a 64-bit Operating System). The 32-bit version is labeled vc_redist.x86.exe.

If you are using AccountEdge Pro 2021 or newer, you will need the 64-bit version of Microsoft Visual C++ redistributable.

Earlier versions of AccountEdge (pre-2017) would display a Side-by-Side configuration error message. This error message indicates the same problem as the MFC140.DLL error. It can be resolved by installing the 32-bit version of earlier C++ Redistributable from the Microsoft site.

.NET Framework Error Message

AccountEdge 2017 (and newer) for Windows requires Microsoft's .NET Framework v4.5.2.

During the AccountEdge installation process, if the machine you are installing AccountEdge on does not have .NET Framework v4.5.2 already installed, AccountEdge will prompt you to install it.

After installing the .NET framework update you will be prompted to restart your machine. After the machine restarts you should automatically be prompted to continue installing AccountEdge Desktop.

If you uninstall .NET Framework v4.5.2 and attempt to open AccountEdge 2017 you will receive an error message and will not be able to get AccountEdge to open.

You can manually reinstall .NET Framework 4.5.2 to correct this error.

You can find the Web Installer on Microsoft's site.

You can also find the Offline Installer on Microsoft's site.

Earlier versions of AccountEdge (pre-2017) would also display a .NET Framework error if .NET framework was missing. You can get earlier versions of .NET framework from Microsoft's site.

Procedure Entry Point or Isdigit Entry Point

Some users have reported errors that are a result of not having the proper updates to their Operating System. The errors:

  • "The procedure entry point ucrtbase.terminate could not be located in the dynamic link library api-ms-win-crt-runtime-l1-1-0.dll"
  • "AccountEdge execute - entry point not found The procedure entry point Isdigit could not be located in the dynamic link library C:/AccountEdgePro2017/icuin51.dll"

You should be able to resolve these issues by installing all Microsoft Updates and then using the update below. Please Note: Windows 7 users - you need to have Service Pack 1 installed to be able to install this update.

Make sure you install the correct one for your Operating System: https://support.microsoft.com/en-us/kb/2999226

ATL100.DLL Error Message

If you receive an atl100.dll error after installing AccountEdge Pro for Windows, you can resolve the problem by

  1. Uninstalling AccountEdge Pro
  2. Download and reinstall AccountEdge Pro

For more information about the uninstall and reinstall process please see this article.

This is not a valid Win32 Application

This message is often caused by a corrupt executable file. For instance, you may get the error while launching your accounting program on Windows. You may also get it while launching the Upgrade Assistant on Windows. You will need to re-install your program to replace the corrupted executable file(s) myobp.exe or myobupg.exe

This article explains how to uninstall and reinstall your software.

Error Creating a New Company File

When creating a new company file, it's possible to receive an error due to the location the file is being saved to or the name of the company file.

Example Error Message: Error -255 in DMCreateMYOBDat

This issue can be resolved by either changing the name of the company file (shortening it) or by changing the location the file is being saved to.

As a general recommendation saving to the Desktop directly can resolve this error.

As a final note, this same sort of error can be caused because of the naming of the Hard Drive. If you have special characters in the hard drive name (i.e.: !@#$%) these should be removed.