From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

BreakPoint

cancel
Showing results for 
Search instead for 
Did you mean: 

Site to look at current CARs?

Hello,

 

I am trying to find a way to look at the status of current CARs and have so far been unsuccessful in finding anything other than the bugfix lists for product releases. Specifically I am trying to find information on CAR #320545 as I believe I am running in to that issue. Thoughts? Ideas?

 

Thanks!

0 Kudos
Message 1 of 6
(6,804 Views)

There is not a way for people to get insight into CARs in LabVIEW.  All you can do is look for the bug fix in the release documents.  Now just maybe somebody inside of NI will be nice and look up that CAR for you and give you a status.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 6
(6,801 Views)

Hello,

 

That CAR relates to special characters not appearing correctly in the Volume License Manager.  Is this the issue you are running into?  If not, what trouble are you running into?

 

 

Jesse S.
Applications Engineer
National Instruments
0 Kudos
Message 3 of 6
(6,784 Views)

It isn't an issue displaying the characters. I can't import the .xml file. I am receiving the following error: "The following files were not loaded because they could not be read or are not valid NI VLM Import Utility files:" followed by the file path and name. Both the file name and the computer name in the file have " í "s in them (little accent thing instead of a dot). Searching for this pointed me to http://forums.ni.com/t5/Volume-License-Manager-and/Problems-with-VLM-Import-Utility/m-p/1877255/high... which listed that CAR. Thanks for your help!

0 Kudos
Message 4 of 6
(6,776 Views)

Removing the special characters in the computer name within the xml file appears to have fixed the issue. Assuming this is the same CAR, would that be a recommended workaround? Thanks!

0 Kudos
Message 5 of 6
(6,774 Views)

I think this is likely a separate issue - I would recommend posting on the Volume License Manager board or calling into support to work with them and try to identify if there is a new CAR. The original CAR you referenced relates specifically to displaying characters and appears to be fixed in VLM 3.1. 

 

Hope that helps,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 6 of 6
(6,751 Views)