This was a real head scratcher, and like many others who have run into this, I spent MANY hours digging through trace logs, event logs, dump files trying to figure out what the heck was going on. It ended up being a really obscure issue with Text Display size.
Anyway, let’s back up. The issue I am describing is one where from within the Microsoft Test Manager client you attempt to open a Shared Step – either from a test case or from the Shared Steps Manger. In either scenario, the shared step opens and before the actual steps load MTM greys out, you see the spinning blue circle of doom, and see the dreaded (Not Responding) message in the title bar:
Somewhere in the distance, a sad trombone plays softly… I was seeing this issue across multiple versions of MTM, multiple operating systems, and against multiple TFS instances. But not everyone was seeing it. Only certain people with a wide variety of versions, update levels, and OSs. So I dig through the event log, looked at MTM trace logs, dump files from the Task Manager, repair MTM, clear cache files, etc. No change.
Then I turned to the MSDN forums. After about 45 minutes of reading unrelated posts about various ways to hang up MTM, I finally ran across this. I though “No way! It couldn’t be something that obscure”. But I tried it, and lo and behold MTM stopped hanging. Truth be told I don’t even remember changing the text size, but I must have. It’s so weird that this is the only thing it seemed to have hosed for me.
In case you’re seeing something similar and like me could not remember where the heck to make that change, right click the desktop and choose Screen Resolution then go to Make Text and Other items Larger or Smaller:
Make sure you choose smaller - 100%, and perhaps buy some bifocals because now we are going to go blind trying to read tiny, tiny font. Be sure to log off and then log back in like the operating system tells you to.
Now everything works as expected. I worked from home the next day, and CANNOT reproduce the issue. Making me wonder if it is because at home I do not have a second monitor. But other people running in second monitors cannot repro. Oy.
I have been working with the MTM product team to try to figure out the root cause, as this has been hard to pin down. I have a number of people who have different OS, MTM, and TFS versions, some of whom also run MTM in a second monitor – and ability to repro is inconsistent ::HEAD DESK:: If you feel like trying to reproduce this issue, leave me a comment and let me know what happened for you, and your OS/MTM/TFS version, if your text size is 100% or not, and if you are using a second monitor. Would love some more data points to throw at the debugging efforts.