I prefer Windows authentication, and had the same error with SQL Server Standard Edition because my Windows authentication login didn't have enough privileges ( was only 'public' role ) . So logging as "sa" and adding "sysadmin" role for my Windows account login solved the problem.