locked
MTM Crashes when connecting to a particular TFS server RRS feed

  • Question

  • Hi,

    MTM repeatedly crashes on my machine when I try to connect to any project on our main TFS server.  Nobody else in the company reports this same issue, so seems like it's just my machine. However, I can successfully connect to a test TFS server.

    I'd installed VS SP1, and the following 2 hot fixes. I also uninstalled VS Test Professional and reinstall it, but nothing worked. Please HELP!

    KB2387011 - https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=31858

    KB2403277 -http://archive.msdn.microsoft.com/KB2403277/Release/ProjectReleases.aspx?ReleaseId=5157

    Here is one of the errors from Windows Event Log:

    The description for Event ID 0 from source VSTTExecution cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    (mtm.exe, PID 7804, Thread 1) Object reference not set to an instance of an object.Stack Trace ==> at Microsoft.TeamFoundation.Client.ProjectConfiguration.SharePointWebApplication.GetBaseUri()

    at Microsoft.TeamFoundation.Client.ProjectConfiguration.TfsWebSiteRelative.GetFullyQualifiedUri()

    at Microsoft.TeamFoundation.Client.ProjectConfiguration.ProjectPortal.get_FullyQualifiedUrl()

    at Microsoft.TeamFoundation.TestManagement.Client.Runtime.TfsServerExtensions.GetPortalForProject(Project project)

    at Microsoft.TeamFoundation.TestManagement.Activities.Centers.TrackCenter.UpdatePortalLink()

    at Microsoft.TeamFoundation.TestManagement.Activities.TestingCenterGroup.runtime_ActiveTfsProjectChanging(Object sender, EventArgs e)

    at System.EventHandler.Invoke(Object sender, EventArgs e)

    at Microsoft.TeamFoundation.TestManagement.Client.Runtime.ActivityRuntime.OnActiveTfsProjectChanging(ActivityRuntime activityRuntime, EventArgs eventArgs)

    at Microsoft.TeamFoundation.TestManagement.Client.Runtime.ActivityRuntime.Connect_Completed(Object sender, EventArgs e)

    at Microsoft.TeamFoundation.TestManagement.Client.Runtime.BackgroundInitializer`1.CompletedHelper()

    at Microsoft.TeamFoundation.TestManagement.Client.Runtime.BackgroundInitializer`1.CompletedHandler(Object sender, RunWorkerCompletedEventArgs e)

    at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e)

    at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg)

    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

    at System.Windows.Threading.DispatcherOperation.InvokeImpl()

    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)

    at System.Threading.ExecutionContext.runTryCode(Object userData)

    at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)

    at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Windows.Threading.DispatcherOperation.Invoke()

    at System.Windows.Threading.Dispatcher.ProcessQueue()

    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

    at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)

    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)

    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)

    at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

    at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)

    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

    at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)

    at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)

    at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)

    at System.Windows.Threading.Dispatcher.Run()

    at System.Windows.Application.RunDispatcher(Object ignore)

    at System.Windows.Application.RunInternal(Window window)

    at System.Windows.Application.Run(Window window)

    at Microsoft.TeamFoundation.TestManagement.Shells.WpfShell.SingleInstanceWrapper.Launch(String[] args, Boolean isFirstInstance)

    at Microsoft.VisualStudio.TestTools.Common.SingleInstance.SingleInstanceApplicationManager.Run(String appId, String applicationTitle, LaunchAction action, String[] args)

    at Microsoft.TeamFoundation.TestManagement.Shells.WpfShell.SingleInstanceWrapper.Main(String[] args)

      

    the message resource is present but the message is not found in the string/message table

     


    Thursday, October 6, 2011 4:04 PM

Answers

  • This is now fixed by emptying all of the cache data in and restart MTM: C:\Users\<your user account>\AppData\Local\Microsoft\Team Foundation

    • Marked as answer by Ngan Menegay Thursday, October 6, 2011 5:21 PM
    Thursday, October 6, 2011 5:21 PM

All replies

  • This is now fixed by emptying all of the cache data in and restart MTM: C:\Users\<your user account>\AppData\Local\Microsoft\Team Foundation

    • Marked as answer by Ngan Menegay Thursday, October 6, 2011 5:21 PM
    Thursday, October 6, 2011 5:21 PM
  • Thanks!!! This fixed my issue.
    Wednesday, September 26, 2012 5:01 PM