after updating to 2012 f3 patch all built programs crash

[mattvx]

I updated to the f3 patch yesterday and now all executables that I've built in 2012 crash without even opening. No error messages at all. Anyone else experiencing this issue on f3 and know of a solution? I've tried installing the 2012f3 runtime but it thinks it's already installed. Thanks.

[User002]

I am able to build applications using 2012 with f3 patch.

Have you tried to build a test exe with a really simple/trivial VI?

If it still crashes, you might have something wrong with your environment?

Br,

/Roger

[mattvx]

I doubt it's anything to do with the builds themselves. All these exes worked before I patched to f3. Also I checked and I'm missing those files that the f2 patch supposedly removes. 

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\tdtable.tdr

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\English\lvapps.rsc

But I think I went straight from f1 to f3 so I'm not sure how they got removed. Is it possible to just copy those files from another computer? Thanks.

[JÞB]

Let me see if i'm tracking.

You built some executables in LabVIEW 2012 f1.

They do not execute with LabVIEW 2012f3 Run Time Engine

Correct?

(That might be expected behavior-  NI?)

Re-reading.  You are missing

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\tdtable.tdr

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\English\lvapps.rsc

The f3 patch writes them if they are missing!  did you re-boot?

[billko]

---

@mattvx wrote:

I doubt it's anything to do with the builds themselves. All these exes worked before I patched to f3. Also I checked and I'm missing those files that the f2 patch supposedly removes. 

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\tdtable.tdr

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\English\lvapps.rsc

But I think I went straight from f1 to f3 so I'm not sure how they got removed. Is it possible to just copy those files from another computer? Thanks.

---

So... maybe do a repair on LabVIEW and then reinstall the patch?

[billko]

---

@JÞB wrote:

Let me see if i'm tracking.

You built some executables in LabVIEW 2012 f1.

They do not execute with LabVIEW 2012f3 Run Time Engine

Correct?

(That might be expected behavior-  NI?)

---

I didn't think of this!  If that is correct, I guess he'd have to re-build the executables?

[mattvx]

Looks like after repairing the installation everything is working 🙂 The files are back. And Labview - About reports that it's on f3

[Jeff-P]

Hello all,

Hopefully I can clarify this behavior a little bit - 

---

@JÞB wrote:

You built some executables in LabVIEW 2012 f1.

They do not execute with LabVIEW 2012f3 Run Time Engine

Correct?

(That might be expected behavior-  NI?)

---

The runtime engine was broken by the missing files which is why your executables were not able to launch. To clarify how all the LabVIEW Runtime Engines work - each version of the runtime will execute executables built in that version of LabVIEW. For example the LabVIEW 2011 SP1 runtime can still run LabVIEW 2011, and the LabVIEW 2012 f3 runtime can still run LabVIEW 2012 f1 and LabVIEW 2012. However the runtime engine will not run code from other versions of LabVIEW, so the LabVIEW 2012 f3 RTE will not run LabVIEW 2011. 

This is why you don't to have multiple runtimes within the same version of LabVIEW (you don't need a LabVIEW 2012 f3 RTE and a f2 RTE for example).

---

@mattvx wrote:

I doubt it's anything to do with the builds themselves. All these exes worked before I patched to f3. Also I checked and I'm missing those files that the f2 patch supposedly removes. 

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\tdtable.tdr

C:\Program Files (x86)\National Instruments\Shared\LabVIEW Run-Time\2012\English\lvapps.rsc

But I think I went straight from f1 to f3 so I'm not sure how they got removed. Is it possible to just copy those files from another computer? Thanks.

---

This behavior can happen if the LabVIEW Run Time Engine is in use while the f1 patch is installed and then again when a later patch is installed. The reason this was a problem with the f2 patch was that LabVIEW 2012 ships with the  "Variable Web Service" which uses the RTE even if all other applications have been closed. Thus in certain circumstances the f2 patch would remove those two files. We removed the f2 patch from circulation and issued the f3 patch which will restore the missing files (and adds some other fixes). The f3 patch also gets around the variable web service so that the RTE is not in use while the patch is being installed.

You went directly from the f1 patch to the f3 patch, which is entirely fine. 

However, you can get into this state if you install a patch while the RTE is in use and then install a second patch to the same version of LabVIEW later while the RTE is again in use. The RTE must be in use during both installations for the files to be removed. This is not new to LabVIEW 2012 and can occur with any version of LabVIEW. Examples of things that use the RTE are the Example Finder, built executables, or certain web services (no web services ship with LabVIEW that are dependent on the RTE)

To prevent this - follow the installer instructions and close down programs that are using the RTE during the patch install process (close down all NI software and any built executables that are running).

If you do experience this - a repair installation of LabVIEW or an installation of a later patch will repopulate the missing files.

Hopefully that clears this up a little bit!

Regards,

[JÞB]

MEGA Kudos!  Thank you Jeff. (The other Jeff, not me)

[SkeeterMcjenkins]

Also haveing the same problem I am a student at the University of South Alabama our it department informed all the student to do a system restore to a point before the F2 and F3 patch should reverse the problem with going through minimal effort, although this has helped most students but not all.