LabVIEW 2016 Run time error 127

[CarstenPXI]

Have built an executable in LabVIEW 2016 64 bit on Windows 10 targeting WIndows 7 service pack 1 and up. DAQ is not used, and a few vis from the Sound and Vibration toolkit are used.

After installing on a Windows 7 machine I get the following errors when opening the program.

"The Procedure entry point nier_setApplicationCallback2 could not belocated in the dynamic link library nierInterface.dll"

 followed by

"System error 127 while loading the LabVIEW Run-Time Engine ....(path to 2016 run time engine)  .... <my program name> requires a version 2016 (or compatabile) LabVIEW Run-Time Engine.

After that the program crashes.

The program installs and runs fine on the Windows 10 machine.

Have verified that my target machine has the 2016 run time Engine.   Also verified that my program is installed in the Program folder (64bit). Get the same error on two different Windows 7 machines.

Have searched Google and NI support forums and found nothing.

Carsten

[CarstenPXI]

Have just built a mini vi which adds two numbers, and created an installer, put on Win 7, and get the same errors. So this should eliminate any issues with complex code or weird libraries.

Verified that it install OK on Win 10.

[udka]

Which version of Runtime Engine you installed and Win7 32 bit or 64 bit?: http://www.ni.com/download/labview-run-time-engine-2016/6067/en/ (If target is 64 bit)

-http://www.ni.com/download/labview-run-time-engine-2016/6066/en/ (If target is 32 bit)
And check with this which version of Runtime engine installed: How to Determine the Installed Versions of the LabVIEW Run-Time Engine: http://digital.ni.com/public.nsf/allkb/A10E33BD994EC3CF86257B8700528C96?OpenDocument

[CarstenPXI]

Thank you for your reply.  The target PC is 64 bit Windows, and the Run time engine was created by 64 LabVIEW Installer.  I have verified via Max that the Runtime enginer is LabVIEW 2016 64 bits...thanks NI for now adding this to the Max software list.  Have also checked that the 2016 LabVIEW runtime engine resides the Programs (64 bit) folder. 

So we will continue the wild goose chase!

Thanks again,

Carsten

[udka]

Possible to post exact error screenshot?
- Are there any other runtime engines presently installed or previously installed before the current installation?
- could you try with 32 bit runtime engine also once?

[natasftw]

He said he's using Windows 10.

You're also looking at bitness.  He'd run into a message saying the Runtime didn't exist if he had the wrong runtime.  He wouldn't get an error from the runtime if it was the incorrect runtime.

But, looking at Windows 7 is something worthwhile to consider.  If you run the executable on a Windows 7 machine, do you see the same error or does it work?  That helps narrow down if the executable is having issues running due to Windows 10 or something else.

You made a simple add executable.  Is that all that happens in the source?  It'd be helpful to attach that project as well as the executable you build to see if other PCs have the same issue.

Have you successfully built executables on this PC before?  If so, do those still work if you build them fresh?  If not, do you have another PC you can try just to see if it is PC dependent?

[CarstenPXI]

This is the first time I have built Executables and Installers on this PC (Win 10 Bootcamp on MacBook).

They install fine on this machine, but not others.

Have tried running executable on Win 7, same error messages.

Attached is the executable and the project file.

Very advanced program, add two numbers in an event structure;-)

Carsten

[CarstenPXI]

Attached screen shots of Max Software List, Explorer view in Program Files, and the two Error Messages. Looks like only the first error message comes in this post.

[CarstenPXI]

And here is the second error message.

Carsten

[NataliaS]

Hey, 

The nierinterface.dll gets installed with the run time engine and LabVIEW development environment.
Since you are building the installer, this dll should be included with run time engine. It is recommended that you leave the option for run time engine to default (in My Installer Properties window>>Additional Installers>> enable Automatically select recommened installer), it will only install the required dlls.

Kind Regards,

-Natalia