Measurement Studio 8.6 Known Issues
PrintOverview
This document contains the Measurement Studio 8.6 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 Issue appears as a row in the table and includes these fields:
- Issue ID - the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
- Legacy ID (optional) - If an issue has a legacy ID from NI's legacy/deprecated bug reporting database, you will see it appear on a separate line directly below the Issue ID in the table, or to the right of the Issue ID in the table of contents (separated by a space).
- Issue Title: in italics - it describes the issue in one sentence or less
- Problem Description - a few sentences which describe the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
- Workaround - possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
- Reported Version - the earliest version of Measurement Studio the issue was reported in. If you discover the issue appears in an earlier version of Measurement Studio than is reported in this field, you can report that to NI (contact information below) to have the field updated.
- Resolved Version - version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
- 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 (not necessarily the date the issue was reported to NI). This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face with Measurement Studio 8.6 during development. If an issue has multiple categories, it will appear multiple times in this document. To view the issues organized by date, visit the document linked below:
Known Issues by Date
Contacting NI
Feel free to contact NI regarding this document or issues in the document. 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 ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). 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. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
Note: To see known issue relating to Microsoft Visual Studio 2003, please view the ReadmeVS2003.html document located on your Measurement Studio media.
Known Issues by category
The following items are known issues in Measurement Studio 8.6 sorted by category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Visual Studio 2003 - .NET Class Libraries | ||||||
| 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
|
|||||
| Visual Studio 2003 - Visual C++ Class Libraries | ||||||
| 116288 Return |
Resizing the font of the CWNumEdit control causes the text to flicker before it updates. When resizing the font of the CWNumEdit ActiveX control, the text flickers back to the default size momentarily and then updates. This behavior occurs in Visual C++ and Visual Basic 6 but does not occur in .NET. Workaround: N/A
|
|||||
| 136196 Return |
The gridlines (ticks) do not invert when the Inverted checkbox is selected on the Range tab of the CWGraph3D Properties dialog box. Workaround: N/A
|
|||||
| Visual Studio 2005 - .NET Class Libraries | ||||||
| 117112 Return |
An extraneous horizontal or vertical white patch sometimes appears in a .NET control. 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.
|
|||||
| 121822 Return |
Changes to a TDMS file property value might not be reflected in other objects. If you have multiple TdmsFile objects accessing a single TDMS file and you update a property value in one object, the updated property value might not be reflected in the other objects. This known issue applies to file, channel group, and channel properties. 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
|
|||||
| 127686 Return |
The TDMS data written to two or more channels might become corrupted. 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 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.
|
|||||
| 133218 Return |
Rendering ASP.NET Web pages using Mozilla Firefox on Windows Vista can be very slow. Workaround: The following workaround may correct the issue:
|
|||||
| 133220 4B89AJ00 Return |
Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT. Logos is the National Instruments proprietary protocol for inter-process communication that is used by NI-Publish Subscribe Protocol ( psp:). Performance is especially degraded when the writer and network variable host use LogosXT and the reader that attempts to read the network variable uses Logos. This issue occurs for all reader classes.Workaround: For optimum performance, National Instruments recommends that all machines accessing network variables, including the machine that hosts the variable, should use LogosXT. If using LogosXT on all machines is not possible, you should disable LogosXT. You disable LogosXT by adding a DWORD value named DisablePSPXT to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LogosXT and setting its value to 1. If you must use a mix of Logos versions, you can reduce the performance loss by using Variable Manager. Use Variable Manager to configure a sufficiently large server-side buffer for the network variable.
|
|||||
| 133256 4DDCC0IO Return |
Creating network variables causes a small memory leak Creating a network variable using the ServerVariable.Create or ServerVariableInfo.Create methods results in a memory leak of approximately 50 bytes per variable that is created.Workaround: Consider using implicitly created network variables if you are creating and deleting numerous variables over a long period of time.
|
|||||
| 133380 Return |
In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler. The network variable class library deadlocks if you are stepping through code in a network variable class library event handler and you are watching any of the following properties in the Debugger Watch Window:
Workaround: To work around this issue, do not add the properties listed above to the Watch Window when stepping through network variable event handler code.
|
|||||
| 133384 Return |
In some instances, running your Visual C++ 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.
|
|||||
| 133390 Return |
National Instruments has designed the VisaNS API as a custom, optimized .NET interface to NI-VISA. Workaround: N/A
|
|||||
| 133396 Return |
Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly. As a result, part of the plot is not drawn. Microsoft has confirmed that this is a problem with clipping in the .NET Framework. Workaround: N/A
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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. 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| Visual Studio 2005 - Documentation | ||||||
| 119969 Return |
The Document/View Architecture in Visual C++ Test and Measurement Applications topic link is broken. Selecting the Document/View Architecture in Visual C++ Test and Measurement Applications topic in the Measurement Studio Help Table of Contents returns a page requesting a new info code. Workaround: Enter info code rddvav or refer to Document/View Architecture in Visual C++ Test and Measurement Applications on NI Developer Zone to access the topic.
|
|||||
| 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
|
|||||
| 133222 451EGFBK Return |
Windows Vista does not support use of help files with a .hlp file extension, including What's This? help. Workaround: If you want to view .hlp files, you must download and install the WinHlp.exe program from the Microsoft Download Center.
|
|||||
| 133327 Return |
In Visual C++, Measurement Studio user interface and 3D graph controls have What's This? help available, unless you are running Windows Vista. All code samples in the What's This? help are in Microsoft Visual Basic 6.0 syntax. Workaround: N/A
|
|||||
| 133328 Return |
In Visual C++, the What's This? help question mark is not always displayed. Workaround: In Visual C++, the What's This? help question mark that usually appears at the top right corner of a property page is not displayed until you right click an item in the property pages for a Measurement Studio control and choose to view What's This? help.
|
|||||
| 133331 Return |
Accessing the Help button in Visual C++ does not always show Measurement Studio help. Measurement Studio Visual C++ user interface and 3D graph control property pages include a Help button. However, you cannot use the button to access the NI Measurement Studio Help. Workaround: To access the NI Measurement Studio Help, click Start»All Programs»National Instruments»<Measurement Studio>»Measurement Studio Documentation, or from Visual Studio, select Help»Contents to view the Visual Studio table of contents, in which the NI Measurement Studio Help is listed.
|
|||||
| 133386 Return |
Measurement Studio Visual C++ properties that are defined by get and set methods do not show help in the Object Browser. Workaround: Refer to the NI Measurement Studio Help to view the help for these properties.
|
|||||
| 133437 Return |
Some help items do not work if MSDN help is not installed. The following help items do not work if MSDN help is not installed:
Workaround: N/A
|
|||||
| 133439 Return |
Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed. Workaround: Use the Contents, Index, or Search tabs instead to find the topic.
|
|||||
| 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.
|
|||||
| Visual Studio 2005 - Environment Integration Features | ||||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 33154 483FFE00 Return |
The Parameter Assistant does not always show NI-VISA resources or NI-488.2 boards. The Parameter Assistant does not show NI-VISA resources or NI-488.2 boards if only Measurement Studio Visual C++ support is installed. Workaround: Install Measurement Studio .NET language support.
|
|||||
| 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
|
|||||
| Visual Studio 2005 - Installer | ||||||
| 133291 Return |
If you install new, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit unexpected behavior. If you install new, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit one of the following behaviors:
Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix these problems.
|
|||||
| 133317 Return |
If you install previously licensed versions of Measurement Studio ActiveX controls on a machine that has new, unlicensed versions of the Measurement Studio controls, the controls might exhibit evaluation software behavior for 30 days. Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.
|
|||||
| 133318 Return |
Measurement Studio controls might exhibit evaluation behavior. If you have installed Measurement Studio 8.5 on a machine that has earlier versions of the Measurement Studio user interface and 3D graph controls and then uninstall Measurement Studio 8.5, the controls might exhibit evaluation software behavior for 30 days. Note: Applications that install earlier versions of the Measurement Studio user interface and 3D graph controls include ComponentWorks 2.0, Measurement Studio 1.0 and later, and LabVIEW 6i and later. Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.
|
|||||
| 133319 Return |
Installing Measurement Studio 8.5 over previous versions could result in a loss of Analysis class library functionality. This issue occurs only on systems where the underlying Analysis DLL from previous versions has never been deployed. In this case, if you install Measurement Studio 8.5 without installing the Analysis feature, then execute an install modification and add the Analysis installer feature, the underlying Analysis DLL from previous versions is not reinstalled. Complete the following steps to add the underlying Analysis DLL from previous versions to your system: Workaround:
|
|||||
| Visual Studio 2005 - Visual C++ Class Libraries | ||||||
| 116253 Return |
Programmatically changing the background color of a CWNumEdit control that has hidden increment/decrement buttons does not change the background for the entire control until you redraw it. Workaround: You can redraw the control by programmatically toggling the Enabled property of the CWNumEdit control after the background color has been updated.
|
|||||
| 116288 Return |
Resizing the font of the CWNumEdit control causes the text to flicker before it updates. When resizing the font of the CWNumEdit ActiveX control, the text flickers back to the default size momentarily and then updates. This behavior occurs in Visual C++ and Visual Basic 6 but does not occur in .NET. Workaround: N/A
|
|||||
| 133392 Return |
In Visual C++, if you have Measurement Studio windowless controls and any windowed controls together on an MFC dialog box, tabbing through the dialog box skips all windowless controls. Workaround: N/A
|
|||||
| 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.
|
|||||
| 133415 Return |
The Analysis library calls the LoadLibrary function. Under most circumstances, it is unsafe to call LoadLibrary inside DllMain. Therefore, avoid calling any analysis functions inside DllMain.Workaround: N/A
|
|||||
| 133416 Return |
If you have created a Visual C++ Console Application and are linking statically to MFC, you may encounter LNK2005 and LNK1169 errors. This problem happens when MFC static libraries and CRT static libraries link in the wrong order. To correct this problem, ensure that the #include <afx.h= statement is the first include statement in the generated stdafx.h header file. For more information, refer to Microsoft Knowledge Base Article 148652.Workaround: N/A
|
|||||
| 133421 Return |
Measurement Studio Visual C++ controls do not support being hosted in HTML dialogs. HTML dialogs use the CDHtmlDialog base class.Workaround: N/A
|
|||||
| 133422 Return |
The wrappers that Visual C++ generates for the Measurement Studio ActiveX controls are incomplete. Visual C++ generates wrappers only for the top-level objects in the controls. This causes some Visual C++ generated wrappers to produce compile errors. Workaround: Refer to National Instruments KnowledgeBase Article 2IECTLXL for more information and suggested workarounds.
|
|||||
| 132143 Return |
CNiNumEdit and CNiAxis error messages and documentation do not indicate that they support only absolute time and not time spans. CNiNumEdit and CNiAxis do not support time span values. Consequently, time values greater than "23:59:59"(hh:nn:ss) are invalid. Documentation and error messages do not describe this limitation. Workaround: N/A
|
|||||
| 130937 Return |
Dotted lines in ActiveX controls are printed as solid lines in some cases. GDI draws the dotted lines as solid if the width of the line is greater than 1. While printing a control, a metafile is created which normally involves scaling of the control and consequently scaling of the width of the line. This makes the width of the line greater than 1 and the print will have a solid line instead of a dotted line. Workaround: There are two workaround options:
|
|||||
| 136196 Return |
The gridlines (ticks) do not invert when the Inverted checkbox is selected on the Range tab of the CWGraph3D Properties dialog box. Workaround: N/A
|
|||||
| 129864 Return |
ControlImage and ControlImageEx may not fill multiple annotations on the CWGraph correctly. The annontations will not be filled correctly if the fill color or line color does not change, and if Workaround: Increase the line width to fill the annotation
|
|||||
| 138093 Return |
Changing the axis range on a CWGraph 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.
|
|||||
| 143046 Return |
The clipping region of the CWGraph changed between Measurement Studio versions 8.1.2 and 8.5 to use the plot bounds instead of the graph bounds. Workaround: N/A
|
|||||
| 151406 Return |
Setting the annotation style of a CWGraph to Range or Half Space causes the numbering to disappear for the X and Y axes. Workaround: N/A
|
|||||
| 134358 Return |
Disconnecting a Visual C++ Datasocket object sometimes results in a crash. This can happen if the Datasocket objects are wrapped in a class that exposes connect and disconnect methods. If multiple instances of these classes are instantiated, and then one of the objects is deleted before disconnecting all the Datasocket connections, the final call to Disconnect will crash.Workaround: Disconnect all instances before deleting any of the objects
|
|||||
| 156506 Return |
The Microsoft C++ Add Variable wizard throws a script error when Internet Explorer 8 is installed. This is a bug that has been reported to Microsoft. Workaround: Microsoft has now released a security update that fixes this issue. Information about the security update can be found here.
|
|||||
| Visual Studio 2008 - .NET Class Libraries | ||||||
| 117112 Return |
An extraneous horizontal or vertical white patch sometimes appears in a .NET control. 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.
|
|||||
| 121822 Return |
Changes to a TDMS file property value might not be reflected in other objects. If you have multiple TdmsFile objects accessing a single TDMS file and you update a property value in one object, the updated property value might not be reflected in the other objects. This known issue applies to file, channel group, and channel properties. 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
|
|||||
| 127686 Return |
The TDMS data written to two or more channels might become corrupted. 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 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.
|
|||||
| 133218 Return |
Rendering ASP.NET Web pages using Mozilla Firefox on Windows Vista can be very slow. Workaround: The following workaround may correct the issue:
|
|||||
| 133220 4B89AJ00 Return |
Network variable performance decreases when machines hosting the reader, writer, and variables are mixed between Logos and LogosXT. Logos is the National Instruments proprietary protocol for inter-process communication that is used by NI-Publish Subscribe Protocol ( psp:). Performance is especially degraded when the writer and network variable host use LogosXT and the reader that attempts to read the network variable uses Logos. This issue occurs for all reader classes.Workaround: For optimum performance, National Instruments recommends that all machines accessing network variables, including the machine that hosts the variable, should use LogosXT. If using LogosXT on all machines is not possible, you should disable LogosXT. You disable LogosXT by adding a DWORD value named DisablePSPXT to the registry key HKEY_LOCAL_MACHINE\SOFTWARE\National Instruments\LogosXT and setting its value to 1. If you must use a mix of Logos versions, you can reduce the performance loss by using Variable Manager. Use Variable Manager to configure a sufficiently large server-side buffer for the network variable.
|
|||||
| 133256 4DDCC0IO Return |
Creating network variables causes a small memory leak Creating a network variable using the ServerVariable.Create or ServerVariableInfo.Create methods results in a memory leak of approximately 50 bytes per variable that is created.Workaround: Consider using implicitly created network variables if you are creating and deleting numerous variables over a long period of time.
|
|||||
| 133380 Return |
In some circumstances, the network variable class library deadlocks if you are stepping through code in a network variable class library event handler. The network variable class library deadlocks if you are stepping through code in a network variable class library event handler and you are watching any of the following properties in the Debugger Watch Window:
Workaround: To work around this issue, do not add the properties listed above to the Watch Window when stepping through network variable event handler code.
|
|||||
| 133384 Return |
In some instances, running your Visual C++ 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.
|
|||||
| 133390 Return |
National Instruments has designed the VisaNS API as a custom, optimized .NET interface to NI-VISA. Workaround: N/A
|
|||||
| 133396 Return |
Under some circumstances, plots with data that extend outside the plot area are clipped incorrectly. As a result, part of the plot is not drawn. Microsoft has confirmed that this is a problem with clipping in the .NET Framework. Workaround: N/A
|
|||||
| 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.
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 31271 40A7S0HW Return |
Editing an axis interactively and then calling PlotYAppend from the AutoRefresh callback with a fixed axis erases the previous committed axis value. Workaround: Put the control inside an UpdatePanel and plot data using the timer tick event
|
|||||
| 96497 Return |
Calling ShowDialog on a Windows Form that contains a property editor control might cause an InvalidCastException. Calling ShowDialog on a Windows Form that contains a property editor control linked to a Measurement Studio .NET control from a non-UI thread causes an InvalidCastException.Workaround: Use SetApartmentState() to set the ApartmentState of the thread created to ApartmentState.STA.
|
|||||
| 115770 Return |
Measurement Studio UI controls that are part of a custom Web control do not display during design time. This issue has been fixed with the release of Visual Studio 2008 SP1. Workaround: Upgrade to Visual Studio 2008 SP1. The controls will display correctly at run time even without SP1.
|
|||||
| 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
|
|||||
| 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
|
|||||
| 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.
|
|||||
| Visual Studio 2008 - Documentation | ||||||
| 119969 Return |
The Document/View Architecture in Visual C++ Test and Measurement Applications topic link is broken. Selecting the Document/View Architecture in Visual C++ Test and Measurement Applications topic in the Measurement Studio Help Table of Contents returns a page requesting a new info code. Workaround: Enter info code rddvav or refer to Document/View Architecture in Visual C++ Test and Measurement Applications on NI Developer Zone to access the topic.
|
|||||
| 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
|
|||||
| 133222 451EGFBK Return |
Windows Vista does not support use of help files with a .hlp file extension, including What's This? help. Workaround: If you want to view .hlp files, you must download and install the WinHlp.exe program from the Microsoft Download Center.
|
|||||
| 133437 Return |
Some help items do not work if MSDN help is not installed. The following help items do not work if MSDN help is not installed:
Workaround: N/A
|
|||||
| 133439 Return |
Links to hardware class library documentation may be broken if you do not have the latest hardware drivers installed. Workaround: Use the Contents, Index, or Search tabs instead to find the topic.
|
|||||
| 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.
|
|||||
| 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:
|
|||||
| Visual Studio 2008 - Environment Integration Features | ||||||
| 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
|
|||||
| 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.
|
|||||
| 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
|
|||||
| 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.
|
|||||
| 33154 483FFE00 Return |
The Parameter Assistant does not always show NI-VISA resources or NI-488.2 boards. The Parameter Assistant does not show NI-VISA resources or NI-488.2 boards if only Measurement Studio Visual C++ support is installed. Workaround: Install Measurement Studio .NET language support.
|
|||||
| 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
|
|||||
| Visual Studio 2008 - Installer | ||||||
| 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.
|
|||||
| 133291 Return |
If you install new, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit unexpected behavior. If you install new, unlicensed versions of Measurement Studio ActiveX controls on a machine that has previously licensed versions of the Measurement Studio controls, the controls might exhibit one of the following behaviors:
Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix these problems.
|
|||||
| 133317 Return |
If you install previously licensed versions of Measurement Studio ActiveX controls on a machine that has new, unlicensed versions of the Measurement Studio controls, the controls might exhibit evaluation software behavior for 30 days. Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.
|
|||||
| 133318 Return |
Measurement Studio controls might exhibit evaluation behavior. If you have installed Measurement Studio 8.5 on a machine that has earlier versions of the Measurement Studio user interface and 3D graph controls and then uninstall Measurement Studio 8.5, the controls might exhibit evaluation software behavior for 30 days. Note: Applications that install earlier versions of the Measurement Studio user interface and 3D graph controls include ComponentWorks 2.0, Measurement Studio 1.0 and later, and LabVIEW 6i and later. Workaround: Use the Measurement Studio ActiveX License Fixer Utility located on your CD in the ActiveX License Fixer Utility folder to fix this problem.
|
|||||
| 133319 Return |
Installing Measurement Studio 8.5 over previous versions could result in a loss of Analysis class library functionality. This issue occurs only on systems where the underlying Analysis DLL from previous versions has never been deployed. In this case, if you install Measurement Studio 8.5 without installing the Analysis feature, then execute an install modification and add the Analysis installer feature, the underlying Analysis DLL from previous versions is not reinstalled. Complete the following steps to add the underlying Analysis DLL from previous versions to your system: Workaround:
|
|||||
| Visual Studio 2008 - Visual C++ Class Libraries | ||||||
| 116253 Return |
Programmatically changing the background color of a CWNumEdit control that has hidden increment/decrement buttons does not change the background for the entire control until you redraw it. Workaround: You can redraw the control by programmatically toggling the Enabled property of the CWNumEdit control after the background color has been updated.
|
|||||
| 116288 Return |
Resizing the font of the CWNumEdit control causes the text to flicker before it updates. When resizing the font of the CWNumEdit ActiveX control, the text flickers back to the default size momentarily and then updates. This behavior occurs in Visual C++ and Visual Basic 6 but does not occur in .NET. Workaround: N/A
|
|||||
| 127067 Return |
Measurement Studio Support for Visual Studio 2005 Visual C++ examples do not compile when upgraded to Visual Studio 2008. If you upgrade a Visual Studio 2005 VCNET example or to Visual Studio 2008 by opening the Visual Studio 2005 solution in Visual Studio 2008, the upgraded application will not compile. The application will not compile because National Instruments defines the minimum system requirement through the symbol _WIN32_WINNT, which is set to 0x0400 (WINNT). This value conflicts with the SDK 6.0 default value of _WIN32_IE, which is used by Visual Studio 2008 Visual C++.Workaround: You should make the values of _WIN32_WINNT and _WIN32_IE compatible for usage with SDK 6.0. To do this, either increase the value of _WIN32_WINNT to 0x0500 (Win2k) or decrease the value of _WIN32_IE to a value <0x0601.
|
|||||
| 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.
|
|||||
| 133415 Return |
The Analysis library calls the LoadLibrary function. Under most circumstances, it is unsafe to call LoadLibrary inside DllMain. Therefore, avoid calling any analysis functions inside DllMain.Workaround: N/A
|
|||||
| 133416 Return |
If you have created a Visual C++ Console Application and are linking statically to MFC, you may encounter LNK2005 and LNK1169 errors. This problem happens when MFC static libraries and CRT static libraries link in the wrong order. To correct this problem, ensure that the #include <afx.h= statement is the first include statement in the generated stdafx.h header file. For more information, refer to Microsoft Knowledge Base Article 148652.Workaround: N/A
|
|||||
| 133421 Return |
Measurement Studio Visual C++ controls do not support being hosted in HTML dialogs. HTML dialogs use the CDHtmlDialog base class.Workaround: N/A
|
|||||
| 133422 Return |
The wrappers that Visual C++ generates for the Measurement Studio ActiveX controls are incomplete. Visual C++ generates wrappers only for the top-level objects in the controls. This causes some Visual C++ generated wrappers to produce compile errors. Workaround: Refer to National Instruments KnowledgeBase Article 2IECTLXL for more information and suggested workarounds.
|
|||||
| 132143 Return |
CNiNumEdit and CNiAxis error messages and documentation do not indicate that they support only absolute time and not time spans. CNiNumEdit and CNiAxis do not support time span values. Consequently, time values greater than "23:59:59"(hh:nn:ss) are invalid. Documentation and error messages do not describe this limitation. Workaround: N/A
|
|||||
| 130937 Return |
Dotted lines in ActiveX controls are printed as solid lines in some cases. GDI draws the dotted lines as solid if the width of the line is greater than 1. While printing a control, a metafile is created which normally involves scaling of the control and consequently scaling of the width of the line. This makes the width of the line greater than 1 and the print will have a solid line instead of a dotted line. Workaround: There are two workaround options:
|
|||||
| 129864 Return |
ControlImage and ControlImageEx may not fill multiple annotations on the CWGraph correctly. The annontations will not be filled correctly if the fill color or line color does not change, and if Workaround: Increase the line width to fill the annotation
|
|||||
| 138093 Return |
Changing the axis range on a CWGraph 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.
|
|||||
| 143046 Return |
The clipping region of the CWGraph changed between Measurement Studio versions 8.1.2 and 8.5 to use the plot bounds instead of the graph bounds. Workaround: N/A
|
|||||
| 151406 Return |
Setting the annotation style of a CWGraph to Range or Half Space causes the numbering to disappear for the X and Y axes. Workaround: N/A
|
|||||
| 134358 Return |
Disconnecting a Visual C++ Datasocket object sometimes results in a crash. This can happen if the Datasocket objects are wrapped in a class that exposes connect and disconnect methods. If multiple instances of these classes are instantiated, and then one of the objects is deleted before disconnecting all the Datasocket connections, the final call to Disconnect will crash.Workaround: Disconnect all instances before deleting any of the objects
|
|||||
| 156506 Return |
The Microsoft C++ Add Variable wizard throws a script error when Internet Explorer 8 is installed. This is a bug that has been reported to Microsoft. Workaround: Microsoft has now released a security update that fixes this issue. Information about the security update can be found here.
|
|||||
Document last updated on 6/18/2009
Reader Comments | Submit a comment »
Legal
This tutorial (this "tutorial") was developed by National Instruments ("NI"). Although technical support of this tutorial may be made available by National Instruments, the content in this tutorial may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this content with each new revision of related products and drivers. THIS TUTORIAL IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).