Linked server

I'm trying to connect to a DB2/400 v4r creating a linked server on the
Enterprise Manager of my MSSQL 2000 box, but i receive the following message
when i try to expand the TABLES node on the tree:
Error 7302: Could not create an instance of OLE DB Provide 'IBMDA400'.
OLE DB error trace [non-interface error: CoCreate of DSO for IBMDA400
returned 0x80040154]
The version of CA400 installed on the MSSQL box is V4R5M0.
ThanksGenerally the error is caused by the provider not being
registered on the machine or from not having the in process
option set for the provider.
For the provider options, if you go to the linked server in
enterprise manager, view the properties and select Provider
Options. Then make sure the Allow InProcess option is
selected.
-Sue
On Mon, 15 Mar 2004 10:55:36 GMT, "Fabio Benedini"
<f.benedini@.magconsulting.it> wrote:

>I'm trying to connect to a DB2/400 v4r creating a linked server on the
>Enterprise Manager of my MSSQL 2000 box, but i receive the following messag
e
>when i try to expand the TABLES node on the tree:
>
>Error 7302: Could not create an instance of OLE DB Provide 'IBMDA400'.
>OLE DB error trace [non-interface error: CoCreate of DSO for IBMDA400
>returned 0x80040154]
>The version of CA400 installed on the MSSQL box is V4R5M0.
>Thanks
>|||Thank you Sue,
I've applied your tip and now I don't get that message, but now when I try
to expand the Tables node, my Enterprise Manager seems to hang. I tried to
wait for over 20 mins but i had to close it from the Task Manager.
Could you give me an example of a working configuration of a linked server
to DB2/400?
Thanks
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:l8eb50dfufaqvf68ugecj8aagokm5pop0h@.
4ax.com...
> Generally the error is caused by the provider not being
> registered on the machine or from not having the in process
> option set for the provider.
> For the provider options, if you go to the linked server in
> enterprise manager, view the properties and select Provider
> Options. Then make sure the Allow InProcess option is
> selected.
> -Sue
> On Mon, 15 Mar 2004 10:55:36 GMT, "Fabio Benedini"
> <f.benedini@.magconsulting.it> wrote:
>
message
>|||If you install Client Access on the server, it will install
and configure the drivers and providers for the AS400 on the
SQL Server box so that you can use linked servers. You
should also make sure you have the client updated with what
whatever service pack level based on updates to the AS400.
There is a link to update this in the Client Access program
group - I think that's where it is, can't remember off the
top of my head. For data source, use the IP address of the
AS400. For provider string, you need to include the library
you are using, connect timeout setting and code page. There
is some documentation for the settings in the Client Access
help files. You'd set the provider string somewhat like:
InitCat=YourLibrary;CCSID=37;PCCodePage=
1252;
Data Source=xxx.xxx.xxx.xxx
Settings will depend on how your AS400 is configured. Again,
the Client Access help files have information on the
necessary connection string settings.
-Sue
On Mon, 15 Mar 2004 15:22:36 GMT, "Fabio Benedini"
<f.benedini@.magconsulting.it> wrote:

>Thank you Sue,
>I've applied your tip and now I don't get that message, but now when I try
>to expand the Tables node, my Enterprise Manager seems to hang. I tried to
>wait for over 20 mins but i had to close it from the Task Manager.
>Could you give me an example of a working configuration of a linked server
>to DB2/400?
>Thanks
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:l8eb50dfufaqvf68ugecj8aagokm5pop0h@.
4ax.com...
>message
>