Actor Framework Executable Doesn't Run Root Actor

[KCC66]

Hello All,

I built a project based on the Actor Framework template.  The code runs well in the development environment.

I built an executable file using the application builder and it built successfully.

The issue is when I run the executable, the launcher runs and then I get a popup asking to save 3 vi's that have been changed, including the root actor core vi.

The root actor does not run at all.

Any ideas?

I also posted this in the LabVIEW forum-

https://forums.ni.com/t5/LabVIEW/Actor-Framework-Executable/td-p/4381284

[KCC66]

Still looking for help on this issue.  Any ideas?

[justACS]

What are the other two VIs?

Do you link to any of them dynamically?

Does your launcher report errors?  What error do you get?

[IlluminatedG]

In Windows you can look at folder %temp% for a <Your EXE>_<version>_<user>_cur.txt log for errors or a brokenvilog text file and see what it lists as being broken.

[Darren]

Do you have the 'Open Actor Core front panel' option set to TRUE on any of your Launch Actor VIs? That option doesn't work in a built EXE, and I've seen cases where it silently fails and the actor doesn't launch as a result.

[KCC66]

I can get the other to files on Monday.

I am not linking any vi's dynamically except where the launcher calls the root actor main vi.

It is not generating any error message pop-ups.

[KCC66]

I'll look for this txt log on Monday.

[KCC66]

I did check the 'Open Actor Core front panel' where the launcher calls the root actor.  It is set to false.

[KCC66]

I created a new project using the actor framework template, and created an exe from the template project as is.  This exe works fine.

So it must be something failing in the code that I added to the template, although the code runs fine in the dev environment.

I am going to schedule some time with NI support to look at the code more closely.

Thank you much for the ideas, and any other suggestions are certainly appreciated.

[KCC66]

I should add that this project also uses the DSC module, and I have both dev and the runtime licenses for DSC on this pc.

I am using the same pc for development and to run the exe.