I resolved the same issue by removing the "GO" statement at the very end of the query that was inserted automatically (usually hidden several line-breaks down).

[SQL Server 2012 SP1]