I realize this answer is a little late in coming, but I just ran into this same issue.
Strangely enough, the error seems to go away if I use SQL Server Authentication rather than Windows Authentication. If you don't have that as an option or that doesn't work for you, I suppose you'll need to resort to old fashioned SQL statements.