TestStand Deployment Error Code 1055 when using LabVIEW Storage VIs

[Simon_Holman]

After a couple of days of playing with the TestStand Deployment. I final tracked down the VI that was causing this Error.

It was using thethe LabVIEW Storage VIs to save data to a TDM file.

My work around at the moment is to use a Wrapper VI and call this VI by reference.

That way the TestStand Deployment can't detect the Storage VIs.

I'm using LabVIEW 8.6.1 and TestStand 4.1.1 does anyone know if this issue has been address in TestStand 4.2?

Looks like the upgrade might be worth it.

[Manooch_H]

Simon,

Could you post an example of the VI you were attempting to deploy so that I may reproduce this issue? I can also test it in TestStand 4.2 for you to let you know if the problem has been addressed.

[Simon_Holman]

Here you go.

This is a simple VI that creates a TDM file and Closes it, using the Storage VIs.

When I try to build it I get "Internal error code 1055 Processing VIs..."

My guess is that the Depolyment engine is trying to find all the SubVIs for these functions,

however the way these Express VIs are setup, You cannot see the SubVIs.

Thanks

[Suse]

Hi Simon,

I tested your sequence file in TestStand 4.2 and I didn't get any error! Which version of TestStand do you have? Can you post a screenshot of the complete internal error pop up?

Usually internal errors can be eliminated with the Clean Reinstall Procedure.doc, where you will remove all NI software and all references to NI software from your computer to start over with a fresh installation!

I hope these informations help you!

Best regards

Suse

[Manooch_H]

Simon,

Please do not perform the Clean Reinstall Procedure. I was able to replicate the error with TestStand 4.1.1 and LabVIEW 8.6.1.

I was also able to build successfully with TestStand 4.2 and LabVIEW 8.6.1 however during the build process LabVIEW attempted to search for a file that did not seem to be necessary for the deployment to build successfully. I'm currently investigating this to find out what the file is and why LabVIEW is looking for it.

I will give you an update as soon as I find out more.

Again, please do spend unneccesary time uninstalling/reinstalling TestStand.

[Manooch_H · Accepted solution]

Simon,

After investigating the issue further I found that we had already come across this bug. It has been corrected in TestStand 4.2 and LabVIEW 2009. I tested your files out with TestStand 4.2 and LabVIEW 2009 and everything built successfully without any hitches along the way.