TestStand 3.5 Deploy error 1035

[LuigiM]

I  found an error that probably someone and especially Rick Francis & Ray Farmer, can help me to solve.

I'm usign TS 3.5 with LV 8.2 & CVI 8.0, when trying to do a deployment when setting the "Lock VI" check (with setting a password) I receive the following error:

Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Lock Heirarchy.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi->TestStand - Build VI Distribution 8 AX Wrapper.vi.ProxyCaller<APPEND>
Method Name: <b>Lock State:Set</b>

Of course I have opened the VI called by our sequence but all themm seems to be ok (no broken arrow) and when we do the deploy without the "Lock VI" check the deployment process goes fine.

It could be possible that is the same reason that Francis pointed out in a previous thread regarding the bug of locking VIs when already locked or something like that?

Thanks in advance for your responses.

[Filippo_Persia]

Dear Luigi,

Seems this problem is connected to password locking custom controls.
Would you be so kind to check this point ?.

Did you try also with TestStand 4.0 ?

Best Regards

[LuigiM]

Thank Filo for your esponse.

Yes, we have some custom controls built for this project and we need, of course, to deploy them.

There is a workaround in order to avoid to apply the lock VI to custom control or there is a patch that avoid to lock ctl files?

At present we haven't tried with version 4.0 cause more time is needed to check (and reapply) our custom process model and also customization of Database step type...

Sincerely

---

@Filop wrote:

Dear Luigi,

Seems this problem is connected to password locking custom controls.
Would you be so kind to check this point ?.

Did you try also with TestStand 4.0 ?

Best Regards

---

[AllenP]

The problem with controls and password protection seems to be corrected in TestStand 3.5.  I was able to create a deployment in TestStand 3.5 with a custom control and add a password to the deployment without any issues.  It appears that your use case is somehow different.  Can you provide a small example that will reproduce the behavior so that we can take a closer look?  Are you locking the controls or VIs before you try to deploy in TestStand?

Allen P.
NI

[LuigiM]

We have done some trials, and also when we exclude from the deploy our custom controls (some of them are Type Def) we encounter the same error (of course when we activate the Lock VI flag).

Some of our VI use the Word Report VI that are already locked it could be the problem?

We are doing other trials...

Your help is apreciated...

[Josh_W]

LuigiM,

I tried reproducing this behavior with the Word report VIs as you described, and I could not get the error you encountered.

Could you post a simple sequence file and VI that reproduce this error?

Thanks!