Archived: Measurement Studio 2009 Known Issues

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.

Overview

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 Measurement Studio 2009 known issues that were discovered before and since the release of Measurement Studio 2009. 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:

  • 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 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

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 Category

The following items are known issues in Measurement Studio 2009 sorted by Category.

Analysis
197171 Using SingleToneInformation.GetDetectedSignal may result in results that are 180 degrees out of phase.
191880 Matrix operations that utilize the Intel MKL on Windows have slight numerical difference between Measurement Studio 2009 and prior Measurement Studio versions.
176144 32-bit analysis and 64-bit analysis library results can have slight numerical differences
295320 The function GaussHG returns NaN for X values less than 0.
370422 The HarmonicAnalyzer method in the Analysis Spectral Measurement library throws an AccessViolationException regardless of the input.
DataSocket
181874 The Datasocket "Select URL" dialog may crash Visual Studio when using Windows Vista.
Deploying Applications
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.
154564 Sometimes the Measurement Studio ASP.NET Web Forms controls throw an InvalidOperationException in IIS.
191580 Uninstalling National Instruments products may also remove installed .NET applications that use National Instruments libraries.
193763 Visual Studio Setup Projects for DataSocket applications do not automatically add the logos.msm merge module.
193809 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
197154 Some applications on a target computer may report errors or terminate unexpectedly after installing a distribution that was created on a computer with Measurement Studio 2009 installed.
226968 Visual Studio Setup Projects for DataSocket applications do not automatically add the ni_utility.msm merge module.
220060 The 64-bit Logos merge module does not contain the commands necessary to install necessary Logos services.
244273 A project using Measurement Studio mixed mode assemblies built against .NET Frameworks prior to .NET Framework 4 cannot run against .NET Framework 4.
292544 Deployed Measurement Studio network variable client programs cannot use LogosXT.
291290 Distributing Measurement Studio applications to computers with User Account Control (UAC) enabled can result in an incomplete installation.
297106 Uninstalling an application that uses network variable leaves behind the network variable assembly in the Global Assembly Cache (GAC).
Hardware Libraries
133322 In some circumstances, you receive error, HRESULT E_FAIL, when using the DAQ Application Project Wizard.
199947 Significant decrease in performance occurs when using NI-488.2 for Microsoft Windows and LabVIEW Real-Time
221889 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.
257280 Generating an NI-DAQmx component and an Instrument Driver component in VB.NET results in a project that will not build.
Installer
292897 Upgrading from Measurement Studio 2009 to Measurement Studio 2010 can result in failing distribution builds from other National Instruments software.
Licensing
133384 In some instances, running your Visual C++/CLI project results in unlicensed exceptions.
National Instruments Common Classes
322666 Istantiating a ComplexDouble for the first time takes a longer than expected.
Network Variable
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
133380 In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler.
182120 Network Variable does not support variables with the Timestamp data type.
196747 Using a single network variable writer from multiple threads may result in a hang in your application.
180681 A memory leak exists in WebForms.NetworkVariableDataSource when Dispose is not called before the host page is unloaded.
240792 Setting the DefaultReadValue of a NetworkVariableBinding object to null results in a NullReferenceException.
251984 Waveform timing information is lost if a network variable with a waveform type is bound to a waveform graph.
Product Documentation
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.
133439 Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed.
TDMS
194685 TdmsFile.ConvertFileFormat may intermittently throw a TdmsException.
168274 Reading and writing data within the same loop using TDMS results in a significant performance decrease.
224471 TDMS file groups with the WaveformLayout property set to PairedTimeAndSampleChannels may become corrupted.
227696 Appending data and adding properties to a TDMS file in a specific sequence can corrupt the file data.
243788 Writing an AnalogWaveform with irregular timing to a TDMS file using AppendAnalogWaveform can result in a different number of data and timestamp values.
247826 The TDMS .NET API leaks memory when creating or reading channels or channel groups.
294382 64-bit TDMS applications might crash when reading properties.
User Interface
122353 Mouse cursor changes to the default mouse cursor after zooming.
133396 Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly.
31074 489EEQ03 Dropping a Measurement Studio control onto the Design vew of an ASP.NET Web site might result in an error.
31138 435E06I0 Calling DoEvents in a NumericEdit control callback may cause an exception.
31271 40A7S0HW Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value.
96497 Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException.
115770 Measurement Studio UI controls that are part of a custom Web control do not display during design time.
140923 Changing the axis range on a WaveformGraph, ScatterGraph, or ComplexGraph with few points causes skewed plot lines.
194621 If a graph includes multiple axes, ZoomXY may not zoom accurately.
190486 If you call Graph.ToImage(Size), the DrawGridLines method incorrectly draws the graph axes.
203199 The Axis.EndLabelsAlwaysVisible property is not cloned when you call the Clone method on an X or Y axis.
208239 ClipDataPoints returns an extra point when used on a WavefromPlot.
208242 The ClipDataPoints method does not work for ScatterPlot objects.
217352 Updating the InteractionModeDefault of any .NET graph while the mouse is over the graph will not update the mouse cursor.
222183 The animation rectangle shown when zooming on a graph moves very slowly if many points are plotted.
222524 The y-axis will accomodate the text length of a custom division label even if the custom division is not visible.
222712 The edit range entry box does not honor axis label formats for some formats.
223012 A .NET waveform graph that throws an exception when calling PlotComplexWaveformsAppend, PlotComplexWaveformsAppendMultiple, PlotWaveformsAppend, or PlotWaveformsAppendMultiple will become unresponsive and will not redraw.
235353 Zooming a .NET waveform graph multiple times with minor gridlines or visible ticks can result in a hang.
235390 Boolean controls do not correctly handle the Escape key.
235391 Measurement Studio .NET boolean controls do not correctly handle loss of application focus.
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.
249777 Some ranges can result in incorrect ticking on graph axes with a logarithmic scale.
249802 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.
251034 Zoom animation is drawn even when a .NET graph has not been added to a Windows Form.
252409 Cursors with a SnapMode value of ToPlot or NearestPoint slow plotting dramatically when the cursors are not visible.
288758 The Measurement Studio tank control displays a red bar when oriented horizontally.
198036 Vertical captions on Measurement Studio controls do not display correctly in some languages, such as Korean, Japanese, and Chinese.
276435 If you call the Draw method on a Measurement Studio annotation and the Visible property of the annotation is set to false, the annotation does not draw.
290486 Using a logarithmic x-axis scale on Measurement Studio graphs can cause a hang for some data sets.
297181 Building a Measurement Studio ASP.NET Web Forms project fails on computers with United States Federal Information Processing Standard (FIPS) enabled.
302132 Cloning a ScatterPlot object does not clone the ProcessSpecialValues property.
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.
316607 The WaveformGraph Plot with ProcessSpecialValues set to true hangs when double.PositiveInfinity is plotted or crashes when double.NegativeInfinity is plotted.
349762 The Windows Forms NumericEdit control does not initialize to a NaN value.
360932 The displayed scales for the Slide, Thermometer, and Tank WindowsForms controls do not accurately map to a value.
338802 Calling the ClearData method on the Windows Forms DigitalWaveformGraph control a second time on an empty graph causes the horizontal scrollbar to disappear.
Visual Studio Integration
111651 The error, "Attempting to deserialize an empty stream", sometimes occurs when you attempt to build a Web Site project using Measurement Studio controls.
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.
133413 The Windows Forms Designer presents an error page stating that parts cannot be found.
129222 Using Measurement Studio controls in a Visual Basic .NET application with an '&' in the project path name causes errors.
33786 Undo does not work for some Measurement Studio .NET properties when edited from the Microsoft Visual Studio Designer.
195429 If you have the "Automatically Update ASP.NET Project" option set to false in Visual Studio 2008, the project is updated.
181843 Dropping a Measurement Studio .NET control into a Visual Studio Web application at design time may result in an error.
215669 Measurement Studio adds National Instruments references to the web.config file of non-Measurement Studio projects.
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.
295481 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.
284835 You cannot de-select the Web Forms User Interface Control Library from the Add/Remove Class Libraries Wizard.



