none
Attempt to Add/Edit Shared Step Hangs

    Question

  • I'm using MTM 2013 and have an issue adding or editing shared steps for my current project.  When attempting to add or edit a shared step, the window hangs and "not responding" is shown in the title bar of the window.  The only resolution is to 'X' out of MTM and restart it. 

    I'm able to add and edit shared steps from other projects I've worked on.  This problem exists for 2 of my projects.

    Any assistance in this issue would be greatly appreciated!

    Colin 

     

    Thursday, October 02, 2014 6:24 PM

Answers

  • Well I'm not sure if this makes any sense or not... but my shared step problem is now fixed.  I had previously changed my display settings to 125% as I wear bifocals and wanted a little bigger font.  I now have office glasses and today changed my display settings back to 100%.  I can now access shared steps without the hang.
    Wednesday, October 15, 2014 10:03 PM

All replies

  • Hi colinrw,

    Are there error message in the event viewer?

    First, please clear TFS cache and try again. (Delete cache folder which path like C:\Users\[alias] \AppData\Local\Microsoft\Team Foundation\5.0)

    Secondly, please use test it in other machine. If it doesn’t work too, I think there are something wrong in these team projects. You may post the issue to the TFS forum to deal with the team project’s error.

    If it works fine in other machine, please repair you VS and try again.

    On the other hand, you may enable tracing for MTM and share the log file on the OneDrive.

    # Enable Tracing for MTM

    http://blogs.msdn.com/b/gautamg/archive/2011/01/20/how-to-enable-tracing-for-mtm.aspx

    Best Regards

    Starain Chen


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Friday, October 03, 2014 6:54 AM
    Moderator
  • Thanks for the reply.  I am getting the following in the event log:

    Source: Application Hang, Event ID: 1002, Level: Error, Application Path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\mtm.exe

    I previously cleared my TFS cache.  There was a 4.0 and 5.0 folder.  Is that expected?  A coworker is able to access the shared steps in this project as well, so the project must be ok.

    I did a repair of VS, but working with shared steps still hangs.

    Thanks again!

    Colin

     






    • Edited by colinrw Friday, October 03, 2014 7:51 PM
    Friday, October 03, 2014 11:28 AM
  • Hi Colin,

    >> I previously cleared my TFS cache.  There was a 4.0 and 5.0 folder.  Is that expected?

    Yes, you need to clear the cache that in 5.0 folder. Did you mean you still have the issue if you clear the TFS cache?

    >> C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\mtm.exe

    What’s the detail error message that you get?

    >> A coworker is able to access the shared steps in this project as well, so the project must be ok.

    What’s the version of your coworker’s VS? Please try to update your VS to the latest version.

    On the other hand, as I previous said that please enable tracing for MTM and share the log file on the OneDrive.

    Best Regards

    Starain Chen


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, October 06, 2014 2:31 AM
    Moderator
  • Yes, the issue still exists after clearing cache.

    This event is logged after I terminated the MTM, so I'm not sure of its relevance:

    The program mtm.exe version 12.0.30723.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.

     Process ID: f1c
     Start Time: 01cfe2368cb71a8a
     Termination Time: 50
     Application Path: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\mtm.exe
     Report Id: 75ba2a3c-4e4c-11e4-aae0-463500000031

    Both my coworker and I are running the latest VS 2013

    Is the only way to enable tracing through registry files?  Also, do those instructions work for VS 2013?

    From the debugger, here's what I see in the output for mtm.exe while the process was hung:
    'mtm.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_32\Microsoft.T5e519c33#\5cbb9205b00c4e09297c2d43a1f360f2\Microsoft.TeamFoundation.Controls.ni.dll'. 
    'mtm.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\GdiPlus.dll'. Cannot find or open the PDB file.
    'mtm.exe' (Win32): Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\comctl32.dll'. Cannot find or open the PDB file.
    'mtm.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Net.22cc68a8#\3618a3d5e8743f72cb3b382d325a5587\System.Net.Http.WebRequest.ni.dll'. 
    'mtm.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_32\Microsoft.Vc1f536d8#\7f2a33f7eb60ec501a0f735a9f8c4367\Microsoft.VisualStudio.Shell.12.0.ni.dll'. 
    'mtm.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_32\Microsoft.CSharp\3a0cef3567ae6b5374b90fc83c2bdefa\Microsoft.CSharp.ni.dll'. 
    'mtm.exe' (Win32): Loaded 'C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Dynamic\c5d17a2b5ad107d4e37e20f05016367a\System.Dynamic.ni.dll'. 
    The thread 0x1658 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x2660 has exited with code 0 (0x0).
    The thread 0x1c80 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x26b0 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x6c8 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x22e0 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x20a8 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x26e8 has exited with code 0 (0x0).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    First-chance exception at 0x75BAC42D (KernelBase.dll) in mtm.exe: 0xE0434352 (parameters: 0x80070002, 0x00000000, 0x00000000, 0x00000000, 0x74120000).
    The thread 0x27dc has exited with code -805306369 (0xcfffffff).
    The thread 0x1c8c has exited with code -805306369 (0xcfffffff).
    The thread 0x1970 has exited with code -805306369 (0xcfffffff).
    The thread 0x237c has exited with code -805306369 (0xcfffffff).
    The thread 0x1b9c has exited with code -805306369 (0xcfffffff).
    The thread 0x2140 has exited with code -805306369 (0xcfffffff).
    The thread 0x1b7c has exited with code -805306369 (0xcfffffff).
    The thread 0x9bc has exited with code -805306369 (0xcfffffff).
    The thread 0x278c has exited with code -805306369 (0xcfffffff).
    The thread 0x153c has exited with code -805306369 (0xcfffffff).
    The thread 0x1dc0 has exited with code -805306369 (0xcfffffff).
    The thread 0x1740 has exited with code -805306369 (0xcfffffff).
    The thread 0x1850 has exited with code -805306369 (0xcfffffff).
    The thread 0x2774 has exited with code -805306369 (0xcfffffff).
    The thread 0xa08 has exited with code -805306369 (0xcfffffff).
    The thread 0x1508 has exited with code -805306369 (0xcfffffff).
    The thread 0x12bc has exited with code -805306369 (0xcfffffff).
    The thread 0x1260 has exited with code -805306369 (0xcfffffff).
    The thread 0x478 has exited with code -805306369 (0xcfffffff).
    The thread 0x15f0 has exited with code -805306369 (0xcfffffff).
    The thread 0x1868 has exited with code -805306369 (0xcfffffff).
    The thread 0x1e2c has exited with code -805306369 (0xcfffffff).
    The thread 0x17d4 has exited with code -805306369 (0xcfffffff).
    The program '[1408] mtm.exe' has exited with code -805306369 (0xcfffffff) 'Process was unresponsive and was terminated'.

    • Edited by colinrw Tuesday, October 07, 2014 6:53 PM
    Tuesday, October 07, 2014 6:15 PM
  • Hi colinrw,

    >> Is the only way to enable tracing through registry files?

    I don’t find other way to enable tracing.

    Are you have VS2012 installed? If yes, what’s the result if you open it in the MTM2012?

    Please open share step in the VS directly to check the result (Team Explorer=>type id and press enter).

    On the other hand, please uninstall VS2013 and reinstall it, then check the result.

    Best Regards

    Starain Chen


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, October 08, 2014 6:37 AM
    Moderator
  • I uninstalled and re-installed VS2013 and have the same issue.  Any attempt to access a shared step results in a hang condition.  I am able to access shared steps for this project directly from VS, but not MTM.

    Accessing via VS doesn't allow me to copy/past entire steps (and multiple steps) which I heavily use.  If there are additional suggestions, please let me know.

    Thanks!

    Colin



    Saturday, October 11, 2014 2:03 AM
  • I'm having the same issue and hope that someone can find a solution.
    Wednesday, October 15, 2014 12:19 AM
  • Well I'm not sure if this makes any sense or not... but my shared step problem is now fixed.  I had previously changed my display settings to 125% as I wear bifocals and wanted a little bigger font.  I now have office glasses and today changed my display settings back to 100%.  I can now access shared steps without the hang.
    Wednesday, October 15, 2014 10:03 PM
  • I am having the same problem.. not sure what was pushed out yesterday... but I can't debug anything... It crashes right way.... Please find a fix for this.
    Wednesday, October 15, 2014 10:12 PM
  • Hi LandLord323,

    Since the op’s issue has been solved by himself and you still have the issue, I think the reason is different. Please create a new thread for this issue, in the new thread, please provide the details below:

    1. What’s the result if you try it in another machine with same TFS?
    2. What’s the detail version of your VS?
    3. What are you tried to fix that issue?
    4. What the error message that you get? (Event viewer, MTM log)

    Best Regards

    Starain


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, October 16, 2014 1:38 AM
    Moderator
  • Unbelievable. I don't recall why my display was set at 125%, but it was. Changing it to 100% solved the problem. Thanks, Colin. 
    Thursday, October 16, 2014 9:41 PM
  • Great!
    Monday, October 20, 2014 6:14 PM
  • Wow, how freaking obscure. I just ran into this too. Wasted half a day diagnosing the problem before running across this. Now it's fixed for me too. Oy.

    Angela Dugan

    Monday, August 31, 2015 9:29 PM