Select the product you need help with
Description of the hotfix rollup package for Microsoft Test Manager 2010: October 2010Article ID: 2387011 - View products that this article applies to. On This PageINTRODUCTIONThis article describes a hotfix rollup package that resolves the following issues in Microsoft Test Manager 2010 and that is dated October 2010. Crashes and exceptions Issue 1 When you perform operations to work items in Test Manager, Test Manager may crash, and then you receive the following error message: The specified Visual is not an ancestor of this Visual. at System.Windows.Media.Visual.TrySimpleTransformToAncestor() at System.Windows.Media.Visual.InternalTransformToAncestor() at Microsoft.TeamFoundation.TestManagement.Client.WpfControls.WindowsFormsHostEx.GetViewport() at Microsoft.TeamFoundation.TestManagement.Client.WpfControls.WindowsFormsHostEx.ClipContentToScrollViewer() at Microsoft.TeamFoundation.TestManagement.Client.WpfControls.WindowsFormsHostEx.Invalidate() at Microsoft.TeamFoundation.TestManagement.Controls.WpfWorkItemControls.WpfWorkItemTabControl.<>c__DisplayClass2.<InvalidateLegacyControls>b__0() When you try to edit an invalid query by using Test Manager, a Microsoft.TeamFoundation.TestManagement.Client.Runtime.VisualizationCannotBeCreatedException exception occurs, and then you receive the following error message: Failed to create the UI element of following type: Microsoft.TeamFoundation.TestManagement.Activities.SelectWorkItemsPartView. Issue 3 When you try to close a test case dialog box, Test Manager may crash after you select Don't Save in the test case dialog box. Issue 4 After you update the Properties settings of the test plan, the data becomes corrupted. For example, the information in the Owners combo box might be incorrect. Issue 5 Consider the following scenario:
The test variable contains a value that is not valid. Issue 6 When you try to delete an iteration of a test case by using the shortcut menu in Test Manager, Test Manager may crash. Note If you debug the problem, a System.Data.DeletedRowInaccessibleException exception occurs, and then you receive the following error message: Deleted row information cannot be accessed through the row. at System.Data.DataRow.GetDefaultRecord() at System.Data.DataRow.get_Item() at Microsoft.TeamFoundation.TestManagement.Client.TestCase.HasDataSetChanged() at Microsoft.TeamFoundation.TestManagement.Client.TestCase.Flush() at Microsoft.TeamFoundation.TestManagement.Controls.TestStepsPart.set_Dirty() at Microsoft.TeamFoundation.TestManagement.Controls.TestStepsPart.SetDirtyHandler() at Microsoft.TeamFoundation.TestManagement.Controls.BaseActionItem.OnSetDirty() at Microsoft.TeamFoundation.TestManagement.Controls.DeleteIterationActon.Perform at Microsoft.TeamFoundation.TestManagement.Controls.TestStepsCustomControl.ContextMenuClickHandler() at System.Windows.RoutedEventHandlerInfo.InvokeHandler() at System.Windows.EventRoute.InvokeHandlersImpl() Issue 7 When you try to assign a build that has an unassigned drop folder to a test plan in Test Manager, Test Manager may crash. Issue 8 When you perform an operation in Test Manager, a Dr. Watson error may occur, and then you receive the following error message: Application: mtm.exe Event type: Clr20r3 Exception code: system.argumentexception FAULT SYMBOL: MICROSOFT.TEAMFOUNDATION.TESTMANAGEMENT.COMMON.NI.DLL!Microsoft.TeamFoundation.TestManagement.Common.KeyedObservableCollection_2[[System.Int32,_mscorlib]] Issue 9 When you perform an operation in Test Manager, a Dr. Watson error may occur, and then you receive the following error message: Application: mtm.exe Event type: Clr20r3 Exception code: system.exception FAULT SYMBOL: MICROSOFT.VISUALSTUDIO.TESTTOOLS.MANUALTEST.COMMON.DLL!Microsoft.VisualStudio.TestTools.ManualTest.Common.TestPointCollectionViewModel.set_ActiveIteration Issue 10 When you perform an operation in Test Manager, a Dr. Watson error may occur, and then you receive the following error message: Application: mtm.exe Event type: Clr20r3 Exception code: System.ComponentModel.Win32 FAULT SYMBOL: MICROSOFT.VISUALSTUDIO.QUALITYTOOLS.COMMON.NI.DLL!Microsoft.VisualStudio.TestTools.Common.SingleInstance.RunningObjectTable.GetObject When you insert a new step in a test case that contains some parameters, data corruption occurs. For example, an iteration of a parameter disappears. Memory leaksIssue 1When you repeatedly open and close a work item that includes a webpage control in the template, the Test Manager process leaks memory. Issue 2 Consider the following scenario:
Issue 3 When you run a test case in Test Manager while an instance of an application is running, the MTM.exe process leaks memory and may grow by hundreds of megabytes. For example, you run a test case in Test Manager while an instance of a Visual Studio 2010 is running. Issue 4 When you run concurrent operations for several hours in Test Manager, you may receive an Out-of-Memory exception, and then Test Manager crashes. Issue 5 When you add many test cases to a test suite, a memory leak occurs. Other issuesIssue 1 After you close the Test Case Manager page, the test cases continue to be downloaded from Microsoft Team Foundation Server (TFS). Issue 2 When you run a test case, and when the Assigned To field in the test case is empty, you receive the following error message: Object reference not set to instance of object. Issue 3 Test Manager does not have a feature to let you type a fractional number in a Double data type field of a work item. Issue 4 An automated test case from a build-drop path requires a long time to load. Issue 5 When a test result is published on a test suite that contains thousands of test cases in Test Manager, the publishing operation is slow. Issue 6 When you connect Test Manager to a Team Foundation Server (TFS) server, you may receive the following error message: Automatic connection to the following team project failed: <project_name> on server <tfs server>. MORE INFORMATIONHotfix InformationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem. To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website: http://support.microsoft.com/contactus/?ws=support Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
(http://support.microsoft.com/contactus/?ws=support)
Note To download this hotfix, you can also visit the following Microsoft website: Download this hotfix rollup package from the Microsoft Connect website
(http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31858)
PrerequisitesTo apply this hotfix, you must have Microsoft Visual Studio Test Professional 2010 or Visual Studio Team System (VSTS) 2010 installed. Restart requirementYou have to restart the computer after you install the hotfix if the affected files are being used.Hotfix replacement informationThis hotfix package does not replace any other hotfixes.File InformationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Collapse this table
PropertiesArticle ID: 2387011 - Last Review: November 4, 2010 - Revision: 4.0
| Article Translations |
Back to the top