ID Known Issue
Analysis
197171

Return
Using SingleToneInformation.GetDetectedSignal may result in results that are 180 degrees out of phase.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40147/
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: 00/40148/
176144

Return
32-bit analysis and 64-bit analysis library results can have slight numerical differences
For more information about this issue, please refer to KB 51MA76UB: Why are There Minor Differences in Analysis Function Results Between 32-bit and 64-bit LabVIEW, Measurement Studio, or LabWindows/CVI Applications?

Workaround: N/A

Reported Version: 2009    Resolved Version: Unknown    Added: 00/40283/
295320

Return
The function GaussHG returns NaN for X values less than 0.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 00/40500/
370422

Return
The HarmonicAnalyzer method in the Analysis Spectral Measurement library throws an AccessViolationException regardless of the input.
This only occurs when using the overloaded HarmonicAnalyzer(Double[], Int32, Double, Double, Double[], Double[], Double) form of the method.The exception is not thrown for the other overloaded forms.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2013    Added: 00/41329/
DataSocket
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

Reported Version: 8.5    Resolved Version: 2012    Added: 00/40148/
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.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 00/39769/
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

Reported Version: 8.0.1    Resolved Version: 2010    Added: 00/39911/
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: 00/40148/
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.

Reported Version: 8.6    Resolved Version: 2010    Added: 00/40148/
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:
  1. After installing both the network variable application installer and the NINETVARSERV installer, reboot the computer.
  2. Ensure you install the NINETVARSERV installer after the network variable application installer.


