Skip to main content

System unable to execute the specified program

  • July 15, 2014
  • 2 replies
  • 0 views
D

I am getting this error on one particular XP SP2 machine, but everything runs fine on other XP and Win 7 machines. I have never some across this before, is it complaining about wrun32 or the .acu program, and how do I get around the problem? For what its worth we are using 8.1.3 runrime

    2 replies

    Stephen Hjerpe
    • Stephen Hjerpe
    • Participating Frequently
    • July 16, 2014

    I am getting this error on one particular XP SP2 machine, but everything runs fine on other XP and Win 7 machines. I have never some across this before, is it complaining about wrun32 or the .acu program, and how do I get around the problem? For what its worth we are using 8.1.3 runrime

    I found several articles, here are 2.

    en.kioskea.net/.../1570-windows-unable-to-run-executable-files-exe

    or Two options. One is to run a system restore to a date right before the

    crash. Start | All Programs | Accessories | System Tools | System

    Restore.

    The second is to run the .exe file association fix on Doug Knox's site:

    http://www.dougknox.com/. Go to Win XP Fixes section, then File

    Association Fixes, Exe File Association Fix.

    D

    I am getting this error on one particular XP SP2 machine, but everything runs fine on other XP and Win 7 machines. I have never some across this before, is it complaining about wrun32 or the .acu program, and how do I get around the problem? For what its worth we are using 8.1.3 runrime

    Thanks very much, but I also lodged this query with Support, who gave me the following answer:-

    When trying to run an ACUCOBOL-GT application with Version 8 or even do a "wrun32 -v" version check "The system cannot execute the specified program" error occurs.

    The problem occurs when the ACUCOBOL-GT Runtime was not installed on the Windows machine where it is attempting to execute. It could be that the bin directory was copied from another Windows machine (ISVs often deploy their applications this way), or in a network environment where client PCs map to the ACUCOBOL-GT bin directory on a server.

    The underlying cause is that Version 8 is built with Visual Studio 2005 which not only binds the Runtime to new Microsoft dlls (MFC80 vs MFC71, etc) but to specific versions of those dlls. When the ACUCOBOL-GT Runtime Version 8 is installed on a given Windows machine the installer detects whether those dlls are present and installs those that are missing.

    When the bin directory is copied to another Windows machine or a client PC is mapped to the bin directory on a server, the necessary Microsoft dlls may not be present and the error is seen.

    Resolution:

    The solution is to download the attached MSdlls.zip and extract it to the bin directory of the ACUCOBOL-GT installation making sure to check "Use folder names".

    There should then be two folders in that bin directory, Microsoft.VC80.CRT and Microsoft.VC80.MFC.

    The Runtime will then have all of the dependent dlls available in the bin directory and will execute without error.

    I am waiting for our consultant to revisit the client and try the support recommendation

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement