Deploy error whe using VI packet library option

[LuigiM]

Hi,

I'm performing a deploy using TS2010 SP1 (4.5.1) & LV 2011 SP1 and I'm trying to use the new deploy option for the VI's "Packed Project Library".

The deploy succeed, but when executing the sequence all VI calls performed via the "Run VI asynch" step type doesn't execute.

Opening the deployed sequence and going to these steps TS signals that the VI prototype is changed. After doing the update everything works fine.

Do you know if this is a deployment utility bug? Seems that the utility doesn't update the VI prototype correctly into the deployed sequence file.

Clearly if we perform the deploy in a standard manner (not using packed library) the deployment is working correctly.

Waiting for an answer.

[Rick_Francis]

Luigi,

Could you post a zip file with a TSD file, sequence file and VIs that reproduces the problem?   We have a test case that builds a PPL for a sequence with an asynch call and it ran using the latest build.   I will install 4.5.1 and back test it too, but it would be useful to have a test case that reproduces the error.

-Rick Francis

[LuigiM]

Hi Rick,

I'm  very sorry to reply just yet but the activities (inside the company) runs very quickly so I haven't time to prepare a demo.

Now I prepared it.

In the attach you find the sources with also the deploy setup (tsw + tsd) and also the deploy result.

As you can see opening the sequence into the deployed image the sequence isn't running cause an error is caught due to a prototype error on Asynch called VI.

It is necessary to reload the VI prototype (just opening).

We used TS 4.5.1 (2010) SP 1 & LV 2011 SP1 f2.

Let us know.

Luigi Magni (CTA)

[LuigiM]

Hi Rick,

have you seen my response and my example case in attach?

Sorry but I solicitate you for a response cause the deploy still fails.

Sincerely

[Al.B]

Hi Luigi,

Thanks for providing these files.  Upon testing, I was able to reproduce the behavior with TestStand 2010 SP1, but not TestStand 2012, so it looks like the issue has been fixed.  I do plan to continue investigating the issue to see if this was an intended fix, or the result of some other change to the TestStand Deployment Utility.  i'll let you know what I find!

[LuigiM]

Many thanks,

I was sure that was a bug in this new feature od Deployment utility in TS2010 (SP1)...

I hope you are able to find and provide as a fix for TS2010 cause we have already stations in 2010 and we can not due the upgrade/update work for TS2012...

Waiting for a solution we remain, sincerely

[LuigiM]

Hi AI.B, have you some news/update regarding the TS2010 deploy issue? Have you found a way to solve the error? Please let me know as soon as possible. Sincerely