Measurement Studio 2015 Known Issues by Date

Aperçu

This document contains the <product> <version> known issues that were discovered before and since the release of <product> <version>. 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.

Overview

This document contains the known issues that were discovered before and since the release of Measurement Studio 2015. Not every issue known to NI appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Each known issue 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 Measurement Studio 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 the reported date)

Document Organization

The Known Issues Document is divided into two separate tables appearing in two separate documents. The known issues in this document are organized by the date they were added to this document. To view the issues organized by category, visit the document linked below:

Known Issues by Category

Contacting NI

You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative.

Known Issues by Date

The following items are known issues in Measurement Studio 2015 sorted by Date.

111651 The error, "Attempting to deserialize an empty stream", sometimes occurs when you attempt to build a Web Site project using Measurement Studio controls.
116288 Resizing the font of the CWNumEdit control causes the text to flicker before it updates.
120249 If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.
122353 Mouse cursor changes to the default mouse cursor after zooming.
127067 Measurement Studio Support for Visual Studio 2005 Visual C++ examples do not compile when upgraded to Visual Studio 2008.
133220 4B89AJ00 Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT.
133256 4DDCC0IO Creating network variables causes a small memory leak
133318 Measurement Studio controls might exhibit evaluation behavior.
133322 In some circumstances, you receive error, HRESULT E_FAIL, when using the DAQ Application Project Wizard.
133332 When the Windows Forms Designer and a source code window are both open, and the Windows Forms Designer is active, the Parameter Assistant does not restrict code from being inserted into the source file.
133380 In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler.
133384 In some instances, running your Visual C++/CLI project results in unlicensed exceptions.
133396 Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly.
133413 The Windows Forms Designer presents an error page stating that parts cannot be found.
133415 The Analysis library calls the LoadLibrary function.
133416 If you have created a Visual C++ Console Application and are linking statically to MFC, you may encounter LNK2005 and LNK1169 errors.
133421 Measurement Studio Visual C++ controls do not support being hosted in HTML dialogs.
133422 The wrappers that Visual C++ generates for the Measurement Studio ActiveX controls are incomplete.
133439 Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed.
31271 40A7S0HW Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value.
33154 483FFE00 The Parameter Assistant does not always show NI-VISA resources or NI-488.2 boards.
96497 Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException.
98865 3ZNCBRAF If you create a managed Visual C++ project using the Windows Application template, put a Measurement Studio .NET control on the form, and add a setup project to the solution using the primary output of the C++ project, you will receive a missing file error when you build.
115770 Measurement Studio UI controls that are part of a custom Web control do not display during design time.
130937 Dotted lines in ActiveX controls are printed as solid lines in some cases.
33786 Undo does not work for some Measurement Studio .NET properties when edited from the Microsoft Visual Studio Designer.
151406 Setting the annotation style of a CWGraph to Range or Half Space causes the numbering to disappear for the X and Y axes.
156506 The Microsoft C++ Add Variable wizard throws a script error when Internet Explorer 8 is installed.
181843 Dropping a Measurement Studio .NET control into a Visual Studio Web application at design time may result in an error.
182120 Network Variable does not support variables with the Timestamp data type.
182150 The Visual C++ VectorMatrix streaming example displays errors when the "Save to Binary File" button is pressed.
182154 The Visual C++ RegistryExplorer example may cause an access violation exception when trying to delete a registry key.
191580 Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries.
191880 Matrix operations that utilize the Intel MKL on Windows have slight numerical difference between Measurement Studio 2009 and prior Measurement Studio versions.
222719 Custom division labels may be clipped on the far right side of the x-axis of the intensity graph.
211806 Intellisense does not display help for methods containing a 2D array as a parameter for Visual C# projects in Visual Studio 2005.
216981 Modifying a collection property of a .NET control from the Visual Studio Designer might not always work.
220060 The 64-bit Logos merge module does not contain the commands necessary to install necessary Logos services.
239529 Autoformatting a .NET waveform, scatter, complex, or intensity graph at design time removes captions from existing annotations.
240646 The background of Measurement Studio .NET controls does not remain transparent when the controls are disabled.
247775 Measurement Studio .NET controls do not work in the MFC CWinFormsControl control.
251034 Zoom animation is drawn even when a .NET graph has not been added to a Windows Form.
251984 Waveform timing information is lost if a network variable with a waveform type is bound to a waveform graph.
198036 Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese.
286890 The Evaluate Products button on the Measurement Studio Activation dialog box is not localized for non-English operating systems.
297181 Building a Measurement Studio ASP.NET Web Forms project fails on computers with United States Federal Information Processing Standard (FIPS) enabled.
301621 The Measurement Studio Help is not uninstalled when Measurement Studio has been uninstalled.
308151 If the FillToBase property is set for a plot on a CWGraph, calling ControlImage on the CWGraph can result in a hang.
309646 When drawing very thick plot lines on a Measurement Studio .NET graph, the line can draw incorrectly.
291673 Adding a Measurement Studio control to a Web User Control in an ASP.NET Web application project might result in an error.
292392 Calling Filter.Reset can change the characteristics of the filter.
298877 Adding Measurement Studio .NET 3.5 assemblies to an ASP.NET Web site that targets .NET 4.0 results in incorrect dependencies added to the project.
307898 The Measurement Studio License Status dialog box sometimes displays a button named "Launch Product" instead of "Evaluate Products"
296833 The Parameter Assistant throws an exception and does not respond when browsing Source URL for NI DataSocket.
314617 Measurement Studio ActiveX controls cause all controls to not anchor to right side of form.
332295 The Windows Forms ScatterGraph displays a red "x" when out of memory, but does not throw an exception.
337384 Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.
338874 If you set the WebForms InteractionMouseCursor property through the designer, the page does not save when using certain controls.
339586 Changing the RangeAdjuster on a WPF Graph does not cause an immediate update.
344059 Custom install locations are ignored when National Instruments Merge Modules target is set to the Module Retargetable Folder.
351983 When using an AxisDateTime or AxisPrecisionDateTime axis on a WPF Graph control, FitLoosely has the same behavior as FitExactly.
361842 Icons for DataSocket URLs do not display with the DataSocket.SelectUrl popup.
338802 Calling the ClearData method on the Windows Forms DigitalWaveformGraph control a second time on an empty graph causes the horizontal scrollbar to disappear.
352017 The RangeLabelDivision.LabelPresenter property of the WPF Graph controls does not accept a single letter for a general formatter value.
359680 The Snap and SnapPointer InteractionMode of the WPF Knob, Meter, Slider, and Tank controls do not work when the MechanicalAction property is set to SwitchUntilReleased..
365949 Plotting a point that contains infinity for both coordinates in a WPF Graph control will not render accurately.
366974 The arrow label to an annotation on a WPF Graph control can shrink and disappear depending on the size of the label and its alignment.
367070 Double-clicking a WPF control in the Visual Studio Design view creates an event handler, but does not switch to the code behind where the event handler was created.
373005 The WPF IntensityGraph control color marker smart tag editor may become inconsistent with the XAML code.
373425 Adding an Object type in the "Object Collection Editor: Children" dialog for WPF Graph controls corrupts the Children collection.
382120 Changing axis ranges on CW3DGraph does not cause surface plots to redraw.
382703 The Instrument Driver Wizard does not remove HTML entities from comments.
383777 The SwitchWhenPressed InteractionMode for the switch and LED Web Forms controls does not work in Internet Explorer 10.
383780 Web Forms Graph interactions do not work when using Internet Explorer 10.
383852 Scrolling does not work in the WebForms Legend and DigitalGraph controls when using Internet Explorer 10.
384492 Repairing Measurement Studio 2013 for Visual Studio 2008 also prompts you to repair Measurement Studio 2012 for Visual Studio 2008.
385490 The Licenses.licx file is not updated properly when updating a .NET 4.5 ASP.NET project with .NET 4.0 and .NET 4.5 Measurement Studio project references.
386176 The Name property is not added for WPF controls added from the Toolbox in Visual Studio 2012.
389778 Invalid property values input in the Property Editor or the Smart Tag editor for WPF controls may be inserted into XAML for some properties.
389801 Changing a WPF Numeric control's data type may restore the Grid.Row property to zero.
501674 An older Global Assembly Cache (GAC) assembly is removed when installing a newer version of the assembly to the GAC with an installer built with Installer Builder.
502114 The description URL does not appear on install for digitally signed installers built with Installer Builder.
508665 The Include Recommended Installers Only option on the NI Driver & Components tab does not do anything.
401356 An Exception has been thrown by the target of an invocation error occurs at System.RuntimeTypeHandle.CreateInstance when Measurement Studio WPF controls are used in a Prism framework view.
434140 The Convolve2D method in the Analysis DSP library throws an AccessViolationException when called on a large matrix with millions of elements or when called repeatedly on smaller matrices.
449638 NationalInstruments.Analysis.Dsp.Filters.IirFilterBase does not have a method for calculating forward and reverse filter coefficients.
461933 The Refresh Project License File feature deletes all entries of the .licx file without a prompt, if the project contains invalid National Instruments references.
485392 Enum properties do not appear as changed in the Property Dialog Editor when launched from a Collection Editor dialog in Visual Studio 2012 and 2013.
499316 Some localized Windows operating systems may cause a compile time licensing failure with the error message LC.exe - Assert Failure.
513981 Calling Cursor.Move or Cursor.MoveNext does not always result in the cursor index increasing by the correct amount in ASP.NET applications.
518031 On certain localized Windows operating systems, Measurement Studio licensing fails at compile time with an LC.exe - Assert Failure message.
521828 Vertical axis gridlines disappear when rendering only digital data in a WPF mixed signal graph.
523024 The ASP.NET Update Project References feature does not add references to dependent assemblies.
525863 The Company Name field on Measurement Studio»About Measurement Studio is displayed as ????????? on a Japanese OS.
526156 Japanese characters in the YAxis Caption of a Windows Forms graph display upsidedown.
529944 A field validation error occurs when you set the Output Directory on the Basic Options tab to a non-existent network path.
529950 An Error: An internal tool or library returned an error. message displays when Installer Builder initializes the build log for the first time.
529958 Adding a merge module that is open in an editor (e.g., Orca) results in unexpected behavior.
534324 Registry keys imported by Installer Builder are not saved properly to the .iip project file.
534325 Registry keys imported by Installer Builder are not properly built into the installer.
534441 (Default) registry key values do not appear in the value field on the Registry tab of Installer Builder after opening a project which contains values for (Default) registry keys.
534442 Importing registry keys from a .reg file can result in multiple, duplicate copies of the registry keys in the Registry tab.
534443 Opening a project containing imported registry keys for the SOFTWARE hive results in both a SOFTWARE key and another Software key of a different capitalization
537212 Setting the XPosition property of an XYCursor (SnapMode: ToPlot) set to a specific value fails in large sets of x data.



