Error -17600 [LV2010 & TS2010]

[swalkin]

Hi Norbert,

I have included some LV Projects in the new setup but not in this case. I am using the exact same setup currently that I did in the past:

- Build on Win7, Deploy on XP

- Litepoint drivers installed on both machines

The code doesn't even start at the moment, it gives the 17600 error straight away.

Do you know if there is a Labview Reader that I can install on the target machine to see if the VI's do actually run?

[Norbert_B]

I am not aware of any "LV Reader".

The secure way to identify the "faulty" module is to set all steps to Run Option >> Loading Option "Load dynamically". Your sequence should start execute then and run into the error for the first module which is broken. This is the suggested way to debug if you do not receive any information about the step/module which is creating the error.

Nevertheless, the error you are now seeing should state, which step is failing here to load its module. So the above suggested method is only viable if you have no idea of the modules name and location in the sequence.....

Another thing you can try is to install the LV development environment (leave it in eval) just to see if this changes something. Remember that you have to reconfigure your LV adapter to LV Dev Env in this case.

hope this helps,

Norbert

[swalkin]

Hi Norbert,

I am going to download and evaluation version of LV and install it on the target PC and see what error it throws back and see if it points me in the direction of what is causing the issue.

I'll let you know how I get along when I have it download, installed and tested.

I have stripped the code down to the exact step that is causing the issue, it is an issue with all my steps to communicate with the Litepoint HW so I have a small sequence with open/close comms and this is displaying the same issue I see with my overall test code so if I fix this sequence then I'll be good for the main test code.

Thanks.

[swalkin · Accepted solution]

Hi Norbert/Ray,

Thanks for your help and suggestions on this issue. I installed the LV evaluation version onto the target PC and there was an issue with a sub-dll that was not included in the "SupportVIs" directory.

Looking at the older TS builds, it was included in this directory without me adding it so I am not sure why it wasn't this time.

I have resolved the referencing of the dll and associated dll's and it is now running fine.

Thanks again.