MAX 5.0.x and System Configuration 5.0.x Known Issues

Overview

This document contains the Measurement & Automation Explorer (MAX) 5.0.x and System Configuration 5.0.x known issues that were discovered before and since the release of MAX 5.0.x and System Configuration 5.0.x. 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.0.x and System Configuration 5.0.x Known Issues sorted by Date.

113710 Import/Export wizards may fail to report errors
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
225580 DHCP address not assigned if target is not immediately restarted after Network Settings are saved
225915 Chinese, Japanese, and Korean comment strings show up improperly
227480 MAX provides no warning when the same static IP address is used on multiple targets
258540 Deploying an image of a standard RSS to a cRIO may cause the FPGA target on that cRIO to disappear from MAX
281382 Find (Systems) VI may hang if executed repeatedly on a Real-Time target
282710 Adding network cDAQ device with old firmware to MAX might crash MAX
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
303218 LabVIEW Real-Time Software Wizard may time out while waiting for a target to reboot on a Windows XP system with multiple NICs
308070 The Initialize VI may initialize incorrect system if only the IP address is specified
308775 Obtaining the NI System Configuration C API property NISysCfgResourcePropertyNumberOfExperts always returns NISysCfg_PropMismatch error
309247 Installing a Startup Application to a Real-Time target will always install all software dependencies
309348 The Set System Image VI does not properly apply secondary NIC settings



ID Known Issue
113710

Return
Import/Export wizards may fail to report errors
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
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
225915

Return
Chinese, Japanese, and Korean comment strings show up improperly
After saving and refreshing a comment string containing Chinese, Japanese, or Korean characters, the comment string does not display the same characters previously entered.

Workaround: N/A

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
258540

Return
Deploying an image of a standard RSS to a cRIO may cause the FPGA target on that cRIO to disappear from MAX
If an image of a cRIO controller containing the standard RSS is re-deployed to the same controller, the FPGA target on the controller may disappear from MAX.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 04/27/2011
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
282710

Return
Adding network cDAQ device with old firmware to MAX might crash MAX
Adding a network cDAQ device with out-of-date firmware to MAX might cause MAX to crash. This has been seen with network cDAQ devices running firmware revision 1.1.0.

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
303218

Return
LabVIEW Real-Time Software Wizard may time out while waiting for a target to reboot on a Windows XP system with multiple NICs
The LabVIEW Real-Time Software Wizard may time out on a Windows XP system with multiple NICs connected to different, isolated subnets while waiting for a Real-Time target to reboot into install mode.

Workaround: N/A

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

Return
The Initialize VI may initialize incorrect system if only the IP address is specified
If a new Real-Time target shares the same IP address of a target that has recently gone offline, running the Initialize VI with only the IP address specified may try and initialize the offline target.

Workaround: Use the Hostname (IP) format

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

Return
Obtaining the NI System Configuration C API property NISysCfgResourcePropertyNumberOfExperts always returns NISysCfg_PropMismatch error
Querying NISysCfgResourcePropertyNumberOfExperts using NISysCfgGetResourceProperty will always incorrectly return the NISysCfg_PropMismatch error.

Workaround: N/A

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

Return
Installing a Startup Application to a Real-Time target will always install all software dependencies
Installing a Startup Application through MAX or through the System Configuration API will always install all software dependencies declared in the Component Definition, regardless of whether or not those dependencies are already installed on the Real-Time target.

Workaround: N/A

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

Return
The Set System Image VI does not properly apply secondary NIC settings
If an image of a target with two NICs is taken and deployed to a different target with two NICs, the secondary NIC settings of the target will not be applied correctly.

Workaround: Manually modify settings of secondary NIC after imaging

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

Document last updated on 8/11/2011

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