469,271 Members | 876 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,271 developers. It's quick & easy.

Catastrophic failures with linked servers

(Config: SQLServer2005, MySQL5.0 and MySQL4.0 all running on
Windows2003 server)
I've created linked servers to my MySQL servers from SQL server, and
had no problem for several months. I was using the MySQL ODBC 3.51.12
Driver. I upgraded to the 3.51.14 driver and have started having
problems. Obviousyl the first thing I did was revert to the 3.51.12
driver, but things are still failing.

What happening is: my linked servers work intermittently now. There is
no rhyme or reason for it to stop working. Bet every time it fails, I
receive the following error:

Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "MSDASQL" for linked server "foo" 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 "foo"

I tried doing an ODBC trace and it did not dump anything useful (I
guess I knew that it wouldn't since ODBC trace is not tied to the
OLEDB provider). I'm using the MSDASQL provider for the linked server,
since it's the only one that works with MySQL.

I'm wondering if anyone else has had any similar experiences, and
worked around it in any way. When I first got these errors I just
rebooted the SQL Server, and things worked fine for a while (a couple
of months). Now nothing seems to work.

May 2 '07 #1
0 2457

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Raghuraman | last post: by
8 posts views Thread by Ootyguy | last post: by
3 posts views Thread by RandyMartin | last post: by
reply views Thread by Abyss7 | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.