MAX 19.5 and NI System Configuration 19.5 Known Issues

Overview

This document contains the MAX 19.5 and NI System Configuration 19.5 known issues that were discovered before and since the previous release. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

This document contains the MAX 19.0 and System Configuration 19.5 known issues that were discovered before and since the release NI System Configuration 19.5. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.

Known Issues by Date

The following items are known issues in MAX 19.5 and NI System Configuration 19.5 sorted by Date.

587524NI-VISA Trigger Bus Query Property is not supported by NI System Configuration API.
633751NI MAX System Settings page doesn't populate when all host network adapters are disabled.
683930The Install Startup VI will reinstall all dependencies of the Real-Time startup executable even if those dependencies are present on the target
700712NI IO Trace on Linux displays only the hex code for properties instead of the property name
744123NI MAX can report an Inconsistent IP Settings status for network targets if NIC Teaming is enabled on Windows Server.



IDKnown Issue
587524

Return
NI-VISA Trigger Bus Query Property is not supported by NI System Configuration API.
NI-VISA allowed users to query for the PXI Trigger Bus number using the instrument session handle but there is no similar functionality in the NI System Configuration API.

Workaround: N/A

Reported Version: 15.3  Resolved Version: N/A  Added: 05/20/2017
633751

Return
NI MAX System Settings page doesn't populate when all host network adapters are disabled.
On any system that either has no network adapters, or has all network adapters disabled, the Systems Settings page in NI MAX for My System does not populate.

Workaround: Enable a network adapter on the machine.

Reported Version: 17.0  Resolved Version: N/A  Added: 05/20/2017
683930

Return
The Install Startup VI will reinstall all dependencies of the Real-Time startup executable even if those dependencies are present on the target
When using the System Configuration API Install VI to install a startup executable to a Real-Time system, all dependencies of the executable will be reinstalled to the target. This installation will happen even if those dependencies were previously installed on the target.

Workaround: N/A

Reported Version: 17.0  Resolved Version: N/A  Added: 05/02/2018
700712

Return
NI IO Trace on Linux displays only the hex code for properties instead of the property name
When using NI IO Trace on a Linux Operating System, only the hex code will display for certain properties and not corresponding the property name.

Workaround: Refer to nisyscfg.h for the numeric values that correspond to each property.

Reported Version: 18.0  Resolved Version: N/A  Added: 01/25/2019
744123

Return
NI MAX can report an Inconsistent IP Settings status for network targets if NIC Teaming is enabled on Windows Server.
If a Windows Server system is configured to use NIC Teaming, NI MAX may report Inconsistent IP Settings for network devices even if the network adapter configuration is valid.

Workaround: Disable NIC Teaming.

Reported Version: 19.0  Resolved Version: N/A  Added: 11/01/2019

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).