December 8, 2010 at 2:40 pm
I am new bie trying to learn SSAS. I have these errors in trying to process my cube after it has shown to have deployed successfully. I need help.
1. OLE DB error: OLE DB or ODBC error: login failed for user 'NT AUTHORITY\NETWORK SERVICE.; 28000; cannot open database "AdventureWorksDW2008R2" requested by the login. The login failed.
2. Errors in the high-level relational engine. A connection could not be made to the Data source with the Data source ID of 'AdventureWorksDW2008R2', Name of 'AdventureWorksDW2008R2'.
3. Errors in the OLAP storage engine: An error occured while the dimension with the ID of 'Dim Date', Name of 'Dim Date' was being processed.
4.Errors in the OLAP storage engine: An error occured while the 'Date key' attribute of the 'Dim Date' dimension from the 'SSAS Project' database was being processed.
5. Internal error: The operation terminated unsuccessfully.
6. Server: The operation has been cancelled.
December 20, 2010 at 9:17 am
it seems that the SQL server that has your relational database has 'NT AUTHORITY\NETWORK SERVICE' rights wrong.
Go to your SQL server, expand security and then expand Logins, find 'NT AUTHORITY\NETWORK SERVICE', double click. See what roles it has, probably only public checked. Mark everything else. Since you set up 'NT AUTHORITY\NETWORK SERVICE' to be a default service account, you can give it more rights that public.
January 13, 2011 at 3:33 pm
I have the same problem. I have SQL 2008 installed on my local system. Created a windows local account and in SQL server added this account with sysadmin access.
I have changed the account in the analysis servesis services(configuration manager) to this account.
Now I am able to start and stop services but when I go nad try to process any dimension in SSAS I get the above error.
OLE DB error: OLE DB or ODBC error: Login failed for user '029W-8MS0CK1\srini'.; 28000.
Process failed.
Any suggestions appriciated
Thanks for reading.
January 13, 2011 at 4:38 pm
I solved the problem by going to impersonation tab of my data source and providing my windows login username and password.
March 18, 2011 at 6:49 pm
I just wanted to say thank for posting the answer which worked for me as well.
April 18, 2012 at 7:01 am
I grant sysAdmin to the NT AUTHORITY\NETWORK SERVICE And It worked
September 24, 2012 at 6:58 am
I am hi-jacking this thread. I have a similar problem as srivasuk described: I have a Windows global admin account under which all SQL Processen run. I receive the same cannot-login-failure, made this account explicitly member of the Windows Administrators group. Did not work, gave it explicitly SA role within SQL Server, still I receive this cannot-login-error.
Now, I can try one of the solutions given, but I would like to understand what is happening here. Also, it is policy here to use this specific global account for these services. In another, similar, SSAS setup this account gives no problem. Obviously there must be a difference, but I cannot find what that is.
Any other hints?
TIA
EDIT/SOLUTION: I found out that the datasources of the cubes where pointing to an alias, which is used on all servers of a specific OTAP que. This new server did not yet have this alias installed, hence the login failure. I am amazed however why I get this cannot-login-error, and not a cannot-find-server/alias...
Greetz,
Hans Brouwer
October 3, 2012 at 11:08 pm
give sysadmin permissions to NT AUTHORITY\LOCAL SERVICE then it will work
October 16, 2012 at 1:22 pm
This error is caused by the Data Source connection not having access into the OTLP database. Connect to your SSAS instance and verify the connection string of your data source is accurate. Make sure to update the Security Settings to use the proper Impersonation Info. The impersonation info defines what credentials to use to connect to the data source, independent of who triggers the processing.
Most likely, your Analysis Services is running under 'NT AUTHORITY\NETWORK SERVICE' and your impersonation settings is set to Run As Service Account. In production environments I've worked in, we usually create a windows service account that runs Analysis Services and grant that service account read access to the underlying data sources. In dev environments, I just run the service under my credentials or just set the data source to use my credentials by using Impersonate Account.
October 28, 2012 at 3:58 pm
Thanks - yulia.klimov, your answer below is still helping people. It solved my problem running the basic tutorial using AdventureWorksDW2008R2_Data.mdf
yulia.klimov (12/20/2010)
it seems that the SQL server that has your relational database has 'NT AUTHORITY\NETWORK SERVICE' rights wrong.Go to your SQL server, expand security and then expand Logins, find 'NT AUTHORITY\NETWORK SERVICE', double click. See what roles it has, probably only public checked. Mark everything else. Since you set up 'NT AUTHORITY\NETWORK SERVICE' to be a default service account, you can give it more rights that public.
January 28, 2013 at 3:42 am
Got into the same problem on my Dev machine. For me the solution was simple,
1. Goto Services.msc
2. Select SQL Server Analysis Services (sql2012) ("Your Instance") -> Properties -> Log On -> Added my Username and Password.
3. Bingo :w00t: Process the cube.
January 28, 2013 at 11:27 am
Thanks - I will try that - where is the services.msc file?
Ramón
January 28, 2013 at 11:30 am
Never Mind - it is just the Services app. Thanks.
March 1, 2013 at 12:04 pm
None of the above solutions is working for me.
I too get the error, as below, when I try to deploy the standard 'Adventure Works DW 2008R2'
"Error 22 OLE DB error: OLE DB or ODBC error: Login failed for user '<username>' .; 28000; Cannot open database "AdventureWorksDW2008R2" requested by the login. The login failed.; 42000"
I downloaded the 'Adventure Works DW 2008R2.abf' and installed via SSMS by connecting to an analysis services server instance and doing a database restore.
I copied the .abf file to
C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
and restored the database from there and called it 'AdventureWorksDW2008R2'. That was all fine.
So, once the database was restored to my analysis server this was the view in SSMS. See attached SSMS - SSAS AW Db image.bmp.
I then created an Analysis Services project in BIDS, by importing an existing SQL Server Analysis Services database (namely AdventureWorksDW2008R2). The wizard completed without errors.
I then do a deploy of the project and get 20 Warnings and 14 errors and the deploy failed.
The impersonation information is set to my username and password. I am an administrator on the server.
If I go to 'connection manager' the server name defaults to localhost and the 'connect to a database name' defaults to a list of databases within the local database engine, which does not include 'AdventureWorksDW2008R2' as this database resides within the Microsoft Analysis Server only.
Both the Microsoft Analysis Server and the Microsoft database engine are local and I have sysadmin rights on the engine too.
I dont have an 'NT AUTHORITY\NETWORK SERVICE' login user. I do have a NT AUTHORITY\SYSTEM and this login has the sysadmin role and makes no difference either.
SQL Server Analysis Services (MSSQLSERVER) via Services.msc is running as me too - no problem.
The only services that are not running is SQL Server Agent (MSSQLSERVER) and SQL Server Browser. The agent I have the rights to start but the browser I don't. I haven't attempted to start either as I have had no indication that they would have any effect.
This is a very frustrating problem as it means you cant use the product at all. I have been trying fix it for 2 days now. Grrr!
Please someone enlighten me.
March 1, 2013 at 7:03 pm
Hey Anthony.
There's a couple questions before I can give you a good answer.
If you are trying to deploy and test the Adventure Works analysis services database, you need to make sure you the analysis services database AND the Adventure Works DW SQL database.
Once you have both the analysis services database AND the SQL database restored, you need to make sure the Data Source connection is set up correctly and pointed to the SQL database.
When you import the Analysis Services database in BIDS, make sure you set the deployment properties of the project and point it to the server you want to deploy this too. Also make sure you verify the Data Source connection is valid and the impersonation is set to a login that has access to the SQL database.
To deploy, make sure you have access on the Analysis Services server and I'd recommend trying to deploy using the Analysis Services Deployment Wizard (Start>SQL Server> Analysis Services> Deployment Wizard). Follow the wizard and be sure to choose to Not Process. If you get an error at this point, it's probably because you don't have access to the Analysis Services server you're trying to deploy to.
Once the Analysis Services database is deployed, connect to it through SSMS. Open up the data source and check again to make sure the connection is valid and is using the impersonation information. Right click a dimension and Process Full.
I've noticed that the data source has to be verified/updated after deployment, especially if you're using a login. Initial deployment through BIDS seems to attempt to deploy and process which may fail the deployment if the data source needs updating.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply