MAX 5.4 and System Configuration 5.4 Known Issues

Panoramica

This document contains the Measurement & Automation Explorer (MAX) 5.4 and System Configuration 5.4 known issues that were discovered before and since the release of MAX 5.4 and System Configuration 5.4. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of MAX the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document(not reported date)

Known Issues by Date

The following items are known issues in MAX 5.3.x and System Configuration 5.3.x Known Issues sorted by Date.


113710 Import/Export wizards may fail to report errors (Only Applicable to MAX)
91473 46EA9908 MAX behaves incorrectly with a disconnect ENET device in the system
217233 Exporting LabVIEW RT target configuration without expanding Remote Systems Devices and Interfaces returns incorrect information (Only Applicable to MAX)
225580 DHCP address not assigned if target is not immediately restarted after Network Settings are saved
227480 MAX provides no warning when the same static IP address is used on multiple targets
281382 Find (Systems) VI may hang if executed repeatedly on a Real-Time target
286591 Accessing Remote Systems and certain Network Devices on Windows Server may cause an Internet Explorer error
294730 Cannot prevent a Real-Time target from being rebooted by users that do not have reboot permissions
299006 Duplicate entries of LabVIEW software versions may appear in MAX
359857 Error Dialog when Exporting in MAX
360642 "S_relFsLib_FILE_NOT_FOUND" is printed on screen during cRIO target installation via MAX
399803 "The Initialize Session VI fails if the username is set to Admin unless System Configuration Remote Support is installed on the target.
406312 Locally restarting a cRIO-9074 with NI System Configuration 5.4 installed returns an error.


ID Known Issue
113710

Return
Import/Export wizards may fail to report errors (Only Applicable to MAX)
Under certain situations, Import/Export wizards may display only an error code, rather than a descriptive message. In other cases, these wizards could fail to report an error even if failure did occur.

Workaround: N/A

Reported Version: 4.5   Resolved Version: N/A   Added: 08/03/2009
91473
46EA9908


Return
MAX behaves incorrectly with a disconnect ENET device in the system
ENET Serial or GPIB devices added in MAX are treated as static resources. When the devices are off, MAX still attempts to connect to them. This can cause a timeout if you have a high port count.

Workaround: Delete the ENET devices from MAX.

Reported Version: 4.2   Resolved Version: N/A   Added: 08/03/2009
217233

Return
Exporting LabVIEW RT target configuration without expanding Remote Systems Devices and Interfaces returns incorrect information. (Only Applicable to MAX)
If you try to export the configuration of a LabVIEW Real-Time target without expanding Remote Systems Devices and Interfaces on that target, certain items will show up incorrectly in the Export Wizard.

Workaround: Expand Devices and Interfaces on the LabVIEW RT target before trying to export its configuration.

Reported Version: 4.6   Resolved Version: N/A   Added: 08/02/2010
225580

Return
DHCP address not assigned if target is not immediately restarted after Network Settings are saved
If you change the DHCP settings of a Real-Time target running VxWorks, such as a cRIO target, and then save but do not immediately restart the target, the DHCP settings will not persist.

Workaround: Restart immediately after saving.

Reported Version: 4.7   Resolved Version: N/A   Added: 08/02/2010
227480

Return
MAX provides no warning when the same static IP address is used on multiple targets
MAX allows you to use the same static IP address on multiple LabVIEW Real-Time targets without providing any warning or error.

Workaround: N/A

Reported Version: 4.7   Resolved Version: N/A   Added: 08/02/2010
281382

Return
Find (Systems) VI may hang if executed repeatedly on a Real-Time target
Find (Systems) VI may hang if it is executed repeatedly inside a loop on a Real-Time target.

Workaround: N/A

Reported Version: 1.2   Resolved Version: N/A   Added: 04/27/2011
286591

Return
Accessing Remote Systems and certain Network Devices on Windows Server may cause an Internet Explorer error
When trying to access Remote Systems or certain Network Devices on Windows Server OS, an Internet Explorer error will display a window explaining that the content is blocked by Internet Explorer Enhanced Security Configuration. The user will then be unable to view the System Settings and Network Settings tabs. Internet Explorer Enhanced Security Configuration is enabled by default starting with Windows Server 2003. See the following Microsoft article for more details: http://support.microsoft.com/kb/815141

Workaround: Disable Internet Explorer Enhanced Security Configuration.

Reported Version: 4.8   Resolved Version: N/A   Added: 04/27/2011
294730

Return
Cannot prevent a Real-Time target from being rebooted by users that do not have reboot permissions
Users that do not have reboot permissions under the Web-Based Security Configuration of a Real-Time target are still able to reboot that target.

Workaround: N/A

Reported Version: 5.0   Resolved Version: N/A   Added: 08/08/2011
299006

Return
Duplicate entries of LabVIEW software versions may appear in MAX
Certain upgrade scenarios can cause multiple entries of the same LabVIEW software version to show up under the Software tree in MAX each time the Software tree is refreshed.

Workaround: N/A

Reported Version: 5.0   Resolved Version: N/A   Added: 08/08/2011
359857

Return
Error Dialog when Exporting in MAX
An error dialog is prompted when exporting the DAQmx nodes in MAX File >> Export

Workaround: N/A

Reported Version: 5.3   Resolved Version: N/A   Added: 08/30/2012
360642

Return
"S_relFsLib_FILE_NOT_FOUND" is printed on screen during cRIO target installation via MAX
After formatting the cRIO target, during the installation, MAX prints several internal error messages(S_relFsLib_FILE_NOT_FOUND) on screen.

Workaround: N/A

Reported Version: 5.3   Resolved Version: N/A   Added: 08/30/2012
373614

Return

Set System Image.vi hangs when applying image that was taken from a target that had never had the IP address set after formatting it

Workaround: Add the below token to the ni-rt.ini. *NOTE only add this token if experiencing this bug.

[TCP_STACK_CONFIG]

IP_Address = USE_DHCP

Reported Version: 5.3.3   Resolved Version: N/A   Added: 10/18/2012
381024

Return
Property FreePhysMem doesn't work properly when executed on RT Target

The FreePhysMem, or Free Physical Memory, property of the Real Time System Property Node doesn't work properly if called from the RT Target. When run, even if the property node is in a loop, it only returns the initial available memory

Workaround: N/A

Reported Version: 5.3   Resolved Version: 5.3.2   Added: 12/28/2012
399803

Return
The Initialize Session VI fails if the username is set to Admin unless System Configuration Remote Support is installed on the target.

Workaround: Leave the username blank.

Reported Version: 5.4   Resolved Version: N/A   Added: 09/06/2013
406312

Return
Locally restarting a cRIO-9074 with NI System Configuration 5.4 installed returns an error.

Workaround: N/A

Reported Version: 5.4   Resolved Version: 5.5   Added: 12/28/2012

Document last updated on 9/6/2013

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).