Reported Version: 8.6.1    Resolved Version: 2010    Added: 00/40148/
197154

Return
Some applications on a target computer may report errors or terminate unexpectedly after installing a distribution that was created on a computer with Measurement Studio 2009 installed.
See KnowledgeBase 53F9JDXU for more information and a patch installer.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 00/40148/
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.

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40150/
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: 00/40515/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40515/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40661/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40774/
297106

Return
Uninstalling an application that uses network variable leaves behind the network variable assembly in the Global Assembly Cache (GAC).

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40774/
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.

Reported Version: 8.0.1    Resolved Version: N/A    Added: 00/39769/
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.

Reported Version: 8.5    Resolved Version: Unknown    Added: 00/40186/
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.

Reported Version: 8.6.1    Resolved Version: 2012    Added: 00/40515/
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.

Reported Version: 8.0    Resolved Version: 2012    Added: 00/40515/
Installer
292897

Return
Upgrading from Measurement Studio 2009 to Measurement Studio 2010 can result in failing distribution builds from other National Instruments software.
This issue only happens if you install the NI Measurement Studio 2009 Network Variable Update.

Workaround: If you are unable to build distributions in other National Instruments software, refer to one of the following KnowledgeBase articles:
  • LabVIEW: KB ID 5K5BCLSK
  • LabWindows/CVI: KB ID 5LMA6NXU


Reported Version: 2009    Resolved Version: 2010 SP1    Added: 00/40774/
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.

Reported Version: 8.0    Resolved Version: N/A    Added: 00/39769/
National Instruments Common Classes
322666

Return
Istantiating a ComplexDouble for the first time takes a longer than expected.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 00/40960/
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.

Reported Version: 8.1.2    Resolved Version: N/A    Added: 00/39769/
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: 00/39769/
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: 00/39769/
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: 00/40148/
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.

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40148/
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.

Reported Version: 8.6.1    Resolved Version: 2010    Added: 00/40515/
240792

Return
Setting the DefaultReadValue of a NetworkVariableBinding object to null results in a NullReferenceException.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40515/
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: 00/40515/
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

Reported Version: 8.1.2    Resolved Version: N/A    Added: 00/39769/
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: 00/39769/
TDMS
194685

Return
TdmsFile.ConvertFileFormat may intermittently throw a TdmsException.

Workaround: Try the method again until it succeeds.

Reported Version: 2009    Resolved Version: 2010    Added: 00/40147/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40148/
224471

Return
TDMS file groups with the WaveformLayout property set to PairedTimeAndSampleChannels may become corrupted.
If a TDMS file has the AutoSave property set to true and contains a group with the WaveformLayout property set to PairedTimeAndSampleChannels, the data in the file will become corrupted after the third append operation.

Workaround: Turn off AutoSave for the TDMS file, and save the file manually with the Save() method anytime changes to the file occur. Changes occur after adding channels or groups to the file, or after write operations.

Reported Version: 2009    Resolved Version: 2010    Added: 00/40515/
227696

Return
Appending data and adding properties to a TDMS file in a specific sequence can corrupt the file data.
The following specific sequence of calls causes the data in a TDMS file to be corrupted:
for(int i = 0; i < 3; i++)
{
    channel1.AppendData<double>(data, TdmsSaveFile.SaveFile);
    channel2.AppendData<double>(data, TdmsSaveFile.SaveFile);
    channel1.AddProperty("Test", TdmsPropertyDataType.Int32, samples);
    file.Save();
}

Note that the following conditions must be met for this behavior to occur:
  1. You must be writing to two channels.
  2. The value passed for the saveFile parameter in TDMS_AppendDataValues must be 1 for both channels.
  3. The TDMS_SetChannelProperty call must come after the two writes.
  4. TDMS_SaveFile must be called after TDMS_SetChannelProperty.
  5. The loop must have at least 3 iterations.
If 0 is passed for the saveFile parameter for either of the TDMS_AppendDataValues calls, or the TDMS_SetChannelProperty call is done before either of the data writes, the data is not corrupted.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 00/40515/
243788

Return
Writing an AnalogWaveform with irregular timing to a TDMS file using AppendAnalogWaveform can result in a different number of data and timestamp values.

Reported Version: 2009    Resolved Version: 2010    Added: 00/40515/
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.

Reported Version: 8.6    Resolved Version: 2010    Added: 00/40515/
294382

Return
64-bit TDMS applications might crash when reading properties.

Workaround: N/A

Reported Version: 8.6    Resolved Version: 2010 SP1    Added: 00/40774/
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

Reported Version: 8.0.1    Resolved Version: N/A    Added: 00/39769/
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: 00/39769/
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.

Reported Version: 8.0.1    Resolved Version: 2010    Added: 00/39769/
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

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 00/39769/
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: 00/39769/
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: 00/39769/
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: 00/39818/
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.

Reported Version: 8.1    Resolved Version: 2010    Added: 00/39882/
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

Reported Version: 8.6    Resolved Version: 2010    Added: 00/40147/
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.

Reported Version: 8.6.1    Resolved Version: 2010    Added: 00/40514/
203199

Return
The Axis.EndLabelsAlwaysVisible property is not cloned when you call the Clone method on an X or Y axis.

Workaround: After the clone call, manually set the EndLabelsAlwaysVisible property of the new axis to the value of the original axis.

Reported Version: 2009    Resolved Version: 2010    Added: 00/40514/
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

Reported Version: 8.5    Resolved Version: 2012    Added: 00/40515/
208242

Return
The ClipDataPoints method does not work for ScatterPlot objects.

Workaround: N/A

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40515/
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.

Reported Version: 8.6.1    Resolved Version: 2010 SP1    Added: 00/40515/
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

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40515/
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

Reported Version: 8.6    Resolved Version: 2010 SP1    Added: 00/40515/
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

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40515/
223012

Return
A .NET waveform graph that throws an exception when calling PlotComplexWaveformsAppend, PlotComplexWaveformsAppendMultiple, PlotWaveformsAppend, or PlotWaveformsAppendMultiple will become unresponsive and will not redraw.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 00/40515/
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.

Reported Version: 8.6.1    Resolved Version: 2010    Added: 00/40515/
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

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 00/40515/
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:
  1. You set the interaction mode of the boolean control to SwitchUntilReleased.
  2. Start the application, and another small application you can switch to.
  3. You press and hold the mouse over the boolean control.
  4. You Alt+Tab to another application while still holding down the mouse.
  5. You move the mouse away from the control and release.
