NI MAX will not populate the Systems Settings or other windows if certain security settings such as "Use FIPS-compliant algorithms for encryption, hashing, and signing." are enabled.
Troubleshooting Remote System Discovery incorrectly reports the Minimum Required Driver Version in certain scenarios.
NI MAX Technical Support Reports for PXI Linux Real-Time targets do not list software at the top of the report.
NI MAX and NI System Configuration 19.0
NI System Configuration installer does not include header files on Linux.
On Linux RT devices, target discovery can cause the calling process to crash when a large number of NI discoverable devices are present on the network
NI System Configuration SerialPortBinding property is not exposed publicly.
NI System Configuration Help does not describe Slot Number and Number of Slots properties accurately for NI Serial devices
NI System Configuration and CVI define CVITime, CVIAbsoluteTime, and CVITimeInterval differently.
When interacting with a PharLap Real-Time device using the System Configuration API, the API will hang if the system has a network adapter set to DHCP Only that does not obtain an IP address.
Loading NI System Configuration before loading a LabVIEW-built shared library on Linux can cause the application to hang.
NI MAX and NI System Configuration 18.5
The Troubleshoot Remote System Discovery tool could get stuck while checking firewall status on Windows Server systems.
Device properties could incorrectly be stuck with a Loading... status when displayed within a table in NI MAX.
When using System Configuration 18.1 on Linux Desktop Operating Systems, the NISysCfgGetStatusDescription function will always return error -2147220616.
NI MAX and NI System Configuration 18.0
When logging to *.txt or *.csv files from NI I/O Trace, commands sent with the GPIB Interactive Control are not logged.
NI MAX crashes upon exit when installed on systems configured using the Secure Host Baseline.
Closing the Overwritten Resource handle returned by NISysCfgRenameResource could invalidate existing handles to the same resource.
System Configuration .NET API takes disproportionate amount of time when querying temperature or power sensors compared to the LabVIEW API.
Running the Initialize Session VI installed with System Configuration 17.5 on any system with System Configuration 17.0 or older installed throws Error 15. The error is thrown because the entry point called by the 17.5 version of the Initialize Session VI does not exist in versions of System Configuration prior to 17.5.
NI MAX will crash when updating device firmware if multiple NI MAX windows are open at the same time.
NI MAX and NI System Configuration 17.5
The Troubleshooting Remote System Discovery Wizard generates Error 1 on the "Searching for Remote Systems.." page when there are no targets to discover on the host's subnet
Calling the System Configuration API from more than one version of the LabVIEW Run-time Engine in the same process (i.e. two LabVIEW built DLLs each built with different versions of LabVIEW) throws error -2147024809
When setting an invalid property and calling the Save Changes VI subsequent reads of that property will return the value for the invalid property
Capturing API calls in NI I/O Trace 17.0 that pass strings in excess of 512 bytes in certain cases and in excess of 1024 bytes in other cases causes NI I/O Trace to crash when the "Buffer Limit per Parameter" setting is set to "Large Buffer (Maximum size: 64k bytes)"
NI MAX and NI System Configuration 17.0
NI MAX can crash when generating a Technical Support Report using the MAX Report Wizard
Using the Set Time VI to set the system time to some value in the past causes the System Resources:CPU and System Resources:Memory properties to stop updating
NI MAX and NI System Configuration 16.0.1
MAX displays "Inconsistent IP Settings" for Ethernet devices and fails to display local network adapter properties
NI MAX and NI System Configuration 16.0
Set System Image VI on Linux targets ignores blacklisting /c/ni-rt/ directory
NI System Configuration times out when deploying firmware to Linux RT targets over slow or congested networks
NI MAX and NI System Configuration 15.3
Crash when generating a report from MAX or NI System Configuration
Cannot use MAX to set Ethernet speed/duplex on a cRIO-9075 in safe mode
NI MAX and NI System Configuration 15.0
MAX Crash when Exiting Improvements
MAX cannot access cRIO-9068 when Get System Configuration permission is removed from 'Everyone' account
LabVIEW crashes if NI System Configuration tries to access a resource whose session has been closed
Using the same NI System Configuration session to set firmware and then get firmware revision yields old firmware revision
LabVIEW and CVI hang when cancelling out of the MAX Export Wizard dialog while trying to include hardware configuration in installer
Real Time target cannot use NI System Configuration to reboot itself when both network ports are set to DHCP only and fails to obtain an IP address
No method to programmatically remove unused devices using NI System Configuration
[Mac] LabVIEW crashes when running NI System Configuration Initialize Session.vi while connected to an SSL VPN
[Mac] LabVIEW crashes when calling NI System Configuration Find Systems.vi with many RT targets on the subnet
[Mac] SIGPIPE causes break in debugging when using NI System Configuration
NI MAX and NI System Configuration 14.5
NI MAX may time out when installing software to a real-time target
Running more than one Initialize Session VI in parallel does not improve, and may worsen, performance
NI MAX must be launched with elevated permissions to include ni_services.txt in a Technical Support Report
Formatting and installing software to a real-time target using Windows 8.1 resets the target's name to default
NI 5652 appears outside of the composite device in MAX
NI System Configuration may time out when deploying images to NI Linux Real-Time controllers, especially if the batch size is large or the network speed is slow
On Mac OS X, a GPIB Instrument will still be listed in MAX after its GPIB Interface has been deleted until after a refresh
On Mac OS X, NI MAX does not display the IP address for networked GPIB devices
On Mac OS X, MAX crashes when a device alias is set to an empty string
The Find Hardware VI fails, but does not return an error, if there is whitespace in the Experts string input
NI MAX and NI System Configuration 14.0.1
Unable to get or set real-time system image with only the NI System Configuration Run-Time Engine installed
Error -229771 during task creation when running from a LabVIEW project on a standalone cDAQ
NI MAX and NI System Configuration 14.0
myRIO Controller may not be discoverable on machine with many items in the domain search list
System Configuration Restart VI will return a timeout error if IP Address of myRIO changes during reboot
Using the Initialize Session VI and Close VI causes a memory leak on real-time targets
There isn't an easy way to get installed version of NI System Configuration at run time
The Set Time VI takes 4 seconds to execute on VxWorks targets if you are setting the time zone
MAX occassionally returns an exception when you delete disconnected systems
Installing NI-DAQmx or NI-VISA reinstalls an underlying System Configuration component, which causes the Create System Image VI to fail when called
Error -2147467259 when executing Get Installed Software VI on an NI cRIO-9082
NI MAX and NI System Configuration 5.5.1
For an NI Linux RT target in run mode, acquiring an image fails when a blacklist is applied
On a WES7 host, restarting a simulated cDAQ-918x/919x restarts the host
On a real-time target, a System Session for "localhost" returns 127.0.0.1 as the IP address instead of the IP of the real-time target
On a VxWorks target, the System Configuration API returns different values for FirmwareRev depending on how it is queried
MAX Crashes on exit
NI MAX and NI System Configuration 5.5
NI Web-based Configuration & Monitoring must be installed on a CompactRIO target to set the time using the Set Time VI
NI-RIO PXI devices show up twice in NI MAX
NI MAX crashes when expanding Devices and Interfaces
Using the Calibration Audit example displays an error for devices that do not support self-calibration
The Hostname and Supports Locking properties display error -2147220364 when called on a VxWorks target
Basic system monitoring capabilities are now installed with the core component of System Configuration. NI System Configuration Remote Support is no longer required for this functionality
Locally restarting a cRIO-9074 with NI System Configuration 5.4 installed returns an error
NI MAX and NI System Configuration 5.4
The Get System Experts VI affects performance and determinism on a VxWorks target with NI-RIO installed
The Set System Image VI hangs when applying an image taken from a target that didn't have an IP address
Logging in and out in NI Web-based Configuration & Monitoring does not change ability to modify properties on the Hardware Configuration page
The Set System Image VI returns an error when deploying an image created by the Real-Time VIs
NISystem Configuration 5.3.3
"The display information of the device was not valid" error when parsing XML files in Web Interface in non-English languages
Set System Image Returns Error -2147220327 when deploying image created by RT VIs
NI System Configuration 5.3.2
Adding network cDAQ device with old firmware to MAX might crash MAX
LabVIEW Real-Time Software Wizard may time out while waiting for a target to reboot on a Windows XP system with multiple NICs
Startup Application Components Always Install All Dependencies Even if They Are Already Present
Creating MAX technical report from command line crashes MAX
MAX hangs when Create New while expanding Devices and Interfaces
Property FreePhysMem doesn't work properly when executed on RT Target
NISystem Configuration 5.3
Uninstall All.vi not rebooting into safe mode after uninstalling
Get System Image.vi returns error -2147220322 when a directory path contains '#'
Get System Image.vi does not properly apply secondary NIC settings
NISysCfg always returns "NISysCfg_PropMismatch" error when querying "NISysCfgResourcePropertyNumberOfExperts"
Initialize.vi returns wrong system when specifying only IP address
NISysCfg installer doesn't install C API unless CVI support is selected
NISystem Configuration 5.1
Get Installed Software.vi on localhost does not work on 64-bit
Get Installed Software.vi opens broken in LabVIEW 8.6.1
Set System Image (File).vi returns an immediate error when called after Restart
NISystem Configuration 5.0
Internal and External Calibration properties incorrectly returns an error for some devices
Get System Image.vi fails when run on one Real-Time target trying to obtain the image of another Real-Time target.
Set System Image.vi will fail if the image contains a .aliases file
Get System Image.vi does not obtain files in hidden folders and files related to authentication from RT targets
Certain MAC Address formats will cause the Initialize VI to initialize the wrong target
Get System Image.vi cannot obtain zero byte files
NISystem Configuration 1.2
Initialize (String).vi returns error if ' : ' is used
System Configuration VIs are not re-entrant
Filtering system names dialog box is broken in French versions
VxWorks targets return an error when calling Get Installed Software.vi on itself
NISystem Configuration 1.1.3
System Hardware and Filter property nodes return errors on German and French OS
Cannot call Find.vi if only "NI System Configuration" is installed on RT target via RSS