After installing an application that was created using the Application Builder

[Rockwell]

After installing an application that I created using the Application Builder I get this error if I try to run " ANY " LabVIEW App's that I have built. "Executable Version 7.1.1 doesn't match Resource File 7.1. Check your configuration."

The way that I tried to fix this is to reload LabVIEW 7.1 and DAQmx 8.0. I am using two NI-6528 switch cards.

After I reload LabVIEW and DAQmx I can run my applications but as soon as I install one on this development machine the error begins again.

The executable that I built works fine on the development machine and any other machine that I try it on but it appears that the Run-Time engine 7.1 becomes corrupt after I run setup.exe for the newly created application.

I have built numerous Installers, setup.exe's in the past without this error. Just this latest one caused this problem to start.

I can NOT upgrade to 7.1.1. I am doing work for many different sections of this factory and I can not force them to upgrade. I've asked. Others supply code for the same machines using LabVIEW 7.1.

I am stuck creating executables and manualing moving the correct files to the target machines.

What can be done?

[dan_u]

There's a knowledge base on ni.com...
See here.

[Rockwell]

How can this be repaired without updating to LabView7.1.1. I have been using 7.1 for a year without this problem.

[dan_u]

You don't need to upgrade to 7.1.1. The point is that each time you install an application built in LV 7.1 on a machine with LabVIEW 7.1.1 or newer installed you'll face this problem. Just repair the run-time engine on the machine and it will work.
If you upgrade to 7.1.1 on your end you won't face this problem anymore.
A workaround for this could be to leave away the run-time engine in your installer if you're going to install it on a machine with LV 7.1 or newer installed.

[Rockwell]

I did not understand this statement you made. "A workaround for this could be to leave away the run-time engine in your installer if you're going to install it on a machine with LV 7.1 or newer installed."

Note: I am building 7.1 applications and installing them on machines that have LabView 7.1.

LabVIEW 7.1.1 is not in being used here.

[dan_u]

From my experience (and this matches the knowledge base article) the problem you described only occurs when installing an application built in 7.1 on a machine with LabVIEW run-time 7.1.1. This is the case if LV 7.1.1 or newer is installed on the target machine or an application written in 7.1.1 was installed on that machine before.
I never experienced this problem on a clean machine or on a machine with 7.1 on it.
You can check in the "control panel > Add or remove programs > National Instruments Software" what is installed on the machine.

Message Edited by dan_u on 03-26-2007 03:30 PM

[Rockwell]

As another note.

The 7.1 Run Time engine is NOT installed on the development machine. I believe that when DAQmx 8.0 was loaded, it was replaced by the 7.1.1 Run Time Engine.

[dan_u]

In this case I haven't got a clue either. Sorry.
But still, did you try to follow the instructions in the KB article on one of the machines where the problem occurs?

[Rockwell]

No. The KB article was talking about a machine with 7.1.1 installed. I have LabVIEW 7.1 installed.

The machine that I am having trouble with is my development machine. LabVIEW 7.1, DAQmx 8.0.

If I build the executable all is fine. I can still run old executables including the one I just built.

If I create the installer all is fine. I can still run old executables including the one I just built.

When I install the app on my development machine the corruption occurs. I can " NOT " run old executables including the one I just built. The subject error pops up.

I have not moved any executables to the other machines yet. I don't want to corrupt others.

[dan_u]

No, the KB article talks about an application built on a machine with LV 7.1 and trying to run it on a machine with LV run-time 7.1.1. I think this is your scenario.