SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SSAS CUBE PROCESSING ERROR


SSAS CUBE PROCESSING ERROR

Author
Message
eobiki10
eobiki10
Old Hand
Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)

Group: General Forum Members
Points: 313 Visits: 369
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.
yulia.klimov
yulia.klimov
Grasshopper
Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)Grasshopper (15 reputation)

Group: General Forum Members
Points: 15 Visits: 75
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.
srivasuk
srivasuk
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 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.
eobiki10
eobiki10
Old Hand
Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)Old Hand (313 reputation)

Group: General Forum Members
Points: 313 Visits: 369
I solved the problem by going to impersonation tab of my data source and providing my windows login username and password.
salharris
salharris
Grasshopper
Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)Grasshopper (24 reputation)

Group: General Forum Members
Points: 24 Visits: 9
I just wanted to say thank for posting the answer which worked for me as well.
adelante326
adelante326
SSC Veteran
SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)SSC Veteran (221 reputation)

Group: General Forum Members
Points: 221 Visits: 80
I grant sysAdmin to the NT AUTHORITY\NETWORK SERVICE And It worked
FreeHansje
FreeHansje
SSCommitted
SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)SSCommitted (2K reputation)

Group: General Forum Members
Points: 1979 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
cooljagadeesh
cooljagadeesh
SSC Journeyman
SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)

Group: General Forum Members
Points: 94 Visits: 221
give sysadmin permissions to NT AUTHORITY\LOCAL SERVICE then it will work
richykong
richykong
SSC Veteran
SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)SSC Veteran (260 reputation)

Group: General Forum Members
Points: 260 Visits: 621
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.
rvenegasrico
rvenegasrico
SSC Rookie
SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)SSC Rookie (27 reputation)

Group: General Forum Members
Points: 27 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.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search