[HELP] IVI Logical Names Corruption in TestStand and LabVIEW...

[ChristopherPovey]

I have a test set which contains five instruments which are accessed via IVI calls. NI MAX shows the Logical Names are all set and they are all assigned to the correct instrument drivers.

Everything was working fine. I could create and run TestStand IVI DMM, IVI Switch, and, IVI Tools steps referring to the IVI Logical Names in MAX. I could also create LabVIEW VI's with IVI calls to the IVI Logical Names in MAX.

One day I got an error from LabVIEW that the IVI Logical Name contained invalid characters. When I selected the dropdown list it was now empty (it had been populated before with the devices in listed in MAX). TestStand did the same, threw an error about IVI Logical Name contained invalid characters. Opening NI MAX, under the IVI, Logical Name branch all the logical names are still present and correct.

I assumed something had got corrupted, so I did a repair install of the IVI Compliance Package. No change. So I removed it completely, rebooted, and re-installed it. Again no change. I reloaded the IVI logical names from an XML file we have as part of the installation, but no dice.

Does anyone have any ideas? I would like to avoid a format and complete re-install from scratch if possible, but it might be the only solution? 😞

Thanks.

[ChristopherPovey]

Additional Information:

If I add a IVI DMM Step to TestStand 3.5 I get the following error:

"The National Instruments IVI Compliance Package may not be installed. The Installer for the IVI Compliance Package is located on the National Instruments Drivers CD-ROM (-17501)".

If I add IVI DMM Initialise VI to LabVIEW 2012, and run it with a valid Logical Name IVI for the DMM I get the following error:

"Primary Error (Hex 0xBFFA0010) Invalid value for parameter or property. Elaboration: IVI Configuration Server C API: Set failed. The name of the virtual name item must consist of one or more of the following: 'a-z', 'A-Z', '0-9', '!', or '_'".

As I mentioned before I reinstalled the IVI Compliance Package so it is not missing!

[SasounT]

Hello Christopher,

Could you please send screenshots of the error you are receiving?

have you tried resetting the NI MAX database? instructions below:

http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9

Could you list what logical names you have chosen?

Thanks, 
Sas

[ChristopherPovey]

---

@SasounT wrote:

Hello Christopher,

Could you please send screenshots of the error you are receiving?

have you tried resetting the NI MAX database? instructions below:

http://digital.ni.com/public.nsf/allkb/2C7480E856987FFF862573AE005AB0D9

Could you list what logical names you have chosen?

Thanks, 
Sas

---

I ran the process for resetting the database in MAX, but after the reboot the IVI Logical names all remained in MAX! I get the same error. I am going to try the ResetNIConfig Tool next.

Error message is attached.IVI ErrorIVI Logical Names

Edit: I managed to reset than add an IVI Logical Name for the Switch on our Test Set, but got the same error. Looks like I going to have to wipe it and start again. 😞

[SasounT]

Hello Christopher,

That's unfortunate. One last thing you could try before wiping is to repair NI MAX.

http://digital.ni.com/public.nsf/allkb/AC6ED75D3D93375686256E8E00245F0D

Best of luck,
Sas

[ChristopherPovey]

---

@SasounT wrote:

Hello Christopher,

That's unfortunate. One last thing you could try before wiping is to repair NI MAX.

http://digital.ni.com/public.nsf/allkb/AC6ED75D3D93375686256E8E00245F0D

Best of luck,
Sas

---

Unfortunately I have already tried a Repair/Remove/Re-install of the "IVI Compliance Package" and a Repair of NI MAX. 😞

Thanks for you suggestions though. 

I have the tools and hardware now to image the hard drive, so this time after I install Windows XP, then NI software, I will take drive images. If it happens again I can just restore the image! 🙂

[ChristopherPovey]

I am now wondering if the IVI Compliance Package version 4.5 is not compatible with TestStand 3.5?

I wonder if creating an IVI step in TestStand 3.5 trashed something?