Updating files links hangs during deployment

[SharkAttack]

I am trying to deploy Test Stand from a Workspace file and when it gets to the phase under Build Status; "Updating File Links" it seems to hang, but I don't get any error messages. I've left it running anywhere from an hour up to several hours.

Previously, I have successfully used the deployment utility to create an installer with just the Test Stand Engine (took 20minutes), but when I installed it to the target machine there was a missing "cviauto.dll" that wouldn't let me login.

Any ideas, confirmed solutions...etc,

[Matt M.]

Hi SharkAttack,

Are you using a subsequence call in your sequence? If so, is the subsequence in the same file?

We have noticed that the deployment utility will hang at the Updating File Links step when you are calling a subsequence from the same file, except instead of selecting the "Use Current File" option, you browse to the file again. This creates a circular reference and will cause the deployment editor to hang.

Perhaps this is your problem?

Matt M.

NI

[SharkAttack]

Hi Matt,

Yes I am using many subsequence calls.

I had noticed that the processor was pegged at 100% and got the feeling there was a circular reference issue. I was able to isolate the problem to the batchmodel.seq file, but not to the step within it. I removed the batchmodel from the workspace and the build finished. There are subsequences that call external sequences, but the calls that should be marked "use current file" seem to all be checked.

Is there an "easy" way to find out if "use current file" isn't checked when it should be?

...

[Matt M.]

Hi SharkAttack,

You could search for batchmodel.seq in your file. This would show you when you are calling the file directly, not using the current file option.

When I searched through the batchmodel.seq file that ships with TestStand, it doesn't appear to have any circular references. How are you using the batchmodel.seq file? Are you using it as your process model or calling it directly? Have you modified this file at all?

Matt M
NI

[SharkAttack]

This is a modified batch model that is in the user directory.

I ran the differ tool to compare it to the original batchmodel.seq file in the NI model directory. I couldn't find the circular reference.... I could try making a copy of it and deleting steps until I found on that causes the system to hang.

[Matt M.]

Hi SharkAttack,

Instead of deleting steps, you could simply replace them with steps from the batch model we ship until the problem occurs.

Have you tried running your program and building the distribution kit using the batch model we ship instead of your custom model?

If the problem disappears then you know the problem is in your batch model. If the same problem persists with our batch model, then it is elsewhere in your sequence.

Regards,

Matt M.
NI

[SharkAttack]

I did test the default batchmodel and it "builds" fine. I opened my Workspace and used the "insert Code Modules" function as a check for circular references. It worked pretty well. As I removed sequences instead of trying the build again and waiting I just checked that the batchmodel wasn't in the list of files presented by the "insert Code Modules" tool under itself. I eventually found a sequence call in the ProcessModelPostResultListEntry that did not have "use current file" checked.

I made the changes and the batchmodel no longer showed up under itself and I was able to build the deployment files successfully. I still have to verify that it installs and runs without errors.

thanks for your help!