Post reply

Linked server "Catastrophic failure"; Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "server_name"

  • October 20, 2010 at 1:33 am

    #141196

    Hi, Some of the users report the following error message while using the openquery:

    Msg 7399, Level 16, State 1, Line 1

    The 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 1

    Cannot 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

  • September 13, 2011 at 7:47 am

    #1380636

    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 created works just fine (and still does), but when creating/recreating the linked server, it will not work.

    Our Tech Services department states "nothing has changed"...

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • September 14, 2011 at 7:02 am

    #1381264

    I had a similar issue occur as I was testing executing functions from MSSQL 2008R2 to a PostgreSQL 9 SQL database using a linked server connection. I unchecked the "Allow inprocess" option in the MSDASQL provider and all is well now.

    Cheers,

    Andy Obregon

  • September 14, 2011 at 5:06 pm

    #1381671

    Thanks, I'll have to check that...

    I found an article on an MSDN blog that said something along the lines of the mySQL DLL receives a PAGE ACCESS VIOLATION and craps out...and the only fix is to actually reboot the server completely.

    http://blogs.msdn.com/b/john_daskalakis/archive/2009/11/13/9921916.aspx

    Ironically, after doing just that, every linked server came out. Go figure!

    ______________________________________________________________________________Never argue with an idiot; Theyll drag you down to their level and beat you with experience

  • March 6, 2012 at 10:30 am

    #1455465

    I ran into a similar issue recently using OpenQuery to connect to an Oracle instance. The failure was being caused by comments being inside the string that was passed thru to oracle. While bouncing the SQL Server instance was still necessary, this at least gave us the knowledge of how to prevent the issue going forward.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply