FIX: SSMS 2012 Object Explorer hangs when expanding Databases node on a server with many DBs

GOLDEN!

REPOST FROM:

http://connect.microsoft.com/SQLServer/feedback/details/768124/ssms-2012-object-explorer-hangs-when-expanding-databases-node-on-a-server-with-many-dbs

Posted by _rod_ on 11/2/2012 at 4:09 AM

 Found this workaround here. http://stackoverflow.com/questions/10970989/sql-server-management-studio-2012-hangs
Can confirm it has fixed the problem for me.
Content as follows:
I experienced this same problem: when accessing a remote server with the Object Explorer, SSMS would hang indefinitely. The Windows System Event Log would show DCOM error 10009 (“DCOM was unable to communicate with the computer MACHINE_NAME using any of the configured protocols.”).
The solution was to clear the MRU history and other settings from my profile. To do that:
Close any open instances of SSMS 2012     In Explorer, open “%AppData%\Microsoft\SQL Server Management Studio”     Rename the “11.0” folder to something else, like “11.0.old”     Open SSMS 2012
You’ll see that your MRU list has been cleared. You should then be able to re-enter your credentials and use SSMS as normal.
If everything works, you can delete the renamed folder. Otherwise, delete the new “11.0” folder that was created and rename the original one back to “11.0”.
I have no idea whether it’s actually the MRU list that’s causing this problem or if it’s some other profile data.
We were able to discover that SSMS is trying to make a DCOM connection over port 135 to the SQL Server (perhaps for SSIS, T-SQL Debugging, or something else). Our firewall was configured to block port 135. By opening the port in the firewall we were able to use SSMS (hence the reason it worked against local databases but not remote ones). Unfortunately, an open port 135 is an invitation for a lot of attacks, so that wasn’t a practical solution for us.

Leave a Reply

Your email address will not be published. Required fields are marked *