Re: Linked server error -- MIDRANGE-L

Thanks Jack. This last document you referenced helped us solve the
problem.

Dean

On Thu, 3 Mar 2011 10:57:27 -0500, in midrange.midrange-l you wrote:

Dean, check this document out, maybe some of this might help you out.

http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/d7cd7e4509cc894c86257280005c65dc?OpenDocument&Highlight=2,IBMDA400

On Thu, Mar 3, 2011 at 10:16 AM, Jack Kingsley

<iseriesflorida@xxxxxxxxx>wrote:

ok, so SSMS direct then to the DB2.

Curious, does it work if you pick something other than this specific

table

like a simple one maybe with 3-4 fields.

Does this field that won't display contain any special characters

maybe.

So you trying to display the data directly using SSMS and tools within

or using browser to hit SSMS.

On Thu, Mar 3, 2011 at 9:49 AM, <Dean.Eshleman@xxxxxxxxxxxx> wrote:

I apologize for not explaining where I see this error. This error

occurs

in SQL Server Management Studio as part of the setup of a linked

server.

When we try to expand the Tables folder underneath the linked server,

the

error occurs. It should list the tables in the libraries which we

have

access to. I have checked, and authority is not a problem from the

System

i side. We are trying to test the SQL Server Reporting Services
functionality against files on our System i. I actually have a copy

the document that you pointed me to. Unfortunately, that doesn't help
much.

Dean

On Thu, 3 Mar 2011 08:24:09 -0500, in midrange.midrange-l you wrote:

I found this link, looks like what your using uses active server

pages

and

cookies from what I read, I am more used to the ODBC connections.

I found this, looks like the catalog list is the key to libraries.

http://www-912.ibm.com/s_dir/SLKBase.nsf/0/c52e46013ce1ded286256a3b006a38c5?OpenDocument

What versions of I5/os are you using, IE8. Curious, have you tried

firefox

to access the data.

On Wed, Mar 2, 2011 at 4:53 PM, <Dean.Eshleman@xxxxxxxxxxxx> wrote:

We are using the IBM DB2 UDB for iSeries IBMDA400 OLE DB provider

which

means we aren't using ODBC. At least I'm pretty sure about that.

part

of configuring the linked server, you can specify a "Provider

string".

I

have some documentation that tells me how to fill it out with a

list of

libraries. I specify "Catalog Library List=MYLIB1,MYLIB2;".

I'm still not totally sure how it sets the library list on the

server

when

it makes the connection. I don't know if it uses the library list

from

the job description specified on the user profile or if it just

uses

what

I specified in the Catalog Library List.

Going back to the original error message,

The OLE DB provider "SQL Server" for linked server "(null)"

reported an

error. The provider did not give any information about the error.
Cannot fetch a row from OLE DB provider "SQL Server" for linked

server

"(null)". (.Net SqlClient Data Provider)

I'm a little surprised it has "null" when it references the linked

server

in the message. Is that a clue?

Dean

On Wed, 2 Mar 2011 16:07:57 -0500, in midrange.midrange-l you

wrote:

Are you coding the library list in the odbc or ??

On Wed, Mar 2, 2011 at 3:47 PM, <Dean.Eshleman@xxxxxxxxxxxx>

wrote:

Yes, the user has access to the library. They can get to

various

files

in

that library using DBU from their 5250 session.

Dean

On Wed, 2 Mar 2011 15:38:27 -0500, in midrange.midrange-l you

wrote:

Does the user have access to the library/schema though.

On Wed, Mar 2, 2011 at 3:19 PM, <Dean.Eshleman@xxxxxxxxxxxx>

wrote:

Yes, the user has access to some of the tables. The problem

we

don't

see any tables listed. I would expect it to list any tables

that

the

user

has access to. We did specify some libraries as part of the

Provider

string in the Linked server setup.

Dean

On Wed, 2 Mar 2011 15:10:13 -0500, in midrange.midrange-l you

wrote:

Does the user your using have access to the table etc.

______________________________________________________________________

Please note my e-mail address has changed

Confidentiality Notice: This information is intended only for

the

individual or entity named. If you are not the intended

recipient,

do

not

use or disclose this information. If you received this e-mail

error,

please delete or otherwise destroy it and contact us at (800)

348-7468

so we

can take steps to avoid such transmission errors in the future.

Thank

you.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

______________________________________________________________________

Please note my e-mail address has changed

Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient,

not

use or disclose this information. If you received this e-mail in

error,

please delete or otherwise destroy it and contact us at (800)

348-7468

so we

can take steps to avoid such transmission errors in the future.

Thank

you.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

______________________________________________________________________
Please note my e-mail address has changed

Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do

not

use or disclose this information. If you received this e-mail in

error,

please delete or otherwise destroy it and contact us at (800) 348-7468

so we

can take steps to avoid such transmission errors in the future. Thank

you.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

______________________________________________________________________
Please note my e-mail address has changed

Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.