Error 7373 Linked Server
Contents |
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Administering » Kerberos SQL 2008 Linked Server to MSOLAP 11 posts,Page 1 of 212»» Kerberos SQL 2008 cannot initialize the datasource object of ole db provider msolap for linked server Linked Server to MSOLAP Rate Topic Display Mode Topic Options Author Message Greg GrowGreg Grow Posted linked server to ssas 2012 Thursday, April 23, 2009 3:24 PM Say Hey Kid Group: General Forum Members Last Login: Friday, October 7, 2016 11:31 AM Points: 702, Visits: 933
The Peer Prematurely Closed The Connection Linked Server
Can someone please help me with the steps to allow for the "Double Hop" scenario using Linked Servers to MSOLAP.Our Environment: Computer A - SSAS (SQL 2008 64bit, uses a service account for log on) Computer B - Has a Linked
The Ole Db Provider Msolap Has Not Been Registered
Server to Computer A (SQL Server 2008 Enterprise 64bit, uses a service account for log on) Computer C - My Desktop with SSMS to test the linked server (2008 Developer 32bit)When I open my SSMS session and connect to computer B to test the linked server it fails with the following error:"Cannot set the initialization properties for OLE DB provider "MSOLAP.4" for linked server.. etc... etc... OLE DB provider for linked server returned message "The following system error occured: The system cannot enable use of kerberos on the database server find the file specified." Error 7373Its interesting; if I log onto the host where the linked server is at with the same domain credentials, the test of the linked server works on the computer B host. And, it now works from my desktop computer C. Once I log off of Computer B, my computer C test begins to fail again. I am guessing that my credentials and profile is authenticating properly.The Windows Adminsitrators say that everything is set up correctly with Kerberos and SPNs, but I still am not sure since I am unable to test successfully. Not sure what to try next.Does anyone of have any lists or steps they used to get the double hop working from personal desktops?ThanksGreg G. Post #703643 AShehzadAShehzad Posted Thursday, April 23, 2009 9:52 PM SSC-Addicted Group: General Forum Members Last Login: Monday, April 4, 2016 1:44 AM Points: 434, Visits: 1,138 The 7373 error code may refer to any errors in the ole db provider itself. Also you may check that ports for your server (1434 and 2383) are listening proper locally and externally. =============================================================Atif ShehzadDBA Zin Technologies Post #703732 Greg GrowGreg Grow Posted Friday, April 24, 2009 9:29 AM Say Hey Kid Group: General Forum Members Last Login: Friday, October 7, 2016 11:31 AM Points: 702, Visits: 933 Thanks. I will have our network guy verify the ports are open. If I add Anonymous Users to the cube, they have access. I would imagine, th
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: OLE DB MSOLAP provider
Linked Server Error 7303
issues SQL Server > SQL Server Analysis Services Question 0 Sign the test connection to the linked server failed in to vote Im unable to create a link server to remote SSAS servers. Error Below. ole db provider sqlncli11 for linked server returned message login timeout expired TITLE: Microsoft SQL Server Management Studio------------------------------ "The linked server has been created but failed a connection test. Do you want to keep the linked server?" ------------------------------ADDITIONAL INFORMATION: http://www.sqlservercentral.com/Forums/Topic703643-146-1.aspx An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) ------------------------------ Cannot set the initialization properties for OLE DB provider "MSOLAP" for linked server "Source".OLE DB provider "MSOLAP" for linked server "Link Server Name" returned message "The following system error occurred: Key not valid for use in specified state. .". (Microsoft SQL Server, Error: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9d5bd9e0-c380-4a0f-bdab-857751c71fba/ole-db-msolap-provider-issues?forum=sqlanalysisservices 7373) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=7373&LinkId=20476 ------------------------------BUTTONS: &Yes&No------------------------------ I tried to creating a UDL file and I get this error.. Test connection failed becasue of an error in setting the window handle property. I tried reinstalling Driver .. no luck. Ensured that allow in process was checked in provider properties. Also checked SAC manager to ensure "allow to" and "allow from" link was set to true on source server. Oh ya... I was aslo able to create a test UDL on my XP workstation with no problem.. Any help much appreciated. Moved by Jens K. Suessmeyer -Microsoft employee, Moderator Thursday, February 26, 2009 8:55 PM Wrong forum (Moved from SQL Server Data Access to SQL Server Analysis Services) Tuesday, November 27, 2007 10:37 PM Reply | Quote Answers 0 Sign in to vote Ok – got this fixed by fine-tuning the Server 2008 inbound rules for ports 1434 and 2283 for all profiles.MattF Marked as answer by Darren GosbellMVP, Mode
SERVER - Linked server creation error: OLE DB provider "SQLNCLI11" for linked server returned message "Invalid authorization specification" October 3, 2015Pinal DaveSQL, SQL Server, SQL Tips and Tricks6 commentsOne http://blog.sqlauthority.com/2015/10/03/sql-server-linked-server-creation-error-ole-db-provider-sqlncli11-for-linked-server-returned-message-invalid-authorization-specification/ of the blog reader sent me the below mail. I always find that using linked server have been of concern and trouble at a number of places. So when the mail landed – well I was not surprised that there was a problem. It is common and hence the resolution for the same is also linked server common yet not discussed. So I thought this blog will bring the nuances that I thought was the resolution and which helped our blog reader.Hi Pinal, I have two SQL Server instances on same machine and I want to fetch data from each other. So I went ahead and created linked server. In SQL ole db provider Server Management Studio, Server Objects > Right-click, Linked Servers, and then selected New linked server. I gave the remote server name as SQL16NODEB\SQL2014 and “Server type” as SQL Server as shown below.While saving I got error as belowTITLE: Microsoft SQL Server Management Studio-------------------- The linked server has been created but failed a connection test. Do you want to keep the linked server? --------------------The OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" reported an error. Authentication failed.Cannot initialize the data source object of OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014". OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399)If I hit No, the linked server is not created. If I created Yes, linked server is created, but any query is failing with the same error.What should I do?Thanks,
and as expected, it failed with the same error.OLE DB provider "SQLN