lvwutil32 & TS4.x with LV8.5 RTE

[burgy]

Hi,

I am trying to complete a TS4.0.1 + LV8.5.1 RTE deployment that uses functionality within the lvwutil32 utilities.

Everything if OK with LV8.5.1 development environment but TS+LV crash out when I change over to the RTE. I believe this is because the Lvwutil32.dll needs to be rebuilt with the latest LV8.x??

Anyone experienced similar problems? and more importantly were you able to fix?

Any help appreciated - I can work around this issue, for my current small app., but these utilities are very usefull and I would like to continue using them.

PS: I have posted this message on the TestStand forum as well

Ian Burgoyne
Powerwave Tech.

[Matthew_Kelton]

I'm fairly confident that the LVWUtil32.dll is a C DLL.  There is no way it is a LabVIEW DLL, because it predates LabVIEW's ability to build DLL's.

Have you skipped the sections that use the DLL and confirmed that they are what's causing the problem?

Are you testing on the same PC you were using for development?  If not, it's possible you may be missing other drivers or components that you unknowingly used.  For example, recently a user I helped had used .NET controls and didn't have the same version of the .NET framework on the deployment machine as he had on his development machine, so his program wouldn't run.

[burgy]

Matthew,

Have you skipped the sections that use the DLL and confirmed that they are what's causing the problem?

IB: I have only skipped the LV call from TestStand - I will trace thru' to the DLL wrapper in LV but being a pessimist I immediately assumed the DLL was the problem

Are you testing on the same PC you were using for development?  If not, it's possible you may be missing other drivers or components that you unknowingly used.  For example, recently a user I helped had used .NET controls and didn't have the same version of the .NET framework on the deployment machine as he had on his development machine, so his program wouldn't run.

IB: Yes to same PC. I am just changing the adapter setting within TestStand

Ian

[burgy]

Matthew,

The fatal error flash screen displays the following text:"LABVIEW.LIB was not called from a LabVIEW process"

http://digital.ni.com/public.nsf/allkb/A4C3AEF93240280A86256931006FB66C?OpenDocument

Ian

[Matthew_Kelton]

Can you post the VI causing the problem?

[burgy]

Will do Mathew when I return to work on Tue.

Thanks for feedback so far

Ian

[Matthew_Kelton]

You can also look for CINs that you are using in the VI.  If you copied a CIN, it could be causing the issue.  I suggest trying to determine exactly where the error is occuring.

[Axel_DSR]

Ian,

I have exactly the same problem as you but TS4.0 + LV8.5 RTE

I already did a Mass Compile LV8.5.

My test sequence crash out when I change over to the RTE when using "lvwutil32.dll".

How did you solve this issue?

Thanks a lot.

Axel Sanchez

Mexico

[burgy]

Sadly I have no fix at the moment - I was pulled onto other 'more important' tasks!   The normal firefighting test activities 😞

Sorry I cannot help in the short term - I never understood why this functionality is not imbedded in LabVIEW. The platform independence excuse became invalid as soon as ActiveX support was added.

Ian

[AdnanZ]

Hi Axel and Ian,

Can one of you post an isolated version specific to this behavior so I can replicate it on my system over here? If need be, I can then get in touch with R&D and we can get to the bottom of this.