Error 2208 and 4A348 occurring when running LabVIEW executable

[CJW1800]

Hi,

I am having some trouble with a built application, i have the following setup;

• LabVIEW 2017
• LabVIEW OOP
• Using malleable VIs

I can successfully run the application in the development environment and i can build the executable.

When i try and run the executable i get the attached message.

I have tried a few suggestions on the forum, but not made much progress in resolving this one.

Cheers

Chris

[snordinh]

Hi, 

Can you confirm that you actually have the LabVIEW full development system and that this is working? If you do, it could be that it has become corrupted and needs to be reinstalled. 

Alternatively, it could be that the build that you have got is corrupted in some way and you will need the source code to rebuild it. Do you have access to that source code?

Thanks, 

Sara

[CJW1800]

Hi Sara,

As i said in my original post, everything is running successfully in the development environment.

I am running the exe on the same machine that i am running the development environment. I have full access to the source code.

Cheers

Chris

[snordinh]

Hi Chris,

Thanks for getting back to me. Have you tried upgrading the .NET framework according to the instructions described in this article?

Best, 

Sara

[CJW1800]

Hi Sara,

Thanks again for the reply, i have checked my .NET versions and they were all up to date, see print screen.

I setup the application for debugging as well, but i get a broken arrow, so i can't get any further than opening the exe and browsing the block diagram. There are a number of VIs that have broken Run arrows.

Cheers

Chris

[WitekN]

Hi, 

I have the same problem. The executable runs correctly when run in the folder it was built to, but when I move the exec to another folder, it doesn't run (2208).
I get two error dialogs.

[dracokev]

Hi WitekN,

Can you try including everything in your build and deselecting everything in the "Additional Exclusions" settings in the build specifications?

Cheers,

Kevin

[Simplicity_Jon]

I was having the same issue (LV 2017 app that uses classes and malleable VIs)

When I built with debugging enabled and everything in "Additional Exclusions" unchecked, the EXE worked OK.

Jon

[CJW1800]

Hi Jon,

I should have put a post on here earlier.

We had the same result with the things you mentioned, but additionally had to include all project files under the Source Files section of the build properties.

Cheers

Chris

[mwatkins]

I just resolved this problem: Source code runs file in development environemnt, running the executable throws a bunch of class errors when loading then finally get a error dialog much like yours: errors 2308, 2208, A348. 

Resolution: Move the executable to a shallower path location (like where the installer would put it) then try running. It seems like the class files cannot load because the total path has exceeded some limit. Example:

App runs fine from "C:\blah\" but moved to "C:\blah\reallylongpathname\organized directory structure\test programs\A-Z\start here\" then get those errors. Solution? short the install directory and change names as necessary.