PROBLEM: Receiving error: "AVR Runtime module not found. Program terminating"

The information in this article applies to:

ASNA Visual RPG, All Versions
Windows
Deploy

SYMPTOMS:

Receiving error: "AVR Runtime module not found. Program terminating".

CAUSE:

One of the supporting runtime DLLs can't be found.

RESOLUTION:

NOTE: Make sure there is enough Registry quota and you have Administrative Privileges prior to registering any dlls or ocx files. Please coordinate with your Network Administrator or Microsoft while working with the Registry and Windows.

When an AVR 3x or 4.x executable is loaded, the supporting runtime DLL (AVRRT3x.dll or AVRRT4x.dll) must be loaded. Here are some steps to determining cause when you get this error:

TIP: ASNA's REGOLE doesn't return a message stating it passed or failed.

AVRRT3x.dll or AVRRT4x.dll not installed on client PC. Resolution:
- Install it using ASNA DEPLOYMENT. Recommended location is "<CommonFilesDir>/ASNA Shared."
AVRRT3x.dll or AVRRT4x.dll is installed. Resolution:
- Register it with REGOLE.exe or Microsoft's REGSVR32.exe. If you are unsuccessful in registering, then supporting files may not be installed. These include ADBAPI.dll, ADBAPX.ocx. MFC42.dll, MSVCRT.dll, MSVCIRT.dll. You may want to use Dependency Walker to troubleshoot problems. You can also review what files are required for AVR 4.x Applications using this document (NOTE: You will need to have AVR 4.x IDE installed to review this document).
- You can also reinstall Deployment which is available on our website or on the ASNA CD. Please make sure you install the correct version of Deployment. The version of the AVR Application has to be the same or lower as the version of AVR you are developing in.
AVRRT3x.dll or AVRRT4x.dll is installed and registered. Resolution:
- Be certain there is only one copy of ADBAPI.dll on the client system. If a 4.2 version of ADBAPI.dll is loaded in a Windows search path for example, Windows may attempt to load that old ADBAPI.dll as a supporting component for the 3.0, 3.1, 3.5, 4.0, or 4.1 runtime. The cause of this is that the client PC may have a 4.2 ADBAPI.dll loaded in Windows\System and the correct 4.6, 4.7, 5.0, or 7.x version of ADBAPI.dll loaded in "<CommonFilesDir>/ASNA Shared." The Windows file search mechanism may find the Windows\System\ADBAPI.dll first. Because this is an incorrect and incompatible version, AVRRT3x.dll or AVRRT4x.dll cannot be loaded.

MORE INFORMATION:

NOTE: AVR Release 3.0, 3.1, 3.5, 4.0, and 4.1 runtimes are not compatible with each other, in addition to their filename will be different (e.g. avrrt30.dll, avrrt31.dll, avrrt35.dll, avrrt40.dll, avrrt41.dll).

When an AVR 3x or AVR 4x executable is loaded, the supporting runtime DLL, AVRRT3x.dll or AVRRT4x.dll (The version of Runtime will be different depending on the release and version of AVR the executable was developed on), must be loaded.

The error: "AVR Runtime module not found. Program terminating" can be a result of: the EXE being at a different version than AVR Runtime.

Below are Instructions to confirm the version of AVR Runtime and an AVR EXE.

Version of AVR used to create an AVR EXE:

In Windows Explorer, go to the folder that the EXE exists;
Right Click on your EXE;
Select Properties;
Select the Version Tab;
In the Item Name Listbox, select AVR Version:

Version of AVR Runtime Installed:

In Windows Explorer, go to the "c:\program files\common files\asna shared" folder;
Right Click on AVRRT3x.DLL or AVRRT4x.DLL (where x is your version);
Select Properties;
Select the Version Tab;
In the Item Name Listbox, select Product Version: