Oledb Catastrophic Error
Contents |
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's unexpected catastrophic failure linked server On Home » SQL Server 2005 » Administering » Linked server
Enable Pre-fetch Of Data For Queries
"Catastrophic failure"; Cannot... Linked server "Catastrophic failure"; Cannot initialize the data source object of OLE DB provider cannot fetch a row from ole db provider msdasql for linked server as400 "MSDASQL" for linked server "server_name" Rate Topic Display Mode Topic Options Author Message sqlstart wannabesqlstart wannabe Posted Wednesday, October 20, 2010 1:33 AM SSC Rookie Group: General Forum msg 7330, level 16, state 2, line 1 Members Last Login: Tuesday, March 4, 2014 9:04 AM Points: 29, Visits: 107 Hi, Some of the users report the following error message while using the openquery:Msg 7399, Level 16, State 1, Line 1The OLE DB provider "MSDASQL" for linked server "_remote_server" reported an error. The provider reported an unexpected catastrophic failure.Msg 7303, Level 16, State 1, Line 1Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "remote_server".I dont think we have a problem with the connecter since other users can fetch data using openquery.Could anyone help me on this?Many thanks,sqlstar Thanks,sqlstart Post #1007500 MyDoggieJessieMyDoggieJessie Posted Tuesday, September 13, 2011 7:47 AM SSCarpal Tunnel Group: General Forum Members Last Login: Monday, October 17, 2016 8:25 PM Points: 4,754, Visits: 7,338 Did you ever get a reply on this or find a solution?I am experiencing a similar problem. We have a report that selects from an OPENQUERY to a mySQL box...it's been working for the better part of 3 years but just started failing this past Saturday night. The error is:The OLE DB provider "MSDASQL" for linked server "MYSERVER" reported an error. The provider reported an unexpected catastrophic failure.Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "MYSERVER". (Microsoft SQL Server, Error: 7399)What's most bizarre is the System ODBC DSN that was cr
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: The provider reported an unexpected catastrophic failure SQL Server > SQL Server Data Access Question 0 Sign in to vote For a very long time we extract data from a linked server without any issues. We use a scheduled DTS package to call a stored procedure which in turn is doing a bulk copy from the linked server. The linked server 'AAA' is MSSQL 2005 SP2 and the server which is doing the extraction is SQL2000 SP unknown at this stage. For http://www.sqlservercentral.com/Forums/Topic1007500-146-1.aspx a while now we get the following error: "The OLE DB provider "AAA" for linked server "AAA" reported an error. The provider reported an unexpected catastrophic failure. Error source: Microsoft OLE DB Provider for SQL Server " Later on the error may turn into the follwoing: "Error string: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. Error source: Microsoft OLE DB Provider for SQL Server " https://social.msdn.microsoft.com/Forums/sqlserver/en-US/053ae332-e200-422c-8513-e6cf57f96ea2/the-provider-reported-an-unexpected-catastrophic-failure?forum=sqldataaccess We did not changed network security, nor usernames or whatever. It just stared to happen. Together we may get a "locked" error message. We do run Redgate to try and trace this error to no avail. The only way to resolves this error is to restart both servers. Any help would be appreciated - this is getting too much now. Pierre Monday, September 27, 2010 11:28 AM Reply | Quote Answers 0 Sign in to vote Please provide ERRORLOG files from all SQL Servers that participate in transaction. Please also check if any additional SQLDump*.* files exist in the LOG folder. If they do please also provide access to them.Once we have this data we'll be able to troubleshoot the root cause of the problem. "SQL Server does not exist or access denied" is returned when either SQL Server process can not be contacted (e.g. it is not listening on the port or not running at all) or when authetication fails. ERRORLOG file would help us pinpoint the exact point of issue. Marked as answer by Ai-hua Qiu Wednesday, October 06, 2010 8:25 AM Monday, September 27, 2010 9:40 PM Reply | Quote Moderator M
Start 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 Stack Overflow the company Business Learn more about hiring developers http://serverfault.com/questions/477003/if-i-select-more-than-15-fields-i-get-catastrophic-failure or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server https://bugs.mysql.com/bug.php?id=29242 Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top if I select more than 15 fields, I get catastrophic failure up vote 3 down vote favorite Using sql server 2012 linked server I am connecting to a linked server with Pervasive SQL on it. When I do select * or select field1,field2,field3....field15 I am getting this error: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "MSDASQL" for linked server "KSLAP208" reported an error. The provider reported an unexpected catastrophic failure. Msg 7330, Level 16, State 2, Line 1 Cannot fetch a row from OLE DB provider "MSDASQL" for linked server "KSLAP208". I feel like there is some kind of oledb catastrophic error memory issue? It will not allow me to select more than a certain amount of data? whereas if I select a small amount of data select field1,field2 it works without problems. What am I doing wrong? sql-server database sql linked-server tsql share|improve this question asked Feb 8 '13 at 19:28 l--''''''---------'''''''''''' 1482726 Suggest that you address this to the DBA SE group for better response. –mdpc Feb 8 '13 at 20:21 Is the problem related to the number of columns you select or to one particular, problematic data type? IOW, using your example, perhaps the driver has a problem with the data type of field3 and SELECT field1,field2,field4 ... might work. Does SELECT field3 by itself work OK? –darin strait Feb 10 '13 at 16:30 @darin that is a wonderful point; however, after testing this, i am confident that it is not a data type issue –l--''''''---------'''''''''''' Feb 10 '13 at 19:50 2 Check the logs on KSLAP208. –Falcon Momot Feb 10 '13 at 20:00 2 @EvanAnderson im glad you feel my pain. what a piece of crap. not to say that i would be able to do any better, but it's frustrating that any application would pick pervasive to be their rdbms provider. you have to be a complete moron –l--''''''---------'''''''''''' Feb 10 '13 at 20:05 | show 13 more comments 3 Answers 3 active oldest votes up vote 2 down v
Email Updates: Status: Closed Impact on me: None Category:Connector / ODBC Severity:S2 (Serious) Version:3.51.16 OS:Microsoft Windows (Server 2003) Assigned to: Bogdan Degtyariov Tags: catastrophic failure, linked server, msdasql, MSSQL, oledb View Add Comment Files Developer Edit Submission View Progress Log Contributions [20 Jun 2007 15:44] Sundar Raman Description: (This is a re-opening of issue 28221). When executing queries containing joins against large data sets, the following error is encountered: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "MSDASQL" for linked server "linkserv" reported an error. The provider reported an unexpected catastrophic failure. Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "linkserv". Once the error is reported, the only way to get the linked server to work again is to restart the SQL Server service. How to repeat: Steps to reproduce: Create a linked server on MSSQL using the version 3.51.16 driver. Run a query that expects to receive a larger dataset (for example 10k rows), but include a join between a SQL Server table and a linked server table. For example: select mssql.fname,mssql.lname,mssql.ssno,mssql.address1, mysql.fname,mysql.lname,mysql.ssno from sqlservertable mssql join linkserv...mysqltable mysql on mysql.ssno=mssql.ssno order by mysql.lname desc Run the query a few times (it may work for the first 2 or 3 times). Eventually a "catastrophic failure" is reported by the OLEDB provider. [20 Jun 2007 21:08] Tonci Grgin Hi Sundar and thanks for your report. It is not clear to me why you reported this to us instead of MS as error clearly states their provider died on their server. And suggested fix is to restart MSSQL server! Can you please explain this to me? [20 Jun