Execution entry point not visible in deployment system

[AmitKaria2k]

I'm using TestStand 2010 deployment system with LabVIEW 2010 SP1 run-time engine.

In development system I have customized to things:

1. Configuration entry point to include call to a LabVIEW VI

2. Execution entry point to show only customized entry point

In deployment system when I open Operator interface and load the sequence file both these entry points are not visible. Also, the execution entry point button in OI at bottom is not seen. To overcome this I have to click on "Configure --> Station Options" and click either Ok or Cancel button. Immediately both the entry points and execution entry point button are seen on OI. I tried to deploy a simple sequence file with original process model (provided by NI) & even this shows same behavior (70% of time).

FYI:

Just as insight to my customized process model. I'm loading all the VI's and process model dynamically. In sequence file load step I have a LabVIEW VI that gets the root folder of installation and adds it to search directory programmatically in TestStand. May be this is the root cause of issue. But even after making the file path for Process model as absolute things did not work for me.

Any ideas why I'm seeing this issue??

- Amit Karia

[snowpunter]

If the entry points aren't displayed it's because the client sequence file can't find the process model.

[AmitKaria2k]

In deployment system the OI is able to load the Process model properly. Only entry points show flaky behavior.

Solution:

1. Move the "Sequence File Load callback" to process model.

2. Set the process model to use absolute path instead of Relative path.

Probable cause of error:

If the client file uses "Relative Path" for loading all files (Process model as well as VI's) and this relative path is programmatically calculated based on "Search Directories" which is populated programmatically using a LabVIEW in "Sequence File Load Callback" in client file then the entry points in OI show flaky behavior.

When the user opens client file in OI the process model is the 1st item that will be called by engine. Now if the process model is not in search directory (initially) TestStand should ideally throw error saying that file is not found. But surprisingly I've no idea that even with no process model file found the client executes the Sequence File Load callback properly and load add search path. Hence after some time the process model path is shown in taskbar but the customized entry points are missing.

Question: Why this is prevalent only in Deployment system & not in Development System?? Any ideas guys..

- Amit Karia