ID Known Issue
111651

Return
The error, "Attempting to deserialize an empty stream", sometimes occurs when you attempt to build a Web Site project using Measurement Studio controls.
On Microsoft Windows Vista x64, when using Visual Studio 2008 without Service Pack 1 installed, the error "Attempting to deserialize an empty stream" occurs when you attempt to build a Web Site project using Measurement Studio controls.

Workaround: Upgrade Visual Studio 2008 to Service Pack 1.

Reported Version: 8.5    Resolved Version: N/A    Added: 11/17/2008
116288

Return
Resizing the font of the CWNumEdit control causes the text to flicker before it updates.
When resizing the font of the CWNumEdit ActiveX control, the text flickers back to the default size momentarily and then updates. This behavior occurs in Visual C++ and Visual Basic 6 but does not occur in .NET.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
120249

Return
If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.
At page load time, Measurement Studio dynamically filters documentation based on the components or package you have installed. If you copy and paste dynamically filtered help content into a text editor, such as Microsoft Word, you may see content that applies to components not installed on your machine.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
122353

Return
Mouse cursor changes to the default mouse cursor after zooming.
After zooming in on a waveform graph in a Measurement Studio .NET WebForms application, the mouse cursor changes to the default mouse cursor until you move the mouse.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
127067

Return
Measurement Studio Support for Visual Studio 2005 Visual C++ examples do not compile when upgraded to Visual Studio 2008.
If you upgrade a Visual Studio 2005 VCNET example or to Visual Studio 2008 by opening the Visual Studio 2005 solution in Visual Studio 2008, the upgraded application will not compile. The application will not compile because National Instruments defines the minimum system requirement through the symbol _WIN32_WINNT, which is set to 0x0400 (WINNT). This value conflicts with the SDK 6.0 default value of _WIN32_IE, which is used by Visual Studio 2008 Visual C++.

Workaround: You should make the values of _WIN32_WINNT and _WIN32_IE compatible for usage with SDK 6.0. To do this, either increase the value of _WIN32_WINNT to 0x0500 (Win2k) or decrease the value of _WIN32_IE to a value <0x0601.

Reported Version: 8.6    Resolved Version: N/A    Added: 11/17/2008
133220
4B89AJ00


Return
Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT.
Logos is the National Instruments proprietary protocol for inter-process communication that is used by NI-Publish Subscribe Protocol (psp:). Performance is especially degraded when the writer and network variable host use LogosXT and the reader that attempts to read the network variable uses Logos. This issue occurs for all reader classes.

Workaround: For optimum performance, National Instruments recommends that all machines accessing network variables, including the machine that hosts the variable, should use LogosXT. If using LogosXT on all machines is not possible, you should disable LogosXT. You disable LogosXT by adding a DWORD value named DisablePSPXT to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LogosXT and setting its value to 1. If you must use a mix of Logos versions, you can reduce the performance loss by using Variable Manager. Use Variable Manager to configure a sufficiently large server-side buffer for the network variable.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
133256
4DDCC0IO


Return
Creating network variables causes a small memory leak
Creating a network variable using the ServerVariable.Create or ServerVariableInfo.Create methods results in a memory leak of approximately 50 bytes per variable that is created.

Workaround: Consider using implicitly created network variables if you are creating and deleting numerous variables over a long period of time.

Reported Version: 8.5    Resolved Version: N/A    Added: 11/17/2008
133318

Return
Measurement Studio controls might exhibit evaluation behavior.
If you have installed Measurement Studio 8.5 on a machine that has earlier versions of the Measurement Studio user interface and 3D graph controls and then uninstall Measurement Studio 8.5, the controls might exhibit evaluation software behavior for 30 days. Note: Applications that install earlier versions of the Measurement Studio user interface and 3D graph controls include ComponentWorks 2.0, Measurement Studio 1.0 and later, and LabVIEW 6i and later.

Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.

Reported Version: 6.0    Resolved Version: N/A    Added: 11/17/2008
133322

Return
In some circumstances, you receive error, HRESULT E_FAIL, when using the DAQ Application Project Wizard.
When you use the DAQ Application Project Wizard within Visual Studio, Visual Studio occasionally gets into a state where it reports the following error: Error HRESULT E_FAIL has returned from a call to a COM component.

Workaround: Restart Visual Studio to fix this issue.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
133332

Return
When the Windows Forms Designer and a source code window are both open, and the Windows Forms Designer is active, the Parameter Assistant does not restrict code from being inserted into the source file.
Instead, code is inserted into the source file at the last cursor location, which might have been changed by the Windows Forms Designer.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133380

Return
In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler.
The network variable class library deadlocks if you are stepping through code in a network variable class library event handler and you are watching any of the following properties in the Debugger Watch Window:

  •  ConnectionStatus,

  •  NetworkVariableBufferedSubscriber.ItemCapacity,

  • NetworkVariableBufferedSubscriber.ItemCount,

  •  NetworkVariableBufferedWriter.ItemCapacity, or

  • NetworkVariableBufferedWriter.ItemCount.


When the Debugger evaluates properties in the Watch Window, it freezes all other threads except the currently executing thread. When the network variable thread is frozen, the network variable class library deadlocks.

Workaround: To work around this issue, do not add the properties listed above to the Watch Window when stepping through network variable event handler code.

Reported Version: 8.1    Resolved Version: N/A    Added: 11/17/2008
133384

Return
In some instances, running your Visual C++/CLI project results in unlicensed exceptions.
In Visual C++/CLI projects, when you drop a Measurement Studio control on a form, Visual Studio references the Measurement Studio assemblies from the GAC. If you select Measurement Studio»Refresh Project License File, the contents of the .licx file are cleared. Without the proper contents in the .licx file, running your project results in unlicensed exceptions.

Workaround: To refresh the .licx file, select Measurement Studio»View .NET Class Library Wizard. In the Measurement Studio .NET Class Library Wizard dialog box, deselect the Measurement Studio libraries and close the dialog box. Run the Measurement Studio .NET Class Library Wizard again and select the Measurement Studio libraries.

Reported Version: 8.0    Resolved Version: N/A    Added: 11/17/2008
133396

Return
Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly.
As a result, part of the plot is not drawn. Microsoft has confirmed that this is a problem with clipping in the .NET Framework.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133413

Return
The Windows Forms Designer presents an error page stating that parts cannot be found.
If your project references NationalInstruments.UI.WindowsForms, but does not reference the assemblies it depends on, there are circumstances in which the Windows Forms Designer presents an error page stating that parts cannot be found. This occurs when the Windows Forms Designer re-parses its generated code and is unable to resolve references to types that are in the assemblies that NationalInstruments.UI.WindowsForms depends on.

Workaround: To fix this problem, add project references to NationalInstruments.UI and NationalInstruments.Common. Measurement Studio does this for you automatically, so you see this issue only if you disable Measurement Studio integration features in Visual Studio.

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133415

Return
The Analysis library calls the LoadLibrary function.
Under most circumstances, it is unsafe to call LoadLibrary inside DllMain. Therefore, avoid calling any analysis functions inside DllMain.

Workaround: N/A

Reported Version: 8.0    Resolved Version: N/A    Added: 11/17/2008
133416

Return
If you have created a Visual C++ Console Application and are linking statically to MFC, you may encounter LNK2005 and LNK1169 errors.
This problem happens when MFC static libraries and CRT static libraries link in the wrong order. To correct this problem, ensure that the #include <afx.h> statement is the first include statement in the generated stdafx.h header file. For more information, refer to Microsoft Knowledge Base Article 148652.

Workaround: N/A

Reported Version: 7.0    Resolved Version: N/A    Added: 11/17/2008
133421

Return
Measurement Studio Visual C++ controls do not support being hosted in HTML dialogs.
HTML dialogs use the CDHtmlDialog base class.

Workaround: N/A

Reported Version: 6.0 for VC.NET    Resolved Version: N/A    Added: 11/17/2008
133422

Return
The wrappers that Visual C++ generates for the Measurement Studio ActiveX controls are incomplete.
Visual C++ generates wrappers only for the top-level objects in the controls. This causes some Visual C++ generated wrappers to produce compile errors.

Workaround: Refer to National Instruments KnowledgeBase Article 2IECTLXL for more information and suggested workarounds.

Reported Version: 6.0    Resolved Version: N/A    Added: 11/17/2008
133439

Return
Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed.

Workaround: Use the Contents, Index, or Search tabs instead to find the topic.

Reported Version: 8.0    Resolved Version: N/A    Added: 11/17/2008
31271
40A7S0HW


Return
Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value.

Workaround: Put the control inside an UpdatePanel and plot data using the timer tick event

Reported Version: 8.1    Resolved Version: N/A    Added: 11/17/2008
33154
483FFE00


Return
The Parameter Assistant does not always show NI-VISA resources or NI-488.2 boards.
The Parameter Assistant does not show NI-VISA resources or NI-488.2 boards if only Measurement Studio Visual C++ support is installed.

Workaround: Install Measurement Studio .NET language support.

Reported Version: 8.1.1    Resolved Version: N/A    Added: 11/17/2008
96497

Return
Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException.
Calling ShowDialog on a Windows Form that contains a property editor control linked to a Measurement Studio .NET control from a non-UI thread causes an InvalidCastException.

Workaround: Use SetApartmentState() to set the ApartmentState of the thread created to ApartmentState.STA.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 11/17/2008
98865
3ZNCBRAF


Return
If you create a managed Visual C++ project using the Windows Application template, put a Measurement Studio .NET control on the form, and add a setup project to the solution using the primary output of the C++ project, you will receive a missing file error when you build.
This is only an issue for Visual Studio 2005.

Workaround: To work around this issue, do not use the primary output option for the setup project. Instead manually add the .exe and the required .msm files to the project.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 11/17/2008
115770

Return
Measurement Studio UI controls that are part of a custom Web control do not display during design time.
This issue has been fixed with the release of Visual Studio 2008 SP1.

Workaround: Upgrade to Visual Studio 2008 SP1. The controls will display correctly at run time even without SP1.

Reported Version: 8.5    Resolved Version: N/A    Added: 01/05/2009
130937

Return
Dotted lines in ActiveX controls are printed as solid lines in some cases.
GDI draws the dotted lines as solid if the width of the line is greater than 1. While printing a control, a metafile is created which normally involves scaling of the control and consequently scaling of the width of the line. This makes the width of the line greater than 1 and the print will have a solid line instead of a dotted line.

Workaround: There are two workaround options:


  • Set the line width to zero. When the line width is set to zero, the width of the line is 1 on screen and in metafiles.

  • Alternatively, you can create the metafile without scaling. To do this, provide the screen DPI as the parameter to the ControlImageEx method. Then, print without scaling by setting the print area to exactly or less than the size of the control.



Reported Version: 1.0    Resolved Version: N/A    Added: 01/05/2009
33786

Return
Undo does not work for some Measurement Studio .NET properties when edited from the Microsoft Visual Studio Designer.
Microsoft has confirmed that this is a bug in the Designer and will possibly fix the issue in a future update or version.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: N/A    Added: 01/30/2009
151406

Return
Setting the annotation style of a CWGraph to Range or Half Space causes the numbering to disappear for the X and Y axes.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 03/09/2009
156506

Return
The Microsoft C++ Add Variable wizard throws a script error when Internet Explorer 8 is installed.
This is a bug that has been reported to Microsoft.

Workaround: Microsoft has now released a security update that fixes this issue. Information about the security update can be found here.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 04/01/2009
181843

Return
Dropping a Measurement Studio .NET control into a Visual Studio Web application at design time may result in an error.
Dropping a .NET control without adding a reference to NationalIntruments.UI results in an error. Note that the Web.Config file and the license files are updated, but the references in the project file are not.

Workaround: Manually add the reference by selecting the Measurement Studio»Add/Remove .NET Class Libraries menu item in Visual Studio.

Reported Version: 8.5    Resolved Version: N/A    Added: 12/01/2009
182120

Return
Network Variable does not support variables with the Timestamp data type.
If you try to browse to a process that contains a variable with this data type, calls to GetSubItems() fail. As a result, you cannot browse for items in that process.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 12/01/2009
182150

Return
The Visual C++ VectorMatrix streaming example displays errors when the "Save to Binary File" button is pressed.

Workaround: N/A

Reported Version: N/A    Resolved Version: N/A    Added: 12/01/2009
182154

Return
The Visual C++ RegistryExplorer example may cause an access violation exception when trying to delete a registry key.

Workaround: N/A

Reported Version: N/A    Resolved Version: N/A    Added: 12/01/2009
191580

Return
Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 12/01/2009
191880

Return
Matrix operations that utilize the Intel MKL on Windows have slight numerical difference between Measurement Studio 2009 and prior Measurement Studio versions.
Measurement Studio 2009 upgrades to use latest version of the Intel MKL library to accelerate linear algebra operations under the Windows operating system. Some functions in latest Intel MKL library return minor differences in the results than previous version of MKL due to different optimizations. This also results in slight numerical difference between Measurement Studio 2009 and previous versions of Measurement Studio.

This affects Linear Alegbra functions and some Mathematics functions in LabWindows/CVI.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 12/01/2009
222719

Return
Custom division labels may be clipped on the far right side of the x-axis of the intensity graph.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 05/26/2010
211806

Return
Intellisense does not display help for methods containing a 2D array as a parameter for Visual C# projects in Visual Studio 2005.
Measurement Studio methods taking a 2D array as a parameter do not display help for the parameters in the Intellisense for Visual C# projects in Visual Studio 2005.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
216981

Return
Modifying a collection property of a .NET control from the Visual Studio Designer might not always work.
For example if you modify the CustomDivisions collection of a component in the Visual Studio Designer, such as XAxis that is included in a collection, such as Plots, the modifications are not saved.

Workaround: When using the Visual Studio Designer, modify collections only from the component that contains them.

Reported Version: 8.6    Resolved Version: N/A    Added: 12/03/2010
220060

Return
The 64-bit Logos merge module does not contain the commands necessary to install necessary Logos services.

Workaround: If you are creating a 64-bit distribution that requires the Logos merge module, you must also include the 32-bit merge module in your distribution.

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
239529

Return
Autoformatting a .NET waveform, scatter, complex, or intensity graph at design time removes captions from existing annotations.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 12/03/2010
240646

Return
The background of Measurement Studio .NET controls does not remain transparent when the controls are disabled.
When you disable a Measurement Studio control, even with the background color to transparent, the entire area of the control is grayed out when you run your program.

Workaround: Set the form background color to ButtonHighlight. This is the same color as the background color for the disabled control.

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
247775

Return
Measurement Studio .NET controls do not work in the MFC CWinFormsControl control.

Workaround: Host Measurement Studio .NET controls in a .NET UserControl, and then use the UserControl in the CWinFormsControl MFC control.

Reported Version: 2009    Resolved Version: N/A    Added: 12/03/2010
251034

Return
Zoom animation is drawn even when a .NET graph has not been added to a Windows Form.
The following code reproduces this behavior:



WaveformGraph g = new WaveformGraph();

g.XAxes.Add(new XAxis());

g.YAxes.Add(new YAxis());

g.ZoomXY(0, 0, 0.1f, 0.1f);



Workaround: If the graph does not belong to a Windows Form, turn off zoom animation with the ZoomAnimation property before zooming.

Reported Version: 8.5    Resolved Version: N/A    Added: 12/03/2010
251984

Return
Waveform timing information is lost if a network variable with a waveform type is bound to a waveform graph.
The bound data is plotted based on the indices of the values, and not on the timing information associated with the waveform.

Workaround: Explicitly retrieve the data from the network variable using a NetworkVariableReader or NetworkVariableSubscriber.

Reported Version: 8.6.1    Resolved Version: N/A    Added: 12/03/2010
198036

Return
Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese.

Workaround: N/A

Reported Version: 8.5    Resolved Version: N/A    Added: 03/22/2011
286890

Return
The Evaluate Products button on the Measurement Studio Activation dialog box is not localized for non-English operating systems.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 03/22/2011
297181

Return
Building a Measurement Studio ASP.NET Web Forms project fails on computers with United States Federal Information Processing Standard (FIPS) enabled.
This issue only exists in Microsoft Visual Studio 2005 and 2008.

For more information on FIPS, refer to Microsoft KB 811833.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 08/18/2011
301621

Return
The Measurement Studio Help is not uninstalled when Measurement Studio has been uninstalled.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 08/18/2011
308151

Return
If the FillToBase property is set for a plot on a CWGraph, calling ControlImage on the CWGraph can result in a hang.

Workaround: Disable the FillToBase property.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 08/18/2011
309646

Return
When drawing very thick plot lines on a Measurement Studio .NET graph, the line can draw incorrectly.
Visible glitching can occur when the plot lines are thick enough.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/18/2011
291673

Return
Adding a Measurement Studio control to a Web User Control in an ASP.NET Web application project might result in an error.
The reported error states: The control cannot be displayed because its TagPrefix is not registered in this Web Form .

Workaround: Before adding any controls to your ASP.NET Web application project, add references to the NationalInstruments.WebForms assembly. You add references by selecting Measurement Studio»Add/Remove .NET Class Libraries.

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
292392

Return
Calling Filter.Reset can change the characteristics of the filter.
This issue applies to all Filter.Reset methods.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
298877

Return
Adding Measurement Studio .NET 3.5 assemblies to an ASP.NET Web site that targets .NET 4.0 results in incorrect dependencies added to the project.
The .NET 4.0 versions of the assemblies are added, and the .licx file is updated with .NET 4.0 licenses.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 08/19/2011
307898

Return
The Measurement Studio License Status dialog box sometimes displays a button named "Launch Product" instead of "Evaluate Products"

Workaround: Select "Launch Products". The dialog box behavior is the same, regardless of the button text.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 08/19/2011
296833

Return
The Parameter Assistant throws an exception and does not respond when browsing Source URL for NI DataSocket.
The Parameter Assistant does not close after the exception is thrown.

Workaround: Close Visual Studio and reopen it. The Parameter Assistant will open again, but will be functional.

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 02/21/2012
314617

Return
Measurement Studio ActiveX controls cause all controls to not anchor to right side of form.
This only occurs if the applications startup WindowState is set to Maximized.

Workaround: Start the application with the WindowState set to Normal, then programmatically change the WindowsState to Maximized in the Form constructor.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 02/21/2012
332295

Return
The Windows Forms ScatterGraph displays a red "x" when out of memory, but does not throw an exception.
Under rare conditions, an OutOfMemory exception can occur while .NET asynchronously redraws a control.

Workaround: If you call the Graph.ClearData() method, the graph returns to a normal state.

Reported Version: 2009    Resolved Version: N/A    Added: 02/21/2012
337384

Return
Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.

Workaround: N/A

Reported Version: 8.1.2    Resolved Version: N/A    Added: 02/21/2012
338874

Return
If you set the WebForms InteractionMouseCursor property through the designer, the page does not save when using certain controls.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2012
339586

Return
Changing the RangeAdjuster on a WPF Graph does not cause an immediate update.

Workaround: Call the Refresh method of the Graph to force the update to occur.

Reported Version: 2012    Resolved Version: N/A    Added: 07/30/2012
344059

Return
Custom install locations are ignored when National Instruments Merge Modules target is set to the Module Retargetable Folder.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/30/2012
351983

Return
When using an AxisDateTime or AxisPrecisionDateTime axis on a WPF Graph control, FitLoosely has the same behavior as FitExactly.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 07/30/2012
361842

Return
Icons for DataSocket URLs do not display with the DataSocket.SelectUrl popup.

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 07/30/2012
338802

Return
Calling the ClearData method on the Windows Forms DigitalWaveformGraph control a second time on an empty graph causes the horizontal scrollbar to disappear.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 03/01/2013
352017

Return
The RangeLabelDivision.LabelPresenter property of the WPF Graph controls does not accept a single letter for a general formatter value.
A single letter will not display any value. Multiple letters will display correctly.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 03/01/2013
359680

Return
The Snap and SnapPointer InteractionMode of the WPF Knob, Meter, Slider, and Tank controls do not work when the MechanicalAction property is set to SwitchUntilReleased..

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 03/01/2013
365949

Return
Plotting a point that contains infinity for both coordinates in a WPF Graph control will not render accurately.
The lines connecting the point at (infinity, infinity) and neighboring non-infinite points will draw from off screen at the wrong angle. If only one of the coordinates is infinity, then the line will draw correctly.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
366974

Return
The arrow label to an annotation on a WPF Graph control can shrink and disappear depending on the size of the label and its alignment.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
367070

Return
Double-clicking a WPF control in the Visual Studio Design view creates an event handler, but does not switch to the code behind where the event handler was created.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
373005

Return
The WPF IntensityGraph control color marker smart tag editor may become inconsistent with the XAML code.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
373425

Return
Adding an Object type in the "Object Collection Editor: Children" dialog for WPF Graph controls corrupts the Children collection.
The Object type is only available to be selected in Visual Studio 2012 and is an invalid selection.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
382120

Return
Changing axis ranges on CW3DGraph does not cause surface plots to redraw.
If the axis range of a surface plot on a CW3DGraph is updated, the range will redraw, but the surface will not redraw to match the new range.

Workaround: Re-plot the surface each time the scale range is updated.

Reported Version: N/A    Resolved Version: N/A    Added: 03/01/2013
382703

Return
The Instrument Driver Wizard does not remove HTML entities from comments.
The entities are not removed even if the Remove HTML Tags from Comments option is enabled. HTML entities may make the Visual Studio Intellisense not work for these functions.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
383777

Return
The SwitchWhenPressed InteractionMode for the switch and LED Web Forms controls does not work in Internet Explorer 10.

Workaround: Enable compatibility mode in Internet Explorer 10.

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
383780

Return
Web Forms Graph interactions do not work when using Internet Explorer 10.

Workaround: Enable compatibility mode in Internet Explorer 10.

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
383852

Return
Scrolling does not work in the WebForms Legend and DigitalGraph controls when using Internet Explorer 10.

Workaround: Enable compatibility mode in Internet Explorer 10.

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
384492

Return
Repairing Measurement Studio 2013 for Visual Studio 2008 also prompts you to repair Measurement Studio 2012 for Visual Studio 2008.
The installation of Measurement Studio 2013 is not affected by the repair of Measurement Studio 2012.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
385490

Return
The Licenses.licx file is not updated properly when updating a .NET 4.5 ASP.NET project with .NET 4.0 and .NET 4.5 Measurement Studio project references.
If the project has references to both .NET 4.0 and .NET 4.5 Measurement Studio assemblies, then an error with the NationalInstruments.UI.Styles3D.msl file will be reported.

Workaround: Remove the NationalInstrumetns.UI.Styles3D assembly from the project references and remove the duplicate entry for NationalInstruments.UI.dll from the web.config file.

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
386176

Return
The Name property is not added for WPF controls added from the Toolbox in Visual Studio 2012.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
389778

Return
Invalid property values input in the Property Editor or the Smart Tag editor for WPF controls may be inserted into XAML for some properties.
The invalid values cause an error in the XAML.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
389801

Return
Changing a WPF Numeric control's data type may restore the Grid.Row property to zero.
In Visual Studio 2012, if a WPF Numeric control is in a row other than the zero row (e.g., into Grid.Row=%quot;1" of a grid with two or more rows), and the control's data type is changed through the context menu, then the control will be moved to the zero row. This issue does not occur in Visual Studio 2010.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 03/01/2013
501674

Return
An older Global Assembly Cache (GAC) assembly is removed when installing a newer version of the assembly to the GAC with an installer built with Installer Builder.
Installing an upgraded assembly to the GAC should result in multiple versions of the assembly existing in the GAC simultaneously. GAC assemblies should not be removed on upgrade.

Workaround: N/A

Reported Version: 14.5    Resolved Version: N/A    Added: 12/03/2014
502114

Return
The description URL does not appear on install for digitally signed installers built with Installer Builder.

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 12/03/2014
508665

Return
The Include Recommended Installers Only option on the NI Driver & Components tab does not do anything.

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 12/03/2014
401356

Return
An Exception has been thrown by the target of an invocation error occurs at System.RuntimeTypeHandle.CreateInstance when Measurement Studio WPF controls are used in a Prism framework view.

Workaround: Use a View Injection pattern to create the view. This may look like the following:

GraphView myGraphView = new GraphView();
m_regionManager.Regions["GraphRegion"].Add(myGraphView, "TheGraphView");


Reported Version: 2012    Resolved Version: N/A    Added: 08/17/2015
434140

Return
The Convolve2D method in the Analysis DSP library throws an AccessViolationException when called on a large matrix with millions of elements or when called repeatedly on smaller matrices.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
449638

Return
NationalInstruments.Analysis.Dsp.Filters.IirFilterBase does not have a method for calculating forward and reverse filter coefficients.
The Measurement Studio Enterprise Analysis library does not provide a way to obtain transfer function coefficients for the IIR filters.

Workaround: Utilize functions provided by other NI tools such as the LabWindows™/CVI™ Advanced Analysis Library to perform filtering and obtain coefficients.

Reported Version: 2010    Resolved Version: N/A    Added: 08/17/2015
461933

Return
The Refresh Project License File feature deletes all entries of the .licx file without a prompt, if the project contains invalid National Instruments references.
Projects may have invalid references if the references are no longer on the development system. This might happen if the project was originally built with an early version of Measurement Studio but was then upgraded to a later version.

Workaround: Remove old National Instruments references from the project, and add references corresponding to the new version of Measurement Studio.

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
485392

Return
Enum properties do not appear as changed in the Property Dialog Editor when launched from a Collection Editor dialog in Visual Studio 2012 and 2013.
For example, if you create a new axis in the Axes collection editor and try to change the Adjuster property, the property does not change. However, once you close the collection editor, the change you made will reflect in the XAML.

Workaround: You may also change the properties using the property grid for the specific collection element you would like to edit, outside the collection editor.

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
499316

Return
Some localized Windows operating systems may cause a compile time licensing failure with the error message LC.exe - Assert Failure.
The error has been known to occur with German and Swedish localized Windows operating systems, but could occur with other locales as well. The error occurs when the Measurement Studio project is compiled.

Workaround: Recompile the project. The error only occurs on the first compile after opening Microsoft Visual Studio, so subsequent compiles should complete successfully.

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
513981

Return
Calling Cursor.Move or Cursor.MoveNext does not always result in the cursor index increasing by the correct amount in ASP.NET applications.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
518031

Return
On certain localized Windows operating systems, Measurement Studio licensing fails at compile time with an LC.exe - Assert Failure message.

Workaround: Rebuild the solution after modifying the UI.

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
521828

Return
Vertical axis gridlines disappear when rendering only digital data in a WPF mixed signal graph.

Workaround: Explicitly add a vertical axis to MixedGraph.Axes.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
523024

Return
The ASP.NET Update Project References feature does not add references to dependent assemblies.
For example, if a project has a reference to NationalInstruments.UI.WebForms, but not an explicit reference to NationalInstruments.Common, the Update Project References feature does not add NationalInstruments.Common to the project.

Workaround: Manually add the dependent assemblies.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
525863

Return
The Company Name field on Measurement Studio»About Measurement Studio is displayed as ????????? on a Japanese OS.

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
526156

Return
Japanese characters in the YAxis Caption of a Windows Forms graph display upsidedown.

Workaround: Set the LeftCaptionOrientation setting to TopToBottom, which will arrange multibyte characters in a top-to bottom order. This will cause any non-multibyte characters to be rotated 90 degrees clockwise.

Reported Version: 2013    Resolved Version: N/A    Added: 08/17/2015
529944

Return
A field validation error occurs when you set the Output Directory on the Basic Options tab to a non-existent network path.
The error message indicates that the path cannot be empty.

Workaround: Create an empty folder at the network destination before setting the network path.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
529950

Return
An Error: An internal tool or library returned an error. message displays when Installer Builder initializes the build log for the first time.
There is no error on subsequent builds.

Workaround: N/A

Reported Version: 15.0    Resolved Version: N/A    Added: 08/17/2015
529958

Return
Adding a merge module that is open in an editor (e.g., Orca) results in unexpected behavior.
No errors appear in Installer Builder or the build output.

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
534324

Return
Registry keys imported by Installer Builder are not saved properly to the .iip project file.
If you import a .reg file on the Registry Keys tab of Installer Builder and save your project, the registry keys and values you imported are not available when you subsequently close and reopen your project.

Workaround: Manually create registry keys and values instead of importing them.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
534325

Return
Registry keys imported by Installer Builder are not properly built into the installer.
If you import a .reg file on the Registry Keys tab of Installer Builder and save your project, the registry keys and values you imported are not built into the installer that is created when you click the Build button.

Workaround: Manually create registry keys and values instead of importing them.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
534441

Return
(Default) registry key values do not appear in the value field on the Registry tab of Installer Builder after opening a project which contains values for (Default) registry keys.
While the (Default) values do not display in the Registry tab, the values are set and appear in the final MSI created by Installer Builder.

Workaround: Check the .iip project file to verify that the (Default) keys contain values.

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
534442

Return
Importing registry keys from a .reg file can result in multiple, duplicate copies of the registry keys in the Registry tab.

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
534443

Return
Opening a project containing imported registry keys for the SOFTWARE hive results in both a SOFTWARE key and another Software key of a different capitalization

Workaround: N/A

Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015
537212

Return
Setting the XPosition property of an XYCursor (SnapMode: ToPlot) set to a specific value fails in large sets of x data.

Workaround: Instead of relying on the XPosition property, you can write code using MoveCursor similar to the following:

// xValue is the x value in data coordinates.
var xData = scatterPlot.GetXData( );
int i = Array.FindIndex( xData, val => val == xValue );

// A value of -1 indicates the xValue was not found in xData.
if ( i != -1 )
xyCursor.MoveCursor( i );


Reported Version: 2015    Resolved Version: N/A    Added: 08/17/2015

Return to the Measurement Studio Release Notes, Known Issues, and Bug Fix Information document.

Document last updated on 8/17/2015

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