If you do these steps, the boolean control is stuck in the true position. Returning the focus to the application does not correct the state of the boolean control.

Workaround: N/A

Reported Version: 8.0.1    Resolved Version: 2010 SP1    Added: 00/40515/
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: 00/40515/
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: 00/40515/
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

Reported Version: 8.1    Resolved Version: 2010    Added: 00/40515/
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

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40515/
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: 00/40515/
252409

Return
Cursors with a SnapMode value of ToPlot or NearestPoint slow plotting dramatically when the cursors are not visible.

Workaround: Change the SnapMode of the cursors while plotting.

Reported Version: 2009    Resolved Version: 2010    Added: 00/40515/
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

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40619/
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: 00/40624/
276435

Return
If you call the Draw method on a Measurement Studio annotation and the Visible property of the annotation is set to false, the annotation does not draw.
All other Measurement Studio user interface components draw correctly when you call Draw, even if the Visible property is set to false.

Workaround: Ensure the Visible property of the annotation is set to true before drawing the annotation.

Reported Version: 2009    Resolved Version: 2010 SP1    Added: 00/40624/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40625/
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: 00/40773/
302132

Return
Cloning a ScatterPlot object does not clone the ProcessSpecialValues property.

Workaround: Manually clone the ProcessSpecialValues property.

Reported Version: 2009    Resolved Version: 2010 SP1    Added: 00/40773/
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: 00/40960/
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: 00/40960/
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: 00/40960/
316607

Return
The WaveformGraph Plot with ProcessSpecialValues set to true hangs when double.PositiveInfinity is plotted or crashes when double.NegativeInfinity is plotted.
This can occur when calculating the MajorDivisions or MinorDivisions when AutoSpacing is set to false.

Workaround: Set AutoSpacing to true.

Reported Version: 2009    Resolved Version: 2012    Added: 00/40961/
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.

Reported Version: 2009    Resolved Version: N/A    Added: 00/41120/
360932

Return
The displayed scales for the Slide, Thermometer, and Tank WindowsForms controls do not accurately map to a value.
The value being displayed on the control may be slightly different from the actual value of the control. This is only noticeable if the control is very large, or if you are interacting with the control and want to set the value to the minimum or maximum.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2012    Added: 00/41120/
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: 00/41334/
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.

Reported Version: 8.5    Resolved Version: N/A    Added: 00/39769/
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: 00/39769/
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: 00/39769/
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.

Reported Version: 8.5    Resolved Version: 2010    Added: 00/39818/
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: 00/39843/
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

Reported Version: 8.5    Resolved Version: 2010    Added: 00/40147/
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: 00/40148/
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:
  • Remove the Measurement Studio controls from the Toolbox when you are working within a WebForms project.
  • For both Visual Studio 2005 and Visual Studio 2008, you must make the following edit in the Visual Studio 2005 registry location. This is due to a bug in the Visual Studio 2008 integration code. Refer to How to Modify the Windows Registry for information on how to work safely within the Windows Registry.
    1. Navigate to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\Measurement Studio\.NET Tools.
    2. Create or update the Automatically Update ASP.NET Projects="False" entry.


Reported Version: 8.6    Resolved Version: 2010    Added: 00/40514/
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: 00/40515/
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: 00/40515/
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.

Reported Version: 8.5    Resolved Version: 2010 SP1    Added: 00/40774/
284835

Return
You cannot de-select the Web Forms User Interface Control Library from the Add/Remove Class Libraries Wizard.
This bug exists for Measurement Studio 2010 SP1 and prior versions, and is fixed in Measurement Studio 2012 for Visual Studio 2008 and 2010. The bug still exists in Measurement Studio 2012 for Visual Studio 2005.

Workaround: Remove and re-add the NationalInstruments.Common.dll, NationalInstruments.UI.dll, and NationalInstruments.UI.WebForms.dll assemblies from the Visual Studio project.

Reported Version: 2009    Resolved Version: 2012    Added: 00/40960/

Document last updated on 3/14/2013

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