DQMH Consortium Toolkits Discussions

cancel
Showing results for 
Search instead for 
Did you mean: 

Start module causing error 1003

Solved!
Go to solution

Very strange thing happening.  My application works flawlessly in development.  

Ran module validation, VI analyzer.....no issues.

 

Problem is when I build the exe, then it doesn't run!  

and of all things, it is the start module.    

I checked and it's just the plain start module

 

Not sure if related but normally it will tell you which VI.  In this error msg, it doesn't say any.  Just shows call chain.

I've built EXE using 2021 and 2025, both has the same error.

 

Any idea where to look next?

 

shuttlefan_0-1756443434332.png

shuttlefan_1-1756443697974.png

shuttlefan_2-1756444272756.png

 

 

 

0 Kudos
Message 1 of 4
(123 Views)
Solution
Accepted by topic author shuttlefan

Hey shuttle fan, we run into the same situation every now and then (actually, we are struggling with it in one of our projects right now).

 

Taken from here, error 1003 means: 

 

The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File»Open to open the VI and verify that you can run it. Refer to the KnowledgeBase at ni.com if you receive this error in one of the following situations: while using the VI Server to call a VI dynamically or while building an application.

 

Usually, the direct reason is that the Main.vi of the module is broken in the .exe.

 

Why the Main.vi is broken of course varies from case to case. In our current project, this symptom has to do with DLLs that are or aren't in the right places after building.




DSH Pragmatic Software Development Workshops (Fab, Steve, Brian and me)
Release Automation Tools for LabVIEW (CI/CD integration with LabVIEW)
HSE Discord Server (Discuss our free and commercial tools and services)
DQMH® (Developer Experience that makes you smile )


0 Kudos
Message 2 of 4
(105 Views)

@joerg.hampel wrote:

In our current project, this symptom has to do with DLLs that are or aren't in the right places after building.


I'm suspecting that's likely the same issue.  Rather it's missing some DLLs
I did notice that only one DLL was included.


https://forums.ni.com/t5/LabVIEW/Issue-with-Executable-and-NET-DLLs/td-p/4025355#:~:text=When%20LabV....

0 Kudos
Message 3 of 4
(83 Views)

Yes!  That was it.  

So I added all the DLLs that I can find into the project.  

Then in the build spec->source file section as always include.

 

shuttlefan_0-1756464980285.png

 

0 Kudos
Message 4 of 4
(75 Views)