deployment of adventureworks cube fails: 'user does not have permission to create a new object in 'GARY-PC' or the object does not exist

Question

when I deploy adventure works cube it fails, and i get: user does not have permission to create a new object in 'GARY-PC', or the object does not exist. trying to process cube from adventureworks DW and having what seem like permissions issues (?). took following steps (i am using sql server 2008 R2 developer edition and VS 2008): 1 downloaded and successfully created adventureworksDW (2008R2) database from 2 successfully created Datasource and DSV for a cube with 2 fact tables and several dimensions. 3 Click deploy

I see the following 2 prompts Login: greyed out, can’t type anything here the password is required for the impersonation account of data source Adventure Works DW.

Now, Whether I enter a password or not, I get: Error 3 Either the 'Gary-PC\Gary' user does not have permission to create a new object in 'GARY-PC', or the object does not exist. 0 0

what objects is SSAS trying to create? are these objects in the relational database?

Answer 1

You have to add your user account as an administrator in the Analysis Services portion of the SQL server.

For some reason the database and the analysis services portion of the server do not share login information. The user you run Visual Studio under needs to have administrative access to the Analysis Services engine; this is the reason running as administrator works. The account you use to access the Database Engine is arbitrary.

• Right-click on the SQL Server Management Studio icon and then select "Run as Administrator"

• Select "Analysis Services" from the "Server type:" drop-down list in the "Connect to Server" dialog box, then click connect.

• Right-click on the localhost definition in the Object Explorer panel and select Properties.

• Click on Security in the left panel of the Analysis Server Properties.

• Click the Add... button and type your user name and click the Check Names button to make sure you typed it right. Then click OK.

• Click OK.

Note: This may not the most secure solution, but it enables not running Visual Studio as administrator every time and possibly opening up yourself to attack.