Deploy TestStand System error

[BERICHARD]

When I try to run:
Tools>>Deploy TestStand System>>Deployed Files>>LabVIEW Options>>Lock VI Diagrams
I get the following error after I hit the Build key:
Failure : linker.cpp line 2022
LabVIEW version 6.1
I suspect I need version 7.0?? Can anyone confirm this or let me know what I'm doing wrong?

[Rick_Francis]

I believe that the error you are seeing is due to a specific VI in your system. It may be a LabVIEW 6.1 bug, or it may be a corrupted VI.

I tried locking a generic 6.1 VI and it worked just fine. To solve the problem you need to narrow down which VI causes the error. You might try distributing a sequence that contains a subset of steps by cutting and pasting from your sequence to an empty sequence. Once you have narrowed it down to a particular top-level VI you can attach it for us to do some diagnostics.

[BERICHARD]

Rick,
I've only got one simple vi in my sequence. I can run the build utility with no errors until I select the "Lock VI Diagrams" option. Note that my error code is now 1035 instead of 2022 like it was previously. The 2022 error was caused by not suppling password in the Lock VI Diagram box.

Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller

[Rick_Francis]

I did some testing and discovered a bug with LV6.1- The save function errors out when trying to save controls such as Test Data.ctl with the locking option.

You can work around this problem by manually locking the control(s) before doing your build.

The error code 1035 is generated because controls can't have locking passwords.

[BERICHARD]

That's what I was afraid of. I guess I'll try converting my code to 7.0. Where did you find the error code info? All I could find in the following from LabVIEW help menu "Explain Error".


Warning 1035 occurred at an unidentified location.

Possible reasons:

LabVIEW: Operation is invalid for this type of VI.

[Rick_Francis]

Rather than converting the code, here is a fix to the deployment utility that works around the problem. I made a small change to TestStand\Components\NI\Tools\Deployment Utility\TestStand - Build VI Distribution\TestStand - Dist Chg and Save VIs.vi Now the VI will not set the lock state on controls. Rename the old TestStand - Dist Chg and Save VIs.vi and copy the attached VI to your system. Let me know if that solves the problem.

[nawang]

I did a convert to the Labview 7.0. Somehow I am still getting 1035 error. The code is written in Labview 6.1. I did remass compile in Labview 7.0. When I try to do a deployment using Test Stand 3.0. 1035 error is occured.

[Rick_Francis]

Did you try installing the updated VI? If not try that update. If the problem is trying to password protect controls that will take care of it.

[nawang]

Where is this updated VI? You mean the binary file you changed on the TestStand to replace the existing one. I try that, too. It still gives me 1035 error.

[Rick_Francis]

There was one other condition that I've seen that can cause error 1035- if we try to lock a VI that is already password protected. Try replacing the TestStand - Dist Chg and Save VIs.vi with the attached file. If that doesn't fix it, then please post a VI that demonstrates the problem.