I used to get this a lot - same work around - close SSMS & reopen.

Patching SSMS to SP1 or 2 seemed to have stopped it happening.