Msolap Reported An Error
Contents |
product team could not reproduce this item with the description and steps provided. A more detailed explanation for the resolution of this particular item may have been provided microsoft sql server error 7399 invalid authorization specification in the comments section. 1 0 Sign into vote ID 688668 Comments 6 the ole db provider sqlncli11 for linked server reported an error. authentication failed Status Closed Workarounds 0 Type Bug Repros 1 Opened 9/15/2011 6:37:19 PM Access Restriction Public Description When I try to linked server error 7399 Create the Linked Servey by providing proper values, selecting right Security Context, getting the following error "OLE DB provider 'MSOLAP' cannot be used for distributed queries because the provider is configured to cannot initialize the datasource object of ole db provider sqlncli11 for linked server run in single-threaded apartment mode." DETAILS ATTACH A FILE EDIT THIS ITEM Assign To Item can only be reassigned when it is active. Comments (6) | Workarounds (0) | Attachments (1) Sign in to post a comment. Please enter a comment. Submit Posted by Sri.SQLBI on 9/26/2011 at 3:28 PM Lisa,Its Working for us. Thanks for the wonderful support!TechMgr1,May be you dont have Right
Linked Server Error 7303
Perms on Server. Posted by Sri.SQLBI on 9/22/2011 at 10:21 AM Hi Lisa,Thanks for the quick response. It seems to work. I may not be able to fully test before Monday.I noticed one thing after created the Linked Server based on the Script provided, when you open the Server Objects --> Linked Servers -- >Click the Properties of the Linked Server created using the Script below, Nothing else you see other than Provider Information and Linked server Name, Is that expected ? Posted by TechMgr1 on 9/21/2011 at 2:47 PM I have similar issues. however when trying to connect based on the changes proposed by Lisa below. I get the following error.Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSOLAP.5" for linked server "LINKED_MYDB" reported an error. Access denied.Msg 7350, Level 16, State 2, Line 1Cannot get the column information from OLE DB provider "MSOLAP.5" for linked server "LINKED_MYDB". Posted by Microsoft on 9/21/2011 at 8:07 AM Hi Sri,Can you please test creating linked server using script such as below and let us know if it works,EXEC sp_addlinkedserver @server='test', @srvproduct='', @provider='MSOLAP.5', @datasrc='YourASServer\Instance', @catalog='YourASDBName'goI was able to create the li
27, 20120 Share 0 0 During a recent investigation I realised that a
The Ole Db Provider Sqlncli11 For Linked Server Does Not Contain The Table
number of people are using MSOLAP.x as the provider name the linked server has been created but failed a connection test for a linked server e.g. MSOLAP.4 when creating a linked server… e.g. EXEC master.dbo.sp_addlinkedserver @server invalid authorization specification sql = N'lsname', @srvproduct=N'msolap', @provider=N'MSOLAP.4′, @datasrc=N'servera\inst', @catalog=N'SSASDBName' /* For security reasons the linked server remote logins password is changed with ######## */ EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'lsname',@useself=N'False',@locallogin=NULL,@rmtuser=N'dom\user',@rmtpassword=‘########' etc https://connect.microsoft.com/SQLServer/feedback/details/688668/issue-while-creating-linkedserver-for-analysis-services If you do this and you then right click the Linked Server that is shown in the SSMS linked servers list and select properties then you will note thatSSMS displays the linked server as if it is a SQL providerlinked server. If you just script it then it will appear to https://blogs.msdn.microsoft.com/as_emea/2012/09/27/issues-with-using-msolap-x-provider-name-in-linked-server-definition/ be using the options that you chose originally. If you were to use processmonitor to check what it happening then you will also note that as well as checkson msolap from sqlserver.exe there will be activity done by dllhost for msolap.4. This is because the provider has defaulted to out of process because there is no provider called MSOLAP.4 in the SQL Server list of providers. From a sql server point of view the provider is called MSOLAP. Change the linked server to use MSOLAP. So long as your MSOLAP driver installation is correct on the SQL Server machine then it will pick up the latest MSOLAP driver. For SQL Server Analysis Server 2008 R2 this will be MSOLAP.4. It will then correctly use the provider in InProcess mode so long as AllowInProcess is set for the MSOLAP provider. e.g. EXEC master.dbo.sp_addlinkedserver @server = N'lsname', @srvproduct=N'MSOLAP', @provider=N'MSOLAP', @datasrc=N'servera\inst', @cat
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://stackoverflow.com/questions/25775913/linked-servers-access-denied-error-with-an-out-of-process-oledb-provider Stack Overflow the company Business Learn more about hiring developers or posting ads with http://sqlblog.com/blogs/marco_russo/archive/2006/10/05/using-msolap-as-a-linked-server.aspx us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up linked servers Access Denied error with an out-of-process OLEDB provider up vote 1 linked server down vote favorite I have an OLEDB for OLAP provider which I am trying to set up a linked server with. For some reason I cannot set the provider to run in-process (by checking the "Allow inprocess" option) as it uses some customized .NET assembly which SQL server seems to have problem to load (although I have run CREATE ASSEMBLY successfully). When I'm trying to run it as an out-of-process ole db provider linked server, I am getting the following errors: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "MSOLAP" for linked server "K2" reported an error. Access denied. Msg 7350, Level 16, State 2, Line 1 Cannot get the column information from OLE DB provider "MSOLAP" for linked server "K2". (Note the same error happens for Microsoft MSOLAP provider as shown above). Further tracing of the errors shown the Access denied error happens on a IColumnsInfo::GetColumnInfo() call which is after the query has been executed successfully. I have tried setting the permissions based on the following links: http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider.aspx http://www.sqlservercentral.com/articles/Linked+Servers/73794/ But those don't work. Just wonder whether anybody else has experienced this issue. sql linked-list denied out-of-process share|improve this question edited Feb 11 '15 at 4:32 AstroCB 7,680113261 asked Sep 10 '14 at 22:11 user3784740 62 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the p
Intelligence solutions with SQL Server. You can follow me on Twitter: @marcorus Using MSOLAP as a linked server I just faced the problem to connect an Analysis Services (2000 or 2005) to a SQL Server 2005 database using a OPENROWSET statement. If you face an "access denied" error (precisely, "The OLE DB provider "MSOLAP" for linked server "SERVERNAME" reported an error. Access denied.") the solution is to enable the "Allow inprocess" flag in MSOLAP Provider Options. You can modify provider option through SQL Server Management Studio, Server Objects / Linked Servers / Providers / MSOLAP, right-click and edit Properties. When you get a result for an MDX query, the resulting column names are composed by dimension+levels+property name, so if you would like a cleaner naming you can use the WITH statement to define column names in a fast way. E.G.WITH A (Customer, Product, Year, Sales ) SELECT * FROM OPENROWSET( 'MSOLAP', 'DATASOURCE=localhost; Initial Catalog=FoodMart 2000;','...[place here your MDX query]...' ) Published Thursday, October 05, 2006 8:32 AM by Marco Russo (SQLBI) Comment Notification If you would like to receive an email when updates are made to this post, please register here Subscribe to this post's comments using RSS Comments rotik said: Thank you very much,that was very helpful for me. September 14, 2010 10:54 AM Leave a Comment Name (required)* Comments (required)* Remember Me? Submit About Marco Russo (SQLBI) Marco Russo is a consultant, writer and trainer specialized in Business Intelligence with Microsoft technologies. He runs the SQLBI.COM website, which is dedicated to distribute resources useful for BI developers, like Integration Services components, Analysis Services models, tools, technical information and so on. Marco is certified as MCT, MCDBA, MCSD.NET, MCSA, MCSE+I. This Blog Home Email Links Syndication RSS 2.0 Atom 1.0 Recent Posts Analyze multiple EVALUATE statem