After a few minutes of working with SSMS 10.50.1600.1 on the console of a cluster node, against a clustered instance, it freezes and returns the error message below.
I ruled out a couple of organic mistakes I might have made, and read, on line, that the likelist solution was to repair ,NET 3.51. And it worked, for a while: the the problem returned.
A reboot will reactivate the SSMS; but it eventually hangs.
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: Ssms.exe
Application Version: 2009.100.1600.1
Application Timestamp: 4bb679e7
Hang Signature: 83f4
Hang Type: 256
OS Version: 6.0.6002.2.2.0.274.10
Locale ID: 1033
Additional Hang Signature 1: a9bd91c6f403a03867b55b9258208bb3
Additional Hang Signature 2: 655f
Additional Hang Signature 3: 1758037c539a8e30944d70e3c8fa8085
Additional Hang Signature 4: 83f4
Additional Hang Signature 5: a9bd91c6f403a03867b55b9258208bb3
Additional Hang Signature 6: 655f
Additional Hang Signature 7: 1758037c539a8e30944d70e3c8fa8085
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409