Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

SSAS CUBE PROCESSING ERROR Expand / Collapse
Author
Message
Posted Wednesday, December 8, 2010 2:40 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, November 3, 2014 8:34 AM
Points: 85, Visits: 346
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.
Post #1032175
Posted Monday, December 20, 2010 9:17 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, August 15, 2014 8:03 AM
Points: 5, Visits: 74
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.
Post #1037242
Posted Thursday, January 13, 2011 3:33 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, June 27, 2013 9:57 AM
Points: 1, Visits: 48
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.
Post #1047626
Posted Thursday, January 13, 2011 4:38 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, November 3, 2014 8:34 AM
Points: 85, Visits: 346
I solved the problem by going to impersonation tab of my data source and providing my windows login username and password.
Post #1047664
Posted Friday, March 18, 2011 6:49 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, May 19, 2012 6:59 PM
Points: 2, Visits: 9
I just wanted to say thank for posting the answer which worked for me as well.
Post #1080775
Posted Wednesday, April 18, 2012 7:01 AM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Saturday, April 20, 2013 5:25 AM
Points: 211, Visits: 80
I grant sysAdmin to the NT AUTHORITY\NETWORK SERVICE And It worked
Post #1285618
Posted Monday, September 24, 2012 6:58 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Thursday, December 6, 2012 8:30 AM
Points: 879, Visits: 810
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
Post #1363463
Posted Wednesday, October 3, 2012 11:08 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Sunday, April 20, 2014 10:08 PM
Points: 30, Visits: 158
give sysadmin permissions to NT AUTHORITY\LOCAL SERVICE then it will work
Post #1368158
Posted Tuesday, October 16, 2012 1:22 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, October 20, 2014 9:30 AM
Points: 132, Visits: 588
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.
Post #1373491
Posted Sunday, October 28, 2012 3:58 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 28, 2013 11:26 AM
Points: 3, Visits: 1

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.
Post #1378061
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse