Error 7 goopsup - source does not exist

[PPG]

The test sequence works fine on the development machine, but I get the error, mentioned above, when I try to assemble the test sequence VIs for run time distribution.

[Shannon R]

PPG,

I have a couple questions for you. Are you using the GOOP Toolkit in your LabVIEW VIs? Does this error occur everytime you run Assemble Test VIs or only with certain sequences?

Let me know.

Thanks!
Shannon R.
Applications Engineering
National Instruments

[PPG]

Hi Shannon,

I do not use any GOOP Toolkit, that is why I am surprized by this error. The error occurs only with a sertain sequence file, that consists of a couple dozens of sequences. Some of the sequences' VIs use the VI server to invoke others VIs.

I hope this will clarify the issue. And thanks for your reply.

Peter

[Shannon R]

Peter,

I have never heard of this error when using the Assemble Test VIs tool. If you could narrow it down to a particular VI or type of VIs within your sequence, that would help us determine what is causing the problem. After you have the VI, you can create an email support request at Request Support and send the sequence and the VIs. We will try and run the tool and see if we can replicate the problem.

Regards,
Shannon R.
Applications Engineer
National Instruments

[PPG]

Shannon,

It was pretty hard to locate the vi that had caused the problem because the error message did not contain any information that could help, such as step or vi name. When I narrowed the problem to a particular test sequence I saved it into a separate sequence file by copy/paste the sequence. Then I opened the VI from the new sequence file by Edit code and saved the vi because it showed that it was changed.
I tried to assemble the VI of the new sequence and I did not get any errors: the problem disappeared. Now I can assemble the VIs of the original test sequence.
I think the problem was caused by a bad subVI path that was fixed when the VI was opened, then saved.
To summarize, I would say the following: the major problem was to understa
nd and locate the problem.
An appropriate error message with the step and vi names could help to fix it sooner.

Peter