I usually see that error message if the user account that you are locally logged in with doesn't have access to the SQL Server. In our environment, each admin has two accounts. One account is for day to day activities (no admin access), the other is the admin account. To use the admin account we have to Ctrl+right click on the icon and choose "run-as". Then use the admin credentials. The SQL server seems to allow this.