When you deploy your SSAS project in SQL 2012 then you might hit the error below.
Error 26 OLE DB error: OLE DB or ODBC error: Login failed for user ‘NT Service\MSSQLServerOLAPService’.; 28000
The issue is SQL 2012 (denali) installation configured MSSQLServerOLAPService to start the Analysis Service but somehow the user is not created in Windows.
I solved this problem by changing the Log on as to Local System account.
About chanmingman
Since March 2011 Microsoft Live Spaces migrated to Wordpress (http://www.pcworld.com/article/206455/Microsoft_Live_Spaces_Moves_to_WordPress_An_FAQ.html) till now, I have is over 1 million viewers. This blog is about more than 50% telling you how to resolve error messages, especial for Microsoft products. The blog also has a lot of guidance teaching you how to get stated certain Microsoft technologies. The blog also uses as a help to keep my memory. The blog is never meant to give people consulting services or silver bullet solutions. It is a contribution to the community. Thanks for your support over the years.
Ming Man is Microsoft MVP since year 2006. He is a software development manager for a multinational company. With 25 years of experience in the IT field, he has developed system using Clipper, COBOL, VB5, VB6, VB.NET, Java and C #. He has been using Visual Studio (.NET) since the Beta back in year 2000. He and the team have developed many projects using .NET platform such as SCM, and HR based applications. He is familiar with the N-Tier design of business application and is also an expert with database experience in MS SQL, Oracle and AS 400.
Chanmingman's Blog 
Not so sure that *fixes* the problem… Having the same error myself and your “solution” is already applied on my end. (But not all solutions are made equal, I know. ;.) )
There is not problem with the service account of analysis services.
In fact the installer creates NT Service\MSSQLServerOLAPService service account under which the Analysis Services are running.
When you try to deploy the AdventureWorks OLAP samples, then by default the data sources are configured to impersonate service account. The problem is, tha for the service account “NT Service\MSSQLServerOLAPService” there is no login created in the SQL Server instance. You simply need to create a login fro the windows service account on SQL Server instance on which the AdventureWorksDW2012 sample database is running and grant such account at least read access to that db (db_datareader for example).
Then the processing will work correctly as the service account of SSAS will have acces to underlying data.
Thanks, Pavel. This solved my problem right away!
Very successful, granted to the user NT Service \ SQL Server MSSQLServerOLAPService in reading rights in the database and worked to process the cube.
thanks
Thanks a lot bro !!!
Thanks! I couldn’t get it to work as I granted access to the database to the wrong account (MSSQLSERVER) — then found your post and after adding MSSQLServerOLAPService and granting it read access it finally worked!
Thanks a lot.. It worked for me too.
Thank you very much. This worked for me, too!
Thanks☺
.
Thanks!!!!!!
sorry guys but how to create a login fro the windows service account on SQL Server instance ??
For example in SSMS, go to the Security/Logins and there create new login for the Account under which the SSAS instance is running. During creation of the login in the Login Properties dialog you can Map the newly clreated user to databases to whcich it should have access. There you can make the user member of the db_datareader role in the databases to allow full read rights.
Thanks, this fixed mine
Thanks
Ljubim te u dupe 😀 Hvala Thanks 😀
I solved this problem by changing the Log on as to Local System account and i start again all SQL-SERVER . THANKS for this help
Bueno el dato, funcionó
Thank you it worked and much better solution than the others