Program not responding for 15 s when ApplicationManager.GetEngine is called

[AndrazS]

Labivew 2019, TestStand 2019, Labview run-time engine selected.

I have Labview TestStand user interface tested on developement PC runned smoothly. After building TestStand deployment and created UI as .exe, the ApplicationManager.GetEngine called in user interface last 20s and program goes into "not responding" state. After 20s the program runs normally.

Any idea what, why and how to fix this very anoying problem?

[billko]

I guess that's how long it takes to spin up the LabVIEW runtime...

[GovBob]

I would think that the issue is related to load time of the TestStand engine. I guess you could compare with one of the TestStand example UI's. 

[JÞB]

---

@AndrazS wrote:

Labivew 2019, TestStand 2019, Labview run-time engine selected.

I have Labview TestStand user interface tested on developement PC runned smoothly. After building TestStand deployment and created UI as .exe, the ApplicationManager.GetEngine called in user interface last 20s and program goes into "not responding" state. After 20s the program runs normally.

Any idea what, why and how to fix this very anoying problem?

---

In this case, I cannot guess very well.

I would like to look at the hierarchy view after the 20sec delay.  What proxy callers are instantiated?  Do you mix calls through lvprojs and naked vi calls,?  Context is everything! How many contexts are used?