Comments on: An invalid schema or catalog was specified for the provider “MSDASQL” for linked server

By: IS Support

IS Support — Tue, 23 Feb 2010 20:57:00 +0000

The Google Gods are smiling on you. Thank You very much. The feature also works
on ProvideX databases. We thank you.

By: HadAProblem

HadAProblem — Mon, 04 Jan 2010 22:02:57 +0000

Thanks a lot. I was looking for this.

By: Milad Qamari

Milad Qamari — Thu, 03 Dec 2009 07:48:11 +0000

Thank you guys . It works great.

By: Sunshine Lewis

Sunshine Lewis — Thu, 12 Nov 2009 18:33:47 +0000

I’m not sure John. I have very little actual understanding of the problem despite trying to decipher books online.

By: John

John — Tue, 08 Sep 2009 15:43:22 +0000

Worked for me. Thanks for the tip. But I wonder.

I could change “level zero” back to 0 (off) and it would still work while on the server. Could it just be initializing MSDASQL on the server?

Testing from my PC, it didn’t work set to 0 from the client, but changing “level zero” again back to 1 fixed that problem as well.

By: Steve

Steve — Thu, 06 Aug 2009 12:58:58 +0000

Thanks for the tip. This saved me a lot of time.

By: Daniel

Daniel — Mon, 20 Jul 2009 15:53:00 +0000

Thanks. It works in our shop.

By: eric

eric — Tue, 31 Mar 2009 00:28:50 +0000

for others also researching this issue. you will come across an alternative notation like this: select * from LINKEDSERVER.DSNNAME..TABLENAME.

this seemed to work, but wound up throwing an access denied error from my remote server. not sure why as i can use the dsn from within a dts package without incident. i was not able to diagnose that and turned on the level zero switch and it works now. thank you!!

By: Angel Paz

Angel Paz — Wed, 18 Mar 2009 20:21:17 +0000

Tnanks a lot.. you really help me with my problem.. !!

By: Steve F

Steve F — Sun, 01 Mar 2009 17:59:26 +0000

This tip was helpful especially with having the linked server to work with a Excel spreadsheet through a ODBC DSN (MSDASQL).

Thanks!