dbTalk Databases Forums  

"Access denied" error using OpenQuery to a linked Analysis server

microsoft.public.sqlserver.olap microsoft.public.sqlserver.olap


Discuss "Access denied" error using OpenQuery to a linked Analysis server in the microsoft.public.sqlserver.olap forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
BI-DBA
 
Posts: n/a

Default "Access denied" error using OpenQuery to a linked Analysis server - 02-13-2004 , 02:39 PM






We have SQL Server 2000 and Analysis Services installed on the same
Windows 2000 server. In Enterprise Manager we have set up a linked
server to the Analysis Server. We execute the following OpenQuery
statement from a SQL job:

select * from OpenQuery(SALES,'select {[Date.All
Dates].[Year].members} ON ROWS, { [Measures].[Sales] } ON COLUMNS from
[SalesCube]')

We receive the following error:

"Executed as user: DOMAIN\SQLEXEC. OLE DB provider 'MSOLAP' reported
an error. Access denied. [SQLSTATE 42000] (Error 7399) OLE DB error
trace [OLE/DB Provider 'MSOLAP' IUnknown::QueryInterface returned
0x80070005: Access denied.]. [SQLSTATE 01000] (Error 7300). The step
failed."

The MSSQLSERVER and MSSQLServerOLAPService services use the same
domain login account (DOMAIN\SERVER). The SQL Server Agent is using a
different domain account (DOMAIN\SQLEXEC). Both domain accounts
(DOMAIN\SERVER and DOMAIN\SQLEXEC) are members of the OLAP
Administrators group on the server.

We have run this same OpenQuery statement from Query Analyzer and any
users with a SQL Login (sa, etc.) can run the OpenQuery statement
successfully. NT authenticated users receive the same "Access denied"
error as the SQL job.

Does anyone know why NT authenticated users (including the domain
account used by the SQL Server Agent) cannot access the Analysis
Server from the SQL Server?

Reply With Quote
  #2  
Old   
Dave Wickert [MSFT]
 
Posts: n/a

Default Re: "Access denied" error using OpenQuery to a linked Analysis server - 02-13-2004 , 09:26 PM






You should be able to do this.
Possibly there is a problem in the way you've configured the linked server.
See if you can follow the linked server example in Appendix F of the AS
Operations Guide.
http://www.microsoft.com/technet/pro...e/anservog.asp
Hope that helps.
--
Dave Wickert [MS]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"BI-DBA" <ronhippen (AT) hotmail (DOT) com> wrote

Quote:
We have SQL Server 2000 and Analysis Services installed on the same
Windows 2000 server. In Enterprise Manager we have set up a linked
server to the Analysis Server. We execute the following OpenQuery
statement from a SQL job:

select * from OpenQuery(SALES,'select {[Date.All
Dates].[Year].members} ON ROWS, { [Measures].[Sales] } ON COLUMNS from
[SalesCube]')

We receive the following error:

"Executed as user: DOMAIN\SQLEXEC. OLE DB provider 'MSOLAP' reported
an error. Access denied. [SQLSTATE 42000] (Error 7399) OLE DB error
trace [OLE/DB Provider 'MSOLAP' IUnknown::QueryInterface returned
0x80070005: Access denied.]. [SQLSTATE 01000] (Error 7300). The step
failed."

The MSSQLSERVER and MSSQLServerOLAPService services use the same
domain login account (DOMAIN\SERVER). The SQL Server Agent is using a
different domain account (DOMAIN\SQLEXEC). Both domain accounts
(DOMAIN\SERVER and DOMAIN\SQLEXEC) are members of the OLAP
Administrators group on the server.

We have run this same OpenQuery statement from Query Analyzer and any
users with a SQL Login (sa, etc.) can run the OpenQuery statement
successfully. NT authenticated users receive the same "Access denied"
error as the SQL job.

Does anyone know why NT authenticated users (including the domain
account used by the SQL Server Agent) cannot access the Analysis
Server from the SQL Server?



Reply With Quote
  #3  
Old   
BI-DBA
 
Posts: n/a

Default Re: "Access denied" error using OpenQuery to a linked Analysis server - 02-15-2004 , 08:56 AM



I am still getting the "Access denied" error even though I used
sp_addlinkedserver with MSOLAP.2 instead of "Microsoft OLE DB Provider
for Olap Services 8.0" from within Enterprise Manager.

I also changed the Data source on the linked server from the actual
server name to "localhost" and still got the error.

Any other ideas as to where the security breakdown is occurring?

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.