01-13-2009 02:48 PM
Collin,
It was a reasonably recent build spec (first created yesterday) but I did delete it and rebuild.
Unfortunately, I did the "always include" suggestion with the new build so I cannot say which action helped or if both were needed. Either way it works now...
Thanks!
01-30-2009 07:23 AM
I'm having this same problem. This project does not target a RT system but I have recently been working on projects that do.
The build worked fine before but now at launching missing Not Found Dialog.vi, Details Display Dialog.vi & Set String Value.vi all from the general Error.llb.
This error has repeated in more than one LV project. The only thing that worked for me was to include these Error.llb vis in the "Always Included" source files when building the app.
This is clearly a bug!!
02-04-2009 02:38 PM
I am having the same problems. My project is very simple and does not call any VIs dynamically (at least not directly from my code). The following VIs are missing from the executable:
Set String Value.vi in VI General Error Handler CORE.vi
Details Display Dialog.vi in VI General Error Handler CORE.vi
Not Found Dialog.vi in VI General Error Handler CORE.vi.
After reading this post and playing around with it for a moment, I have found a solution:
- Delete anything in your build directory that is not put there by building your project.
- Find General Error Handler CORE.vi under Dependencies in your project and open it up.
- If it does not show any changes (from VI recompile), then force a change (by either changing a cosmetic on the front panel or moving a block diagram object forth and back with the arrow keys).
- Save the VI.
- Rebuild your project. The problem should be solved.
No need to delete your current build specification, it seems to be only that the General Error Handler CORE.vi needs a recompile. I too have been compiling for embedded targets recently (cRIO), and have not seen this error prior to that. I suppose that LabVIEW has silently recompiled the error handler VIs to trim out the unnecessary parts for embedded projects. Unfortunately, this has left them unsuitable for Windows projects. Oops.
Hope this helps!
-Richard
Certified LabVIEW Developer
04-30-2009 04:14 AM
Maybe it's a different problem, but the topic fits quite well: after installing LV 8.6.1 / WinXP I cannot run an executable because it misses a lot of VIs. Not only from error.llb, but e.g. XDataNode.xnode or files from picture.llb. Neither did Ctrl-Shift-Run to force a recompile help nor deleting and adding the build again. Adding the missing files as "always include" leads to other files missing, that were not missing before. The application runs on the build system. The Top-Level-VI runs fine without warnings or errors in LabView.
Enhanced DSC support is enabled and necessary.
05-11-2009 05:00 PM
Saving General Error Handler CORE. vi fixed it.
Thanks!!!
06-11-2009 11:22 AM
Hi.
Just wanted to agree that the forced compile of the general error handler is the solution to this problem.
I had exactly the same missing files after building an executable for the PC in a project that includes a cRIO.
CTRL-SHIFT-RUN on the top level VI did not fix the issue. CTRL-SHIFT-RUN on the General Error Handler CORE.vi did fix the problem.
Thanks to the smart people who figured this out.
Jeff.
10-09-2009 11:59 PM
01-05-2010 07:55 PM
For me my labview is missing the files below
-Not Found Dialog.vi
-Details Display Dialog.vi
-Set String Value.vi
But I guess i found the solution...
Copy C:\Program Files\National Instruments\LabVIEW 8.6\vi.lib\Utility\error.llb from a working labview and replace this file to the not working labview.
For your case i guess it may work in this way too.
11-07-2024 01:36 PM
I know that this thread has some age to it but I recently ran into a similar issue with a builder settings and a project that has worked fine for years. However I upgraded toolkits and LV to newer versions.
What worked for me was clearing my cache and re-compiling everything. Addressing any errors that may have been reported.