SSMS 10.50.1600.1 & ApphangB1

Question

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

Answer 1

Hello,

Now that you repaired .NET Framework. Would you consider to uninstall and reinstall the tools only?

Hope this helps

Regards,
Alberto Morillo
SQLCoffee.com

Answer 2

Have you checked the event log ?

---

FAQ
----
Regards,
Ahmed Ibrahim
SQL Server Setup Team
My Blog
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click "Mark as Answer" and "Vote as Helpful" on posts that help you.
This can be beneficial to other community members reading the thread.

Answer 3

Hello all,

This could be the issue when there are more than 32 logical processors. Try to start SSMS through command prompt with affinity 1 and it should work fine

start /affinity 0x00000001 C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe

Applying the kb mentioned below should fix the issue:

http://support.microsoft.com/kb/2733946

Please refer: http://support.microsoft.com/default.aspx?scid=kb;EN-US;2276255

Hope this helps

Don

 

Answer 4

Yes!  I used KB2276255.  This was a great response, Don.   I did it the day before you made your response, otherwise, I'm sure I could have used it.

And, Alberto, I did try to deinstall the tools, but the check box to do so was gray, perhaps because the tools, not being clustered, were needed by all the other instances.