SSAS: Deploying Cube OLE DB Error – Login Failed

Jun.12, 2007 in Business Intelligence, Geeky/Programming, SQLServerPedia Syndication

If you are deploying/building a cube in SQL Server Analysis Services (SSAS), and you get tons of errors, and littered throughout you see

OLE DB error: OLE DB or ODBC error: Login failed for user ‘NT AUTHORITYANONYMOUS LOGON’.; 28000.

You should take a look at your data sources, and on the impersonation tab, play around with the different options. Usually it is set to “Use the service account” or “default”. I have tried “Use the credentials of the current user” but got errors back when deploying saying that the impersonation method was invalid for processing. I have found that “Use a specific user name and password” works. As I sit and wait for the cube I just finally got to deploy to finish, I figured I would write this up in a post. Your mileage may vary.

Technorati tags: SSAS, SQL Server 2005, SQL Server Analysis Services

Tags: SSAS 2005

Simlar Posts

View Comments

Chfalcao

thanks for the info... some added detail though..

you get to the impersonation tab via opening the Datasource designer window, or via double-clicking on the data source on the project list.

I originally tried the properties of the datasource and couldnt find it there.
Ronald

Hi Steve,

Thanks for the post. It works for me.

Thanks
sreedhar

Nice one
Anonymous

Thank you! I encountered the same problem, previously I only tried using current user, but the error still existed, then I specified the username and it worked, though it was just the current user.
Anand

Thanks much - this worked for me too. Earlier, I tried changing permissions for NETWORK SERVICE from inside SQL Server Management Studio, but that didn't do it.
HJ

Cheers, it worked for me as well.
Nazeera Hanif

Thanks a lot, very good post...i had the same problem and it worked for me.
very helpful article...Thanks again.
Arghad Arnaout

Hi ...

Try to run the service as a user who has at least read access to the reporting database. ...

check the link:
http://technet2.microsoft.com/Office/en-us/library/2c87fa4b-5893-441b-af01-eca949bf52a81033.mspx?mfr=true
ZBethem

Props Steve!

This was killing me in figuring out how to get around this error. The "use a specific user name and password" worked. I will add for others finding this post, however, that the user name should be the windows username and not SQL server's. So, you'll want:

username=\

Thanks again!
CPDinesh

Hi Steve,

Nice post,i also had same problem and this article helped me to resolve it. thanks a lot..hv a grt time !

blog comments powered by Disqus

Business Intelligence, SQL, Geek, Music, Programming, and More!

Welcome to stevienova.com. This is my personal blog. I like to write about mostly geeky stuff (Programming, .NET, Microsoft, C#, SQL, Business Intelligence, iPhone, Apple, Mac, Networking, etc) and other stuff that I just run across and feel like posting up to the net!

stevienova.com

Homepage of Steve Novoselac