Error 7 occurred at Get LV Class Default Value.vi only in my executable for Print Report - LV 2010 SP1

[herningg]

I have a program written which uses the print report function. Everything works fine in the uncompiled code, my report prints just fine. I can compile my project all the way to a full installer. When I run the executable I get the error:

Error 7 occurred at Get LV Class Default Value.vi

With the following text:

Possible reason(s):

LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488:  Non-existent board.


Complete call chain:
     Get LV Class Default Value.vi
     NI_report.lvclass:New Report.vi
     print report.vi
     EMS V3.0 streamline.vi

LabVIEW attempted to load the class at this path:
H:\InMotion\EMS\builds\EMS_01\Emissions Analyzer\EMS.exe\1abvi3w\vi.lib\Utility\NIReport.llb\Standard Report\NI_Standard Report.lvclass

"EMS V3.0 streamline.vi" is my main vi, "print report.vi" is the subvi that creates and prints the report based on all the information sent to it. I get no warning when I compile this to an executable. I already tried repairing both LV SP1 and the report generator toolkit. No change after I compile to an exe.

Any help would be appreciated. Thanks.

Garrett Herning

[tst]

Did you try searching?

http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402

[herningg]

Ok, I tried that... and now I get an error when I try to compile to an executable... This is right at the end of the build and will not let me build an executable.

Error:

An error has occurred. Expand the Details section for more information.

Details:

Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:

Error 7 occurred at Invoke Node in AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller

Possible reason(s):

LabVIEW:  File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS X, and / on Linux. Verify that the path is correct using the command prompt or file explorer.
=========================
NI-488:  Non-existent board.

Method Name: Linker:Write Info To File

[tst]

No idea, but if I had to guess, I would guess that the path you're getting is too long. This is relatively easy to check if you change the destination of the build to a short path, such as c:\1.

In any case, you can also try searching for things like build "error 7" to see if other people ran into this.

[K1200LT_rider]

We're having the exact same problem.  In the error window, we noticed "1abvi3w" in the path of a Report VI that it was looking for (which can be seen in the original post above), but it should be the folder for the version of LabVIEW we are using.  Why is it using "1abvi3w" as a folder name???  It looks like someone that coded up the Builder was being funny about an alternative representation of the word "LabVIEW" which somehow gets through the build process and messes up the path.  That's a strange one.  Now we're figuring out a way to get around it (copy it to our support folder before building, or something like that).

[tst]

The leet version is the folder for the NI VIs which are saved inside your executable. The reason for that name was to avoid name collisions. It's not supposed to mess up the path, because it should work like that with any executable which includes VIs which originally in the LabVIEW folder.

[Travis_Ann_N]

Hi K1200LT rider,

Error 7 is a "file not found" error. Double check that you have all of the necessary folders and files in the Always Included section of the source files section as suggested in KnowledgeBbase article 3G5CDDV1. 

Regards,

Travis Ann

[K1200LT_rider]

That KnowledgeBase article fixed our problem. 

[hecmar.arreola]

---

@tst wrote:

Did you try searching?

http://digital.ni.com/public.nsf/allkb/8A0E6274D9BD7B1986256F62006AD402

---

When I searched, the first thing that came up was your post. How does that make you feel?

Realize that these questions do get indexed by Google. Ironically, a lot of folks trying to find a solution by searching will see the post "Did you try searching?" as the first reply.

[RavensFan]

So that is good.  You searched, and you found a message and that took you to the link you needed.