Recently I came across following error while processing cube and after some research I was able to resolve this error. I thought its better to share the solution if someone come across same issue.
OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object 'TableName', database 'DBName', schema 'dbo'.; 42000.
If you come across such error then open SSMS instance which cube is using as a underlying relational database server. Go to "Security" folder and then Logins. If your SSAS services are running under "NT AUTHORITY\NETWORK SERVICE" user then double click on that user under Logins.
Under "Login Properties" window, click on "Server Roles" and select role "sysadmin". Click ok and you have resolved your issue. check again with processing cube.
OLE DB error: OLE DB or ODBC error: The SELECT permission was denied on the object 'TableName', database 'DBName', schema 'dbo'.; 42000.
If you come across such error then open SSMS instance which cube is using as a underlying relational database server. Go to "Security" folder and then Logins. If your SSAS services are running under "NT AUTHORITY\NETWORK SERVICE" user then double click on that user under Logins.
Under "Login Properties" window, click on "Server Roles" and select role "sysadmin". Click ok and you have resolved your issue. check again with processing cube.
Hello Dear i still got this error , do you think i have to edit something in the datasource properties
ReplyDeleteHey sorry for delay in reply, Check the user under which your SSAS services are running and use same steps which I have mentioned in my post for that user under which your SSAS services are running.
ReplyDeleteThis comment has been removed by a blog administrator.
DeleteA big thanks! I've been 4 hours trying to solve the error while processing my cube and finally I solved it with the advices you offered in this post. Really really thanks :)
ReplyDeleteReally Helpfull blog thanks men..
ReplyDeleteThis absolutely helped us. It's the user running the SSAS service on the server that contains the cubes themselves, rather than the service account running SSAS on the server containing the DB.
ReplyDelete