So frustrating! The libraries run in the debugging environment just fine. No errors and two minor warnings. I have to constantly tweak and upgrade these libraries because each has about 40 VIs and are rebuilt on average two times a week. The executables are used at a dozen places and I can't place the developer system on each computer, that is what the Builder and the Labview runtime engine is for.
About a month ago after doing very minor changes in one VI I rebuilt the library into an executable using the same build file and BANG, I get this linker error. After acknowledging Labview disappears (stealth crash). Well eventually I figured I had to copy the diagram of the VI I had changed (yes, complete with changes) to another blank VI. After deleting the old VI and renaming the new (it used to be blank) VI, I rebuilt it. Everything was fine.
Well I have tried to rebuild frequently after each change and save often several copies back a month but somehow this has been futile as the error is back in both libraries. In the two libraries I maintain there are as many as 20 VIs identical between the two libraries. I make a change in one VI in one of the libraries then use the library manager to copy it to the other library. This has worked hundreds of times over the last year and half. Well somehow the problem has come back in both libraries and I can't isolate the bad VI.
Obviously one (or maybe more!) of the VIs are put together wrong but Labview doesn't detect it. I don't use any fancy linking to anything other than DAQ and SERP drivers, everything else are simple VIs (just Labview code) with only the Labview supplied VIs talking to DLLs. I have tried my little cut and paste trick with the last few changed VIs but it didn't work. I tried to use Application Builder to build VIs seperately but that was useless. I tried elminating the lastest changed VIs from the library and rebuilding but to no avail. It fails approximately 1/4 to 1/3 into the build process bar indicator but the Builder doesn't say what file it is building so I can't relate it to any specific VI. Tried relating the bar position to a latest changed list and an alphabetical list but that was inconclusive.
This issue is currently being worked on by NI support but I want to try the resources of the developer community because this is such a rare problem with big implications (at least to me).
