Problem calling a LabVIEW VI that has changed from TestStand

[Dave_RS]

I have changed a VI and now when I try to run the sequence, I get an error from the Sequence Editor.

The prototype of VI ... changed.
You must update the prototype before executing the VI.
Use the TestStand Sequence Editor to update the prototype.

Error Code: 017600, Failed to load a required step's associated module.

I have clicked on the Reload VI Prototype, but this has not helped.

[Anand_Jain]

Hi,

Can you post the VI that causes the issue? You can remove all the content of the VI but keep the controls and indicators. 

Also, what version of TS are you using?

Regards, 

Anand Jain

NI

[Dave_RS]

Hi,

Can I post the VI privately? I am not sure what I can take out without breaking the VI.

Perhaps you could remove what needs to be removed and then post it?

I am using LabVIEW 2014 service pack 1 and TestStand 2014 service pack 1.

Best regards,

Dave

[Anand_Jain]

Hi, 

Sure, you can send it to me via private message. You will have to put the VI somewhere and post a link. 

Note: The versions of LV and TS are really old. It is very likely that the issue was fixed in newer versions of products. 

Regards, 

Anand Jain

NI

[Dave_RS]

Hi,

I have attached the VI with much of it stripped out as suggested.

Best regards,

Dave

[pboucher@werfen.com]

you might want to try deleting the TS step that calls the VI and re-create it.  Ive had some issues in the past where the seq file gets corrupted and just recreating the problem step it fixes it.   

[Anand_Jain]

Dave, 

Can you attach a copy of the sequence file with just one step that prompts to reload the VI?

Regards, 

Anand Jain

NI

[Dave_RS]

This is a copy of the sequence file with just the one step included.

Best regards,

Dave

[Dave_RS]

I tried this approach (of deleting and recreating the TestStand step), but unfortunately the problem remains.

Thank you for the suggestion however.

Best regards,

Dave

[pboucher@werfen.com]

Your Test.vi is still quite big.  and requires about of sub-vi's and ctls that were not included.

my suggestion is to delete ALL the code leaving ONLY the inputs and outputs.  which is what I had to do to your test.vi to get it to a "working" state.

My guess is that your issue is related to what ever control was here: 

could there be multiple locations where this control is defined on your PC and Labview is using the correct one but TS is pulling it from somewhere else?     

the "Search Directories" are not your friend.  I find its much better to get an error stating it couldn't find something then to have false sense that everything is ok, when TS is actually finding an old copy of something somewhere you are not expecting it to pull from.