I just had a developer who had this same issue.

Turns out he was trying to open a SQL 2008 database with SSMS 2005.

He opened up SSMS 2008 and the problem went away.