$ 0 0 Looks like it happens when i connect to SQL 2008 and 2012 instances, but with SQL 2005 instances it doesn't give the error. (In case this makes a difference in the bug search)