Linked server error

Question

Linked server error

Jon Burnett

Valued Member

Points: 65
More actions
July 18, 2007 at 4:24 pm

#173851

I am getting the error message below when I try to include a table from a linked server I created.
Cannot initialize the data source object of OLEDB provider "IBMDASQL for linked server "AS400"
Does anyone know what to do about it?
Thanks.

Viewing 8 posts - 1 through 7 (of 7 total)

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

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 1

What is the RDBMS that you want to link to. IF DB2/ORACLE you need to have client compenents installed. IF sql server then you can use sql native client to create the linked server.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com

Jon Burnett Valued Member Points: 65 More actions · Answer 2

Thanks Sugesh. When you say client components do you mean IBMDASQL OLE DB provider, or are there more components needed? I am using linking to a DB2 database on an AS400.

Thanks again.

Sugesh Kumar One Orange Chip Points: 27311 More actions · Answer 3

Then you need install DB2 client components.

Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com

michael.sommer Grasshopper Points: 18 More actions · Answer 4

Hi,

did you solve this problem? I have the exact same problem on 2 sql server machines. On 3 other machines it is running fine. I have Client Access Express and the OLEDB providers installed on all machines. However on those two machines we run SQL Server Express Edition. Could this be the problem? (i thought sql server 2005 express would also support linked servers).

Regards,

Michael

Jon Burnett Valued Member Points: 65 More actions · Answer 5

I checked to see the the required iSeries components were installed on the server and they were, but the error still occurred. I had a theory that the problem may have been due to attempting to set up the linked server through management studio on my local computer rather than doing a remote logon to the server and setting it up there. I don't know if your situation is similar or not. What I finally ended up doing was writing a SSIS package to pull the data I need from the AS400 into a table in SQL server. It's slower but it got the job done.

michael.sommer Grasshopper Points: 18 More actions · Answer 6

Hi,

thanks for the reply 😉

What SQL-Server Edition are you using? I only have the Problem using SQL-Server 2005 Express currently. It works fine on Developer, Standard and Enterprise (on 64bit also). Maybe it has also something to do with installed Hotfixes.

Regards,

Michael

Jon Burnett Valued Member Points: 65 More actions · Answer 7

I'm running 2005 developer's edition. Like I said in my last post I think the problem was due to my not being directly on the server. I have had other set up issues that were resolved by my logging on to the server and executing the procedure from there.