SSMS 2012 crashes when opening new query on instance with Failover Clustering installed (not 2012 R2)

Question

Hi,
I'm trying to start a new query in SSMS, but every time I click the "New Query" button on the tool bar or open a new query window by Object Explorer -> right-click -> Script as -> New Query Editor Window, SSMS hangs with (Not Responding)
and has to be restarted.
I'm running SSMS 2012 (v11.0.3381.0) on Server 2012 6.2.9200. I'm connecting to the primary node of an AlwaysOn Availability Group, and SSMS is located on the primary node itself.
I'm aware of KB2908806, which describes the same symptoms, but this only applies to Windows 6.3.x. Is there an equivalent fix for 6.2.x, or another workaround?
EDIT: To confirm behaviour: "New Query" works intermittantly, Script as ... to -> New Query Editor Window always crashes.

Answer 1

Hello,
there are many reasons your SSMS process would "hang", including bad server performance or internal SSMS processes being suspended due to locking.
When you open a new query window, what your SSMS application does internally is to open a new connection to your instance. You could be experiencing problems in your instance that are causing the logon process to take too long.
How does the bad performance issue generally happen? Is it only happening by connecting to the instance in SSMS? Does the same problem happen when you attempt to connect through an application, or by any other clients?
What happens if you try to connect to the instance through a remote computer?
Check your server's resource monitor for resource usage. Do you see any counters which could indicate performance problems?
Please post the results of @@Version for your server.
Can you open Activity Monitor in SSMS? How many sessions are listed? Does it also take a long time when you first log into the instance in SSMS, before opening a new query tab? Is the SSMS hanging for all databases when opening a new query window, or just
for the ones included in the availability group? Have you tried to connect to your instance by using a DAC connection?
DAC: http://technet.microsoft.com/en-us/library/ms178068%28v=sql.105%29.aspx
Do you have any server logon triggers? Are there any traces running other than the default trace? What are your server specifications? How many logical cores does it have? Is it being used in a production environment? Is there any CPU or I/O affinity set
for the instance? Whats your min/max memory settings? Run DBCC MEMORYSTATUS and post the results here.
Are there any error messages in the SQL Server errorlog? Is your server dedicated to the SQL Server Instance?
Run this query and post the results:
SELECT * FROM SYS.dm_os_process_memory