NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
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.
This document contains the Measurement Studio 2013 known issues that were discovered before and since the release of Measurement Studio 2013. 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 known issue includes these fields:
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The known issues in this document are organized by the category of issue, and sorted by the date the issue was added to the document. To view the issues organized by date, visit the document linked below:
Known Issues by Date
You can contact us through any of the normal support channels including phone, email, or the discussion forums. 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.
The following items are known issues in Measurement Studio 2013 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Analysis | ||||||
| 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
| |||||
| 176144 Return | 32-bit analysis and 64-bit analysis library results can have slight numerical differences Workaround: N/A
| |||||
| 292392 Return | Calling Filter.Reset can change the characteristics of the filter.This issue applies to all Filter.Reset methods.Workaround: N/A
| |||||
| DataSocket | ||||||
| 361842 Return | Icons for DataSocket URLs do not display with the DataSocket.SelectUrl popup. Workaround: N/A
| |||||
| Deploying Applications | ||||||
| 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.
| |||||
| 191580 Return | Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries. Workaround: N/A
| |||||
| 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.
| |||||
| 344059 Return | Custom install locations are ignored when National Instruments Merge Modules target is set to the Module Retargetable Folder. Workaround: N/A
| |||||
| Hardware Libraries | ||||||
| 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.
| |||||
| 199947 Return | Significant decrease in performance occurs when using NI-488.2 for Microsoft Windows and LabVIEW Real-Time You might experience significant loss of GPIB performance after installing or updating NI software on systems using PCI, PCI Express, PMC, or PXI GPIB interface types or built-in interfaces on PXI and VXI controllers. All other GPIB interfaces are not affected. Refer to KnowledgeBase 54EF93G2 for more information about this issue. Workaround: Refer to KnowledgeBase 54EF93G2 for more information about this issue.
| |||||
| Installer | ||||||
| 301621 Return | The Measurement Studio Help is not uninstalled when Measurement Studio has been uninstalled. Workaround: N/A
| |||||
| Licensing | ||||||
| 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.
| |||||
| 286890 Return | The Evaluate Products button on the Measurement Studio Activation dialog box is not localized for non-English operating systems. Workaround: N/A
| |||||
| Network Variable | ||||||
| 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.
| |||||
| 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.
| |||||
| 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:
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.
| |||||
| 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
| |||||
| 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.
| |||||
| Product Documentation | ||||||
| 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
| |||||
| 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.
| |||||
| TDMS | ||||||
| 376216 Return | "Read from file failed" or "Write to file failed" error occurs when reading or writing very large amounts of data from a TDMS file. Reading a very large file that was written by a Measurement Studio application will report that the file has 0 elements even though the file size is correct and the data is contained within. Testing has determined that approximately 1 GB of data (or 150 million samples of type double) will cause this issue, but the specific amount of data is dependent on the amount of available memory on the system. This issue only occurs in applications built with Visual Studio 2010 or Visual Studio 2012. This issue will also occur with files written by a LabWindows/CVI or LabVIEW application, but the correct number of samples read will be reported. However, reading the LabWindows/CVI or LabVIEW written file will still report a "Read from file failed" error.Workaround: Set the TdmsFileOptions.BufferingDisabled property to false when both writing and reading a large TDMS file.
| |||||
| User Interface | ||||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 222719 Return | Custom division labels may be clipped on the far right side of the x-axis of the intensity graph. Workaround: N/A
| |||||
| 239529 Return | Autoformatting a .NET waveform, scatter, complex, or intensity graph at design time removes captions from existing annotations. Workaround: N/A
| |||||
| 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.
| |||||
| 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: Workaround: If the graph does not belong to a Windows Form, turn off zoom animation with the ZoomAnimation property before zooming.
| |||||
| 198036 Return | Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese. Workaround: N/A
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 337384 Return | Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.Workaround: N/A
| |||||
| 338874 Return | If you set the WebForms InteractionMouseCursor property through the designer, the page does not save when using certain controls.Workaround: N/A
| |||||
| 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.
| |||||
| 343435 Return | If the WPF Graph does not contain data, the zoom operation on the WPF Graph does nothing. This is true for both interactive and programmatic zooming. Workaround: N/A
| |||||
| 345820 Return | The WPF Meter control pointer base may be clipped under certain layout scenarios. Depending on the size of the control and its location in the layout, the round base of the Meter pointer may appear cut off along the bottom edge. Workaround: N/A
| |||||
| 349762 Return | The Windows Forms NumericEdit control does not initialize to a NaN value. Workaround: Set the value of the NumericEdit control to double.NaN after the InitializeComponents method is called.
| |||||
| 350960 Return | ScaleArc properties on WPF gauge and meter controls throw an exception when the default value is modified at run time. Workaround: Set the ScaleArc property of the control to a new ScaleArc object.
| |||||
| 351145 Return | You cannot interact with annotations on a WPF Graph that fall behind a plot that uses an AreaPlotRenderer.This behavior occurs even if the Graph fill is set to Transparent.Workaround: N/A
| |||||
| 351983 Return | When using an AxisDateTime or AxisPrecisionDateTime axis on a WPF Graph control, FitLoosely has the same behavior as FitExactly.Workaround: N/A
| |||||
| 358289 Return | Range annotations compress when dragged outside the range of the WPF Graph. Workaround: N/A
| |||||
| 391307 Return | Changing the WPF Graph Annotation.InteractionMode from DragTarget at run time does not update the interaction mode of the Annotation.If the InteractionMode is initially set to DragLabel or None, then the interaction mode can be updated.Workaround: Set the new value of the InteractionMode property, then remove and re-add the annotation from the Graph control. annotation.InteractionMode = AnnotationInteractionModes.None; graph.Children.Remove( annotation ); graph.Children.Add( annotation );
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 359825 Return | The pointer on a WPF Slider control is cut off if the Slider is too small. Workaround: N/A
| |||||
| 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
| |||||
| 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
| |||||
| 366976 Return | A WPF Graph control RangeAnnotation appears to end at the edge of the visible plot region when its range is partially visible.Workaround: N/A
| |||||
| 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
| |||||
| 369189 Return | When completing a zoom horizontal or zoom vertical interaction on a WPF Graph control, the axis scale adjuster does not run. For example, if the the vertical axis has a FitVisibleExactly adjuster set and the user zooms horizontally, then the graph will zoom to the correct horizontal range, but the vertical axis will not readjust to fit the visible data exactly.Workaround: N/A
| |||||
| 371457 Return | A System.TypeLoadException is thrown when the WPF Graph control's DataSource property is assigned an unknown type.The set of types supported by the Graph control is extensible. When a data type is encountered for the first time, the Graph control performs a search to determine the best descriptor to use. To determine if the type can be supported, the Graph control constructs the type, but this may generate a System.TypeLoadException. The exception is handled by the control and is does not reach the user code. The type search result is cached so that an exception is not thrown each time.Workaround: Disable the System.TypeLoadExpection Thrown option in the Visual Studio Exceptions dialog.
| |||||
| 373005 Return | The WPF IntensityGraph control color marker smart tag editor may become inconsistent with the XAML code. Workaround: N/A
| |||||
| 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
| |||||
| 377450 Return | If you have a model assigned to the DataContext of a WPF Graph, and you try to bind a property on the model to a property on an Axis in the Graph, the binding will fail.Workaround: Use a StaticResource for the Source of the Range Binding.
| |||||
| 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.
| |||||
| 383780 Return | Web Forms Graph interactions do not work when using Internet Explorer 10. Workaround: Enable compatibility mode in Internet Explorer 10.
| |||||
| 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.
| |||||
| 386176 Return | The Name property is not added for WPF controls added from the Toolbox in Visual Studio 2012.Workaround: N/A
| |||||
| 386303 Return | WPF Graph cursor label may disappear if the value is also visible. This will happen if the cursor is moved to the right half of the Graph control. Workaround: N/A
| |||||
| 389773 Return | If the CoercionMode property of a WPF Numeric control is set to ToDivisions then the initial value will always be zero.During control initialization, the coercion of the control's value occurs before the divisions are set. This causes the value to be coerced to zero even if a non-zero value is set for the Value property.Workaround: Set the CoercionMode property after the Loaded event has occurred.
| |||||
| 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
| |||||
| 389799 Return | A WPF Tank control may show fewer divisions on one side than the other depending on its size. If the control's ScaleLocation property is set to NearAndFar, then the number of divisions on one scale may be different than the other scale when RangeLabelDivisions.Mode is set to Auto.Workaround: N/A
| |||||
| 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
| |||||
| 390494 Return | The WPF Graph control causes an application to hang if the AxisDivisions require more than 15 digits of precision.If an Axis contains a WPF Graph control that is configured to use auto-generated divisions on the axis and uses a Range where intermediate divisions require more than 15 digits of precision, the application will hang.Workaround: Do not set the RangeLabeledDivisions.Mode property to Auto.
| |||||
| Visual Studio Integration | ||||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
Document last updated on 3/14/2013