Whenever I do a Teststand deployment and I select to password protect my VI's, I get a very freindly and descriptive: Error 1035. I assume (because I am a LV user and have been trained to decode cryptic error messages) that this means that one of my VI's cannot be password protected. Any help is appreaciated.
Error 1035 occurred at Invoke Node in TestStand - Lock Heirarchy.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi.ProxyCaller
Possible reason(s):
LabVIEW: Operation is invalid for this type of VI.
Method Name: Lock State:Set
So looking up this method help in LabVIEW indicates that the problem may be that the TestStand Deployment tool is trying to password protect type definitions which is not allowed.
I'm getting further along. I figured out that the problem is that there is a bug in your VI locking code. I figured this out because I removed strict typedefs from my project and it still didn't work. I then narrowed it down to other code types and concluded that the problem is Global VI's. Apparently you cannot password protect Globals. My project has one global VI. I removed it and it got further along in the build. This also indicates a bug in the LabVIEW documentation because it states you can lock globals, which is true, but you can't give them a password. So I'm getting further as I stated but now I'm getting error 1004 (LabVIEW: The VI is not in memory.). I'm still investigating...
I think that the issue may be with using *.lvlib files? Basically I'm calling a VI from within a TS sequence that is located inside a LabVIEW *.lvlib file. Could this cause problems when building a deployment?
I was able to reproduce this error 1004 in a dummy project. Find it attached. The 1035 error is easy to reproduce on your own by just including a globle VI in the build.
I have been able to reproduce the error on my end and I have something I would like you to try.
The proper way to deploy a Project Library (*.lvlib) from TestStand is
to insert a Deploy Library step before you call the VI with the shared
variables. To get the Deploy Library step you right click in your
sequence and go to Insert Step » LabVIEW Utility » Deploy Library.
Right click on this step and go to Configure Deploy Library... Change
the Library Path to the Project Library (*.lvlib) that contains your
shared variables. Set the Operation to Deploy. When you are done
calling the VIs, you need to Undeploy using the
same step. Set the Operation to Undeploy.
Also, make sure you add the .lvlib file to the workspace as well. In the example you posted, when I completed these steps, I could build the deployment successfully. I hope this helps!
