12-04-2014 08:46 AM
Solved! Go to Solution.
12-04-2014 09:18 AM
Please refer to the TestStand Lifecycle page for information on compatibility tests done by NI between TestStand and LabVIEW.
As you can see, LabVIEW 2012 is tested in combination with TestStand 2014.
Norbert
12-04-2014 09:26 AM
first tks for your reply,
i do not know how NI tested, when i run Teststand 2014, it happend errors to notice that
Teststand2014 64 Bit request at least labview 2013 SP1
12-04-2014 09:30 AM
Hm, ok.... but i see that the lifecycle page doesn't differ between TS 2014 32- and 64-bit. I find it possible that TS 2014 64bit indeed requires LV 2013 SP1 and newer whereas TS 2014 32bit accepts any LV 2011 and newer.
Can you switch to TS 2014 32bit for testing?
Norbert
12-04-2014 09:38 AM
i can try that, but no other better solutions ?
can not understand, why this happend between labview 2012 and Teststand 2012
i mean, the life cycle show this both can working together perfectly.
12-05-2014 02:09 AM
I would expect your initial issue to be created by invalid ActiveX registration of TestStand ActiveX controls.
You can try running the Version Selector tool from TestStand and re-register your 2012 TestStand.
Norbert
12-05-2014 03:04 AM
tks for the reply, but can you descripe me the concrete actions, what dll or ocx i need exactly manuel registry for teststand2012?
that will be great
12-05-2014 04:10 AM
Simply run the Version Selector Tool you find in the TestStand start menu (Windows Start menu).
Norbert
12-05-2014 04:46 AM
well. i did that before, but it not help to solve the problem
no mater how much time i switch to Teststand 2012 sp1
the error still there
12-11-2014 01:45 AM
Well, the problem is not solved, but i insalled Labview 2013 and Teststand2014, both in 64 Bit. Now the UI can work, but i need do so many initialise work.