I hit that too: it was a known bug in SSMS and Microsoft released an update that fixed it.