VI is not loadable

[CIM1]

Seems a fair bet in the 'wrong order'... 

Actually I think I installed LabView first - looking at some of the installed file timestamps.

Do I need to reinstall TestStand?

[RayFarmer]

I have just re-read my last sentence, I think my brain switched off for a moment.

LabVIEW then TestStand should be the best order. Maybe it's something with TestStand 2010 that has changed. I'll check my machine which has both on and get back to you later.

[AllenP]

There are a few components that are installed by LabVIEW only if TestStand is installed, so I would recommend TestStand then LabVIEW.  But if you do it the opposite way, it's not a big deal unless you need LabVIEW Remote Execution Support, in which case you can run the LabVIEW installer again and just get that component.

The timestamps are almost always based on when they were built by NI, not by when they were installed.  There may be a few files that are created during installation, but those are generally not common.

I wouldn't get too worked up about the order of installation of these two products, though.

[CIM1]

So would you recommend I now install LabView again to get some TestStand required components or install TestStand again to get some LabView components?

[AllenP]

TestStand will install the same no matter if LabVIEW is there or not.

Running the LabVIEW installer may let you choose additional components, but that is unlikely to be the cause of your problems unless you are calling remote VIs on versions of TestStand less than 2010.

[RayFarmer]

Hi,

I have checked my installed version of LabVIEW 2010 and it does have the TestStand addon and can be found in _TSUlity.llb.

Now I know the LabVIEW was installed before TestStand 2010 and the missing addon comes from the TestStand installation not the LabVIEW.

What I dont know is when you install TestStand does it install the LabVIEW components into all installed LabVIEWs or just the active version. My guess is the later. You could try refreshing your TestStand installation make sure LabVIEW 2010 is your active version.

[CIM1]

Thanks for responses thus far...

I am using a clean install on a clean Windows 7 64 bit system with no previous NI software at all - in fact I downloaded the latest 2010 LV and TS installers from NI (my latest developer discs are unfortunately in another office at the moment - not very convenient). Might this be the problem that it is not a DVD install?

Not sure I can force a TestStand refresh without an uninstall-reinstall as the TS updater says everything is up to date?

[AllenP]

TestStand's Version Selector copies these files into all LabVIEW directories it supports.  Installation order won't matter.  If that file is missing due to installing LabVIEW 2nd, it will get automatically copied if you start the Sequence Editor.