Advertisements

SQL 2005 Managment Console is really really slow, fix

One of the biggest things we noticed with SQL Server 2005 was that the Management Studio took for ever and a day to start up. Well I finally ran across this blog which explained why. This really worked for me! It used to take 1 min to start up and now it takes 1 sec!

http://blogs.msdn.com/euanga/archive/2006/07/11/662053.aspx

This is not the answer to all occurrences of the issue but try the following;

* Shut down SSMS.
* Go into IE, select Tools|Internet Options|Advanced
* If “Check publisher’s certificate revocation” under the security node is checked, then uncheck it.

Now try SSMS again, was it faster? Either way re-check the setting to be safe.

Ok so here is what is happening. SSMS has a high percentage of managed code, all of this code is signed when we ship it. At start up (if this setting is checked) the .Net Runtime tries to contact crl.microsoft.com to ensure that the cert is valid(there were some fake certs issued in Microsoft’s name a while back so this is a very valid concern). If there is no internet connection or there is a problem contacting the certificate revocation list server then this will delay SSMS startup.

Advertisements

ESX A general system error occurred: The system returned an error. Communication with the virtual machine may have been interrupted.

Find this post interesting? Do you like interesting things? Maybe you would like my invention, a connectible candle called a WickBrick!

Get one here http://wickbrick.etsy.com/

WickBrick

So I went to start up a Virtual machine and it wouldn’t start up.

The error I got was

A general system error occurred: The system returned an error. Communication with the virtual machine may have been interrupted.

Oh great I’m thinking, this is the same error that the R2 bad patch was causing.

Well I narrowed it down to a problem with ESX1 and yet other machines could start virtual machines just fine.

After a bit of searching I found a command to restart the management service on the ESX server.

Logged on to ESX1

Then typed

service mgmt-vmware restart

Saw the service restart, and now I am able to start virtual machines just fine.

Another Amelia Photo Shoot :) Rocking Chair