MAX 4.7.x and System Configuration 1.1.x Known Issues

Überblick

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

113710 Import/Export wizards may fail to report errors
174178 MAX crashes when deleting multiple remote targets
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
231641 MAX crashes when installing LabVIEW RT software on a system containing Microsoft Office IME 2007
235091 Initialize (String).vi returns error if ' : ' is used
236028 Clicking the error button to view any errors after importing a MAX Configuration File does nothing
237136 Internal and External Calibration properties incorrectly returns an error for some devices
238246 NI Network Browser cannot find devices if any device's comments contain double quotation mark (") or a less-than sign (<)
238500 LabVIEW 2010 Real-Time systems will crash if multibyte characters are used in comments in MAX
240178 Filtering system names dialog box is broken in French versions
243152 Internet Explorer script error when accessing remote targets on certain non-English versions of Windows XP
245018 Cannot use System Hardware and System Filter property nodes on French and German operating systems
245620 Find.vi returns an error if NI System Configuration is installed from a Recommended Software Set to a Real-Time target
246669 System Configuration API may initialize incorrect RT system
255246 Host machines with IP addresses of 192.168.X.X show RT targets on different subnets as disconnected
255826 Get System Image.vi does not obtain files in hidden folders and files related to authentication from RT targets
257689 Systems using comma character (,) as a decimal symbol will see unhandled exception when accessing a remote target in MAX



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
174178

Return
MAX crashes when deleting multiple remote targets
During the discovery stage, MAX may crash if you attempt to delete multiple existing targets together.

Workaround: Launch MAX and try again or delete targets one by one.

Reported Version: 4.6    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
231641

Return
MAX crashes when installing LabVIEW RT software on a system containing Microsoft Office IME 2007
MAX crashes when installing RT software using the LabVIEW Software Wizard in MAX if the host system has Microsoft Office IME 2007 set as the default input language.

Workaround: Change the Default input language in the Windows Language Bar from Microsoft Office IME 2007 to Microsoft IME.

Reported Version: 4.6.2    Resolved Version: 4.7    Added: 08/02/2010
235091

Return
Initialize (String).vi returns error if ' : ' is used
If the "target" input of Initialize.vi is wired to a string containing the : character, Initialize.vi will return error -2147220622.

Workaround: Remove the : character.

Reported Version: 1.1    Resolved Version: N/A    Added: 08/02/2010
236028

Return
Clicking the error button to view any errors after importing a MAX Configuration File does nothing
If any errors occur while importing a MAX Configuration File, clicking the error button does not display anything.

Workaround: N/A

Reported Version: 4.6.2    Resolved Version: N/A    Added: 08/02/2010
237136

Return
Internal and External Calibration properties incorrectly returns an error for some devices
If the IntCal or ExtCal property is queried for NI-DAQmx devices that do not have a valid Last Temperature value, the property node incorrectly returns an error, even if there is a valid Last Date value.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 08/02/2010
238246

Return
NI Network Browser cannot find devices if any device's comments contain double quotation mark (") or a less-than sign (<)
If the Comments field on any device on a local subnet contains a double quotation mark (") or a less-than sign (<) character, the NI Network Browser will fail to find any devices on the subnet.

Workaround: Remove the " or < characters from the Comments field on all devices on a subnet.

Reported Version: 1.1    Resolved Version: N/A    Added: 08/02/2010
238500

Return
LabVIEW 2010 Real-Time systems will crash if multibyte characters are used in comments in MAX
LabVIEW 2010 Real-Time systems can crash if other LabVIEW 2010 Real-Time systems on the same subnet use multibyte characters (such as Japanese, Korean, or Chinese) in the Comments field in MAX.

Workaround: Refer to KnowledgeBase 5BQCM7Q7, or visit ni.com/info and enter the Info Code MAXMULTIBYTE.

Reported Version: 4.7    Resolved Version: 4.7.2    Added: 08/02/2010
240178

Return
Filtering system names dialog box is broken in French versions
The System Configuration IO Filter System Names dialog box does not display all items correctly in its dropdown boxes.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 08/02/2010
243152

Return
Internet Explorer script error when accessing remote targets on certain non-English versions of Windows XP
On non-English versions of Microsoft Windows XP (including Italian, Swedish, and others), trying to access a remote target through MAX will result in an Internet Explorer script error. This issue will then cause the right-hand view of the remote target to not display correctly.

Workaround: Install support for East Asian languages in Windows XP.

Reported Version: 4.7    Resolved Version: 4.7.3    Added: 08/26/2010
245018

Return
Cannot use System Hardware and System Filter property nodes on French and German operating systems
The System Hardware and System Filter properties nodes are unusable on French and German operating systems. An error will be displayed in LabVIEW if either of these property nodes are placed on the block diagram.

Workaround: Refer to KnowledgeBase 5CJDNP9T: System Hardware and Filter property nodes return errors on French and German versions of LabVIEW.

Reported Version: 1.1    Resolved Version: 1.1.3    Added: 08/26/2010
245620

Return
Find.vi returns an error if NI System Configuration is installed from a Recommended Software Set to a Real-Time target
If NI System Configuration is installed from a Recommended Software Set (RSS) to a LabVIEW Real-Time target, calling Find.vi from the host VI on that target will return error -2147220616: "The System Configuration API is not installed at the specified target." This issue occurs because the RSS does not contain all necessary System Configuration components.

Workaround: Manually install NI System Configuration, NI System Configuration network support, and NI Web-Based Configuration and Monitoring to the LabVIEW Real-Time target.

Reported Version: 1.1    Resolved Version: 1.1.3    Added: 08/26/2010
246669

Return
System Configuration API may initialize incorrect RT system
The System Configuration API may initialize a random RT system on your subnet if the "session in" input of a VI contains a target that is offline or does not exist. One way this will occur is if a string control/constant is wired to the "session in" input for a target that does not exist. Another way this will occur is if an I/O Control has "Hostname" selected in the I/O Name Filtering >> Display format field, and the selected target is offline.

Workaround: Use an I/O control with any Display format option other than "Hostname" selected instead of a string control. "Hostname (IP)" for example, will work. Also, ensure the target you're trying to communicate with exists and is running.

Reported Version: 1.1.1    Resolved Version: N/A    Added: 09/01/2010
255246

Return
Host machines with IP addresses of 192.168.X.X show RT targets on different subnets as disconnected
If a host machine has an IP address of the form 192.168.X.X and it tries to add a remote device in MAX, the device is added correctly but always shows up as disconnected. Note that the host can ping this target successfully, but cannot communicate with it in MAX.

Workaround: N/A

Reported Version: 4.7.3    Resolved Version: 4.7.4    Added: 10/29/2010
255826

Return
Get System Image.vi does not obtain files in hidden folders and files related to authentication from RT targets
A system image created with the Get System Image VI does not obtain all files from the RT target. Files related to user authentication and files in hidden folders are not replicated in the image.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 10/29/2010
257689

Return
Systems using comma character (,) as a decimal symbol will see unhandled exception when accessing a remote target in MAX
Systems with regional settings that specify the comma character (,) as the decimal symbol will see an unhandled exception when navigating to the Network Settings or Time Settings tab for a Remote Target. MAX returns this exception only when the remote target you access is not in safe mode and has NI-TimeSync 1.1 or later installed.

Workaround: Change the regional settings on the system to use the dot character (.) as the decimal symbol.

Reported Version: 1.1    Resolved Version: N/A    Added: 11/16/2010

Document last updated on 11/16/2010

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