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 8.6.x known issues that were discovered before and since the release of Measurement Studio 8.6. 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 date they were added to this document. To view the issues organized by category, visit the document linked below:
Known Issues by Category
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.
The following items are known issues in Measurement Studio 8.6.x sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 104534 Return | The Instrument Driver Wizard sometimes creates constants with the same name. The Instrument Driver Wizard creates constants with the same name if the constants in the instrument driver are different only by the sign of the power in scientific notation. Workaround: N/A
| |||||
| 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.
| |||||
| 117112 Return | An extraneous horizontal or vertical white patch sometimes appears in a .NET control with a width or height greater than 474 pixels when the control is using the ThickFrame3D or ThinFrame3D borders. The extraneous horizontal or vertical white patch appears in the .NET control if the size of the control is greater than 474 pixels in either width or height and the control is using either the ThickFrame3D or ThinFrame3D border. Workaround: Choose a non-3D style for large controls.
| |||||
| 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
| |||||
| 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
| |||||
| 125622 Return | The Instrument Driver Wizard generates an invalid class name when the input file name contains characters that are not valid in a class name. Workaround: Ensure that the instrument driver file name is a valid class name.
| |||||
| 127686 Return | Writing a single value to the same TDMS File channel group property, then writing to two different channels, and then saving the file in between a write to two channels can corrupt the channel group property. If you set the same TDMS channel group property to the same value in between writes to two or more channels and save, the data written is corrupted. Workaround: Do not write the same value to the same property twice.
| |||||
| 127687 Return | Setting a TDMS file property multiple times with different data types might corrupt the property. If you set the same TDMS file property more than once with different data types without saving between calls to SetFileProperty, the property becomes corrupted.Workaround: Save the file between calls to SetFileProperty.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 133414 Return | You cannot use Measurement Studio class libraries in 64-bit applications. Workaround: Use Measurement Studio class libraries in 32-bit applications and run those applications on 64-bit Vista, provided that all drivers you use in the applications support 64-bit Vista.
| |||||
| 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.
| |||||
| 136849 Return | The PropertyChanged event for NetworkVariableBufferedSubscriber is not raised for the ItemCount property. The NetworkVariableBufferedSubscriber.PropertyChanged event is not raised when the ItemCount property changes due to a new data item arriving or an item being removed from the buffer. This means there is no notification when new items arrive in the buffer. Workaround: Either use a timer to periodically poll the ItemCount property or use NetworkVariableSubscriber and maintain your own buffer for the data items.
| |||||
| 31074 489EEQ03 Return | Dropping a Measurement Studio control onto the Design vew of an ASP.NET Web site might result in an error. Under some circumstances, dropping a Measurement Studio control onto the Design view of an ASP.NET Web site results in an error. Workaround: If the error occurs, close and then re-open the page in Design view. This issue is fixed in Visual Studio 2010.
| |||||
| 31110 4CEFFD26 Return | The Instrument Driver Wizard does not properly handle .fp files that do not contain a prefix entry within the file. When calling an instrument driver, the Measurement Studio Instrument Driver Wizard will display a value==String.Empty message if the file has no prefix. This prefix is usually based on a company's IVI and VXI plug&play drivers.Workaround: Modify the instrument driver file ( .fp) to include a prefix.
| |||||
| 31138 435E06I0 Return | Calling DoEvents in a NumericEdit control callback may cause an exception. When using the NumericEdit control, if a call is made to DoEvents inside either the ValueChange event or the AfterValueChangeEvent and the button is pressed rapidly, the control throws an exception. This error can also occur if the event handlers take a while to return. Microsoft has confirmed that this is a problem with the NumericUpDown control in the .NET Framework.Workaround: N/A
| |||||
| 31142 42GE5NZ7 Return | F1 does not launch the correct help for Measurement Studio Web Forms Controls In .aspx pages that include Measurement Studio Web Forms controls, pressing F1 help for inherited members of the Measurement Studio ASP.NET Web Forms controls does not launch the correct help.Workaround: Use the help Search, Index, or Table of Contents for help about Measurement Studio ASP.NET Web Forms controls.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 129222 Return | Using Measurement Studio controls in a Visual Basic .NET application with an '&' in the project path name causes errors. Microsoft has confirmed that this is a bug in Visual Studio, which has reportedly been fixed for the next release of Visual Studio. Workaround: Remove the '&' from the path name.
| |||||
| 117515 Return | Nianlys.dll may throw a System.AccessViolationException on a computer with DEP enabled. Workaround: Currently, disabling DEP is the only workaround for this issue. To disable DEP, complete the following steps:
nx parameter of the BCDEdit /set command. Caution The AlwaysOff option disables DEP on all processes running on the machine. Disabling DEP can make your system more vulnerable to malicious software.
| |||||
| 128046 Return | .NET graph control axis labels do not redraw when you change the custom FormatString while using a custom FormatString for the axis LabelFormat. Measurement Studio FormatString objects are assumed to return the same string for a given input value. In some cases, Measurement Studio controls minimize access to FormatString objects during the paint cycle, based on this assumption. Consequently, when a FormatString object returns a different string for a given value, the control that utilizes the FormatString object might not reflect the change when the control redraws. Workaround: To update an axis label that is using a custom FormatString, create a new instance of the custom FormatString object that is assigned to that label, and then assign this new instance to the LabelFormat property.
| |||||
| 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
| |||||
| 31091 3VFEGE9Q Return | The Instrument Driver Wizard does not support functions with parameters that are 64-bit integers or 64-bit integer arrays. Workaround: N/A
| |||||
| 134950 Return | The Instrument Driver Wizard does not publicly expose the instrument C session handle. The Instrument Driver Wizard now generates a public property that returns the instrument C session handle. This handle can be passed to other API wrappers or P/Invoke calls. Workaround: N/A
| |||||
| 140280 Return | The Visual Basic .NET documentation generated by the Instrument Driver Wizard does not conform to Microsoft Help Standards. The comments that are generated use five apostrophes instead of three Workaround: N/A
| |||||
| 132246 Return | If you bind multiple .NET control string properties to a single string network variable, updating a different network variable sets the bound string properties to String.Empty. Workaround: Ensure only one string variable for each string control
| |||||
| 119291 Return | It is not possible to determine whether an axis range was changed programmatically or interactively for .NET graphs. In the AxisRangeChangedEvent event handlers, we do not specify how the event was raised. Workaround: N/A
| |||||
| 140923 Return | Changing the axis range on a WaveformGraph, ScatterGraph, or ComplexGraph with few points causes skewed plot lines. Due to rounding errors, as points move further off screen, the plot lines become less accurate. Workaround: Provide more points for your plot, or constrain the range of the graph in question.
| |||||
| 127011 Return | Under some circumstances, range division label values for .NET controls are formatted incorrectly. This incorrect formatting is cause by internal rounding errors, leading to range division label values that are formatted incorrectly. For example, the label may read 9.500000000000001 instead of 9.5. Workaround: N/A
| |||||
| 134441 Return | Installing LabWindows/CVI and Measurement Studio and then uninstalling Measurement Studio can also uninstall shared merge modules, such as CW3DGraph_OCX.msm. This issue can cause the uninstallation of merge modules shared between Measurement Studio and LabWindows/CVI, including CW3DGraph_OCX.msm, CWUI_OCX.msm, NIMesaDLL.msm, GLU32.msm, OpenGL32.msm, and niMetaUtils.msm.Workaround: N/A
| |||||
| 132782 Return | A .NET cursor with SnapMode configured to NearestPoint mode will snap to the nearest point on any plot in a .NET graph, even if the point's plot is not visible. Workaround: Cancel the event if the cursor is about to snap to an invisible plot in the BeforeMoveCursor event by using the BeforeMoveXYCursorEventArgs parameter as follows: if (!e.Plot.Visible) { e.Cancel = true; }
| |||||
| 133866 Return | The Nework Variable .NET class library does not provide a way to include a description in the variable attribute for a Network Variable. Workaround: You can set the description through Distributed System Manager or Variable Manager.
| |||||
| 138493 Return | Range.Parse(String, IFormatProvider, CultureInfo) throws a runtime exception if the culture parameter is not set to CurrentCulture. Workaround:
The following is an example of this operation:
| |||||
| 138506 Return | Arc.Parse() cannot parse the string returned by Arc.ToString(). Workaround: Manually extract the start angle and sweep parameters from ToString() and pass these to Arc.Parse().
| |||||
| 146529 Return | Assigning the XPosition of a cursor to a point with value of NaN puts the cursor in a bad state. Workaround: Use sampleWaveformGraph.Cursors[0].MoveCursor(x); instead of sampleWaveformGraph.Cursors[0].XPosition = x;
| |||||
| 154564 Return | Sometimes the Measurement Studio ASP.NET Web Forms controls throw an InvalidOperationException in IIS.Sometimes the Measurement Studio ASP.NET Web Forms controls throw an InvalidOperationException in IIS. If you access the page from more than one place, and particularly if you refresh the page very quickly, you may see this InvalidOperationException.Workaround: N/A
| |||||
| 157881 Return | Calling PlotY multiple times on a .NET graph with a cursor can cause the cursor to move along the x-axis. Workaround: Get the position of the cursor prior to plotting, then set the cursor to this position after plotting.
| |||||
| 158854 Return | Installing Measurement Studio and TestStand 4.2 on a machine with Visual Studio 2008 can cause help topics to disappear. If you install TestStand 4.2 first and then Measurement Studio, the TestStand 4.2 help will be removed from the Visual Studio Table of Contents. If you install Measurement Studio first, and then TestStand 4.2, the Measurement Studio help will be removed from the Visual Studio Table of Contents. Workaround: You must remerge the help to fix this. To remerge the help do the following:
| |||||
| 154249 Return | The encryption algorithm used for Measureant.ment Studio .NET class libraries licensing is not Federal Information Processing Standard (FIPS) compli The encryption algorithm used for Measurement Studio .NET licensing is not FIPS compliant. This leads to design time and build time exceptions when using Measurement Studio .NET libraries on a FIPS compliant machine. See this Microsoft KB for more information. Workaround: This issue has been fixed in Measurement Studio version 8.6.1. If you are unable to upgrade and need to be FIPS compliant, please contact National Instruments Support.
| |||||
| 164969 Return | Rounding errors can occur when viewing formatted DateTime values in a Measurement Studio .NET waveform graph. Workaround: N/A
| |||||
| 168826 Return | Japanese characters may appear upside down when the caption orientation is set to Left for Tank and Meter .NET control labels. Workaround: N/A
| |||||
| 178633 Return | The maximum history capacity allowed can be inconsistent for .NET waveform graphs. When setting very large history capacity values, Measurement Studio inconsistently throws Out Of Memory Exceptions. For example, a value of 14,000,000 may be accepted, whereas 13,999,999 may not be. Workaround: N/A
| |||||
| 181879 Return | TdmsChannel.GetData<T>() throws an out of memory exception when the data being accessed is larger than 2 GBs. Instead of returning the largest array possible, TdmsChannel.GetData<T>() throws an Out of Memory exception if the channel is large enough that creating an array of its elements would exceed the .NET object size limit of two GBs.Workaround: N/A
| |||||
| 182240 Return | The Instrument Driver Wizard does not work with function panel (.fp) file formats version 9.0 and later. Workaround: N/A
| |||||
| 182699 Return | .NET graphs with multiple plots behave incorrectly, in the Visual Studio designer, when Visible is set to False for one of the plots. If you add multiple plots to a waveform graph, scatter graph, or complex graph, and then modify the visible property of one of the plots in the Visual Studio designer, the graphs will render incorrectly in the Visual Studio designer. The waveform graph and the complex graph will display X and Y ranges with very large values. The complex graph will throw an exception, and fail to render in the designer. Workaround: N/A
| |||||
| 194621 Return | If a graph includes multiple axes, ZoomXY may not zoom accurately.If a graph has multiple X or Y axes, the overload ZoomXY(referencePlot, xData, yData, width, height) will zoom accurately for the axes associated with the plot that are referenced in the first parameter. However, the axes not associated with the given plot do not zoom accurately.Workaround: N/A
| |||||
| 195429 Return | If you have the "Automatically Update ASP.NET Project" option set to false in Visual Studio 2008, the project is updated. Select Tools»Options»Measurement Studio to view this option. Workaround: N/A
| |||||
| 197171 Return | Using SingleToneInformation.GetDetectedSignal may result in results that are 180 degrees out of phase. Workaround: N/A
| |||||
| 133799 Return | A .NET NetworkVariableDataSource binding does not update its value on connection. Workaround: Call SetValue on the NetworkVariableDataSource binding when each connection occurs.
| |||||
| 158863 Return | Pressing <Enter> when editing the value in the Edit Range text box of a .NET waveform graph at runtime causes a system beep. Workaround: N/A
| |||||
| 168274 Return | Reading and writing data within the same loop using TDMS results in a significant performance decrease. Workaround: Read and write data in separate loops.
| |||||
| 177256 Return | Measurement Studio ASP.NET Web sites do not work by default in IIS7 integrated mode. In the web.config file, IIS6 expects the module and handler definition to be in <system.web>/<httpModules> and <system.web>/<httpHandlers>, whereas IIS7 expects the module and handler definition to be in <system.webServer>/<modules> and <system.webServer>/<handlers>.Workaround: Modify the web.config file to contain the following information: <system.webServer>
| |||||
| 177703 Return | Links from the Measurement Studio stand-alone help viewer to the Visual Studio Help Collection are broken. Use the Visual Studio Combined Help Collection to view the NI Measurement Studio Help Collection. Access this help by selecting Help»Contents from within Visual Studio. Workaround: N/A
| |||||
| 178108 Return | .NET cursors do not snap to plots when SnapMode is Nearest Point and the associated plot has no data. Workaround: Ensure the associated plot contains data.
| |||||
| 180034 Return | The DateTimeKind property of PrecisionDateTime objects is not preserved by the + and - operators. Workaround: N/A
| |||||
| 181121 Return | NetworkVariableBrowserDialog does not handle variables of type TimeStamp. If the dialog is used during design time in Visual Studio, such as when browsing to a variable for a NetworkVariableDataSource, Visual Studio will crash if a process containing a variable of type TimeStamp is expanded. The same operation will result in a "Data Type is not valid" exception at run-time. 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.
| |||||
| 181874 Return | The Datasocket "Select URL" dialog may crash Visual Studio when using Windows Vista. The dialog that appears when you click the "Select URL" option for the Datasocket control may crash Visual Studio. Workaround: N/A
| |||||
| 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
| |||||
| 184825 Return | Zoom and pan operations may not revert correctly when preceded by an EditRange operation if you use more than one x-axis or y-axis. If you are using more than one x-axis or y-axis, and you edit the range of an axis before zooming or panning, reverting the zoom or pan operation will not work correctly. Workaround: N/A
| |||||
| 191580 Return | Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries. Workaround: N/A
| |||||
| 193763 Return | Visual Studio Setup Projects for DataSocket applications do not automatically add the logos.msm merge module.Workaround: Manually add the merge module from c:\Program Files\Common Files\Merge Modules.
| |||||
| 193809 Return | If you deploy a network variable application to a machine that acts as the variable server, the application may crash until the computer is rebooted If you install your application after the NINETVARSERV redist installer, your application installer will stop the Shared Variable Engine service. If this service is not running, applications that use network variable may crash. Workaround: There are two workarounds for this issue:
| |||||
| 196747 Return | Using a single network variable writer from multiple threads may result in a hang in your application. Workaround: Place a lock around each network variable write call.
| |||||
| 226968 Return | Visual Studio Setup Projects for DataSocket applications do not automatically add the ni_utility.msm merge module.Workaround: Manually add the merge module from c:\Program Files\Common Files\Merge Modules. NOTE: On a 64-bit operating system, manually add the merge module from c:\Program Files (x86)\Common Files\Merge Modules.
| |||||
| 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.
| |||||
| 190486 Return | If you call Graph.ToImage(Size), the DrawGridLines method incorrectly draws the graph axes. If the destination size is not the same as the graph image size, the axes do not scale correctly. Workaround: Use the overload of ToImage that does not take any parameters. This overload creates an image the same size as the graph. You can scale this image to your required size. However, rescaling the image can cause pixelation.
| |||||
| 215669 Return | Measurement Studio adds National Instruments references to the web.config file of non-Measurement Studio projects. Workaround: Complete either of the following workarounds to fix this issue:
| |||||
| 180681 Return | A memory leak exists in WebForms.NetworkVariableDataSource when Dispose is not called before the host page is unloaded.The internal implementation of WebForms.NetworkVariableDataSource requires that Dispose be called to clean up internal resources which manage the low-level connections to network variables. This issue does not occur in the typical case, where the data source is hosted on a Web Form because the form calls Dispose on its children. This issue can occur if the program dynamically creates data sources and/or attempts to cache data sources across post backs (e.g., in session state).Workaround: If you dynamically create data source controls, call Dispose on them before the post back completes. This can be done, for example, in the Page_Unload event of the page that contains the controls that the data source binds to. Do not cache instances of NetworkVariableDataSource across post back.
| |||||
| 208239 Return | ClipDataPoints returns an extra point when used on a WavefromPlot.ClipDataPoints returns all the visible points, plus the point that falls just to the right and the point that falls just to the left of the clipping bounds. This enables lines to be drawn into and out of the plot area. However, it also returns one additional point that also lies outside the clipping bounds and is not needed for drawing to the plot area.Workaround: N/A
| |||||
| 208242 Return | The ClipDataPoints method does not work for ScatterPlot objects.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.
| |||||
| 217352 Return | Updating the InteractionModeDefault of any .NET graph while the mouse is over the graph will not update the mouse cursor.The cursor will not update until the mouse moves off and then back onto the graph. Workaround: Manually setting the Cursor property updates the cursor, but you must restore the cursor when the mouse leaves the graph for the first time.
| |||||
| 221889 Return | If a Measurement Studio assistant runs while Measurement and Automation Explorer (MAX) is open, creating future Visual Studio projects will fail, but only if this is the first time you are creating a Visual Studio project. Workaround: Close MAX and restart Visual Studio.
| |||||
| 222183 Return | The animation rectangle shown when zooming on a graph moves very slowly if many points are plotted. Because the number of points affects how quickly the graph area can be redrawn, the larger the number of points, the slower the zoom rectangle moves. Workaround: N/A
| |||||
| 222524 Return | The y-axis will accomodate the text length of a custom division label even if the custom division is not visible. If you create a custom division on the y-axis with a label long enough to cause the y-axis width to grow, the axis does not return to its normal size if the custom division is not visible. Workaround: N/A
| |||||
| 222712 Return | The edit range entry box does not honor axis label formats for some formats. When interactively editing an axis range by clicking on one of the range labels, the format mode of the axis labels is not honored for some formats in the entry box that displays. Workaround: N/A
| |||||
| 235353 Return | Zooming a .NET waveform graph multiple times with minor gridlines or visible ticks can result in a hang. Workaround: Do not enable the grid or ticks for the MinorDivisions of a .NET graph.
| |||||
| 235390 Return | Boolean controls do not correctly handle the Escape key. For example, when an LED or Switch has an interaction mode of SwitchWhenReleased, you cannot press Escape to cancel the change.Workaround: N/A
| |||||
| 235391 Return | Measurement Studio .NET boolean controls do not correctly handle loss of application focus. You can see this behavior if the following steps occur:
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
| |||||
| 240792 Return | Setting the DefaultReadValue of a NetworkVariableBinding object to null results in a NullReferenceException.Workaround: N/A
| |||||
| 244273 Return | A project using Measurement Studio mixed mode assemblies built against .NET Frameworks prior to .NET Framework 4 cannot run against .NET Framework 4. If you build a Measurement Studio project that references a Measurement Studio mixed mode assembly, such as NationalInstruments.Common.Native in Visual Studio 2005 or 2008, and try to run the project on a machine that has only .NET Framework 4, the project will not run, even when using an app.config file to force it to use .NET Framework 4. The project fails to load the mixed mode assembly. Workaround: Install the version of the .NET Framework that the application was built against, along with .NET Framework 4.
| |||||
| 247826 Return | The TDMS .NET API leaks memory when creating or reading channels or channel groups. Each time a channel or channel group is requested from the TDMS .NET API, multiple unmanaged handles may be created that are never closed. This can lead to a significant memory leak. Workaround: Query channels and channel groups only once and cache the results. Do not look up channels and channel groups by name, as this causes a bigger leak than by looking up channels and channel groups by index.
| |||||
| 249777 Return | Some ranges can result in incorrect ticking on graph axes with a logarithmic scale. Ranges such as (1e-15, 1-13), (1e-13, 1e-11), or (1e-33, 1e-31) can cause internal rounding errors that lead to incorrect ticking on graph axes. Workaround: N/A
| |||||
| 249802 Return | Waveform, scatter, complex and intensity graph cursor positions cannot be set before the cursor is added to a cursor collection if SnapMode is set to ToPlot.Workaround: N/A
| |||||
| 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.
| |||||
| 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.
| |||||
| 257280 Return | Generating an NI-DAQmx component and an Instrument Driver component in VB.NET results in a project that will not build. Workaround: Manually remove the namespace declaration added to the Instrument Driver component source code.
| |||||
| 288758 Return | The Measurement Studio tank control displays a red bar when oriented horizontally. If the Measurement Studio tank control is oriented horizontally and uses the Raised 3D style, a red bar will display at the base of the control. Workaround: N/A
| |||||
| 189198 Return | Windows 7 might cause issues of potential significance. National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. While most NI products work with Windows 7, NI has become aware of some compatibility issues regarding Windows 7. To learn more about Windows 7 and NI products, visit ni.com/info and enter the Info Code windows7. Workaround: N/A
| |||||
| 198036 Return | Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese. Workaround: N/A
| |||||
| 290486 Return | Using a logarithmic x-axis scale on Measurement Studio graphs can cause a hang for some data sets. This issue only happens when the lower bound of the x-axis range is <= .1000. This issue also only happens for certain data sets. Workaround: Ensure the lower bound of the x-axis range remains above .1000 when using a logarithmic scale on the x axis.
| |||||
| 292544 Return | Deployed Measurement Studio network variable client programs cannot use LogosXT. A LogosXT merge module is not available to redistribute the LogosXT components. Workaround: Follow the steps in the help topic Deploying Measurement Studio Network Variable Applications to create a Measurement Studio network variable server deployment.
| |||||
| 291290 Return | Distributing Measurement Studio applications to computers with User Account Control (UAC) enabled can result in an incomplete installation. This may result in failures in various Measurement Studio libraries, such as TDMS, Network Variable, and 3D styles in the User Interface library. Workaround: To resolve this issue, refer to KnowledgeBase 5KRERUQW.
| |||||
| 294382 Return | 64-bit TDMS applications might crash when reading properties. Workaround: N/A
| |||||
| 295481 Return | When targeting a previous .NET Framework version in Visual Studio 2008 or Visual Studio 2010, the Measurement Studio Update Project References wizard attempts to update your project references to the latest .NET Framework version. Workaround: When the Update Project References dialog box displays, select Do not show this prompt again for all projects in this solution.
| |||||
| 297106 Return | Uninstalling an application that uses network variable leaves behind the network variable assembly in the Global Assembly Cache (GAC). 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.
| |||||
| 337384 Return | Windows Forms Plot3DMesh causes an exception when run multiple times with a large number of points.Workaround: N/A
|
Document last updated on 3/14/2013