This is actually documented in the RS knowledge base. I just ran across it
the other day. It says to check the option - no idea why. It also says to
check the Server Options and set Rpc Out value to True. This option will
enable the linked server to call a stored procedure.
Glad you got
Final update, hopefully.. As of this moment, IT'S WORKING!
The silver bullet in this situation was some option in SQL Server called
Allow inprocess. Not sure what this does exactly, but this option (in
Server Objects | Linked Servers | Providers | IBM.UniOLEDB) has to be
checked for SQL Server
Hi Kevin
They do the same thing in IIS. It is a security issue to restrict unauthorized
users from accessing greater functionality. I would suspect this is to stop
hackers being able to use SQL Queries to access the operating system and
carrying out malicious activities. This is probably
: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
Hi Kevin
It maybe permissions on other folders on that server. I would suspect that
OLEDB needs to hold data in a temporary area, that temporary area may not be
the same level of permissions on the box that is failing. Calling within
Firewall is disabled. Both on the same domain. Authentication is
configured for Both Windows and SQL Server Auth on both boxes.
Interestingly enough, Brian, absolutely nothing (related to OLEDB) shows up
on the Event Viewer. I agree with you that this is not likely a U2-specific
issue; the
But David, it works without the domain on that other box. (Oh, and the
server in this situation is an AIX box.) The client is simply trying to
recreate the connection that works on another box.
New information: The memory of the failing box has been expanded to 4G and
the customer has installed
Hi Kevin
It maybe permissions on other folders on that server. I would suspect that
OLEDB needs to hold data in a temporary area, that temporary area may not be
the same level of permissions on the box that is failing. Calling within
linked server may change where that temporary area is
I haven't tried linking the two SQL servers together, but that would be a
good test, wouldn't it?
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
] [ud] Unidata as a SQL Server Linked Server via OLEDB
But David, it works without the domain on that other box. (Oh, and the
server in this situation is an AIX box.) The client is simply trying to
recreate the connection that works on another box.
New information: The memory of the failing box has
AM
To: U2 Users List
Subject: Re: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
But David, it works without the domain on that other box. (Oh, and the
server in this situation is an AIX box.) The client is simply trying to
recreate the connection that works on another box.
New
New information: In earlier tests I was logging in to SQL Server using
Windows authentication. All queries with the linked server using
IBM/Rocket's UniOLEDB driver failed. Over the weekend the client set up my
user ID using SQL Server authentication, and the queries now work (on the
old server;
List
Subject: Re: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
New information: In earlier tests I was logging in to SQL Server using
Windows authentication. All queries with the linked server using
IBM/Rocket's UniOLEDB driver failed. Over the weekend the client set up my
user ID
-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Monday, April 19, 2010 7:23 AM
To: U2 Users List
Subject: Re: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
New information: In earlier tests I was logging
from Microsoft helps!)
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Haskett
Sent: Monday, April 19, 2010 7:57 AM
To: U2 Mail List
Subject: Re: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
Robert
Going back to something Colin said earlier, I've created the exact same
test.udl file on the desktop of both machines. The old machine lets me
connect to Unidata via the UniOLEDB driver just fine. The new machine does
not. I get an error:
Test connection failed because of an error in
Ping test reports identical IP addresses for the server name.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
I found the UniOLEDB.dll in C:\windows\system32. On the server that works
the version is 1.5.1.7211. On the server that does not work the version is
1.6.0.7276. I believe the two were at one time identical but the client
downloaded the latest-and-greatest from the RS website, which is why they
New information: I just learned that the Windows server where the UniOLEDB
connection is working is Windows 2003 *R2 Enterprise *SP2 whereas the
Windows server that is not working with UniOLEDB is Windows 2003
*Standard*SP2. My apologies for my earlier assertion that the two
servers were
Kevin:
We all __KNEW__ there was really a difference, just couldn't figure out
what it was. :-)
Bill
Kevin King said the following on 4/19/2010 12:55 PM:
New information: I just learned that the Windows server where
:07 AM
To: U2 Users List
Subject: Re: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
I found the UniOLEDB.dll in C:\windows\system32. On the server that works
the version is 1.5.1.7211. On the server that does not work the version is
1.6.0.7276. I believe the two were at one time
Hi Kevin
Are you putting the domain name in the username dn\user for the logon to
Unidata?
Regards
David Jordan
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
No, not on either box (the one that works vs. the one that doesn't). The
user ID and password are the Unidata user and password with no extra domain
decoration.
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
This is the only one of your errors that I've seen. It's been too long to
remember the exact cause but it was something silly like: bad dll version,
path in uci.config wasn't a proper UniData account, privilege file had the
wrong permissions (somehow changed to read only), etc.
Sorry I'm not much
Hi Kevin
I suggest you try with the domain and see if that works.
Regards
David Jordan
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
And just when I thought it was safe to go back in the water...
This issue is NOT resolved. My customer has found that there is ZERO way to
get the IBM UniOLEDB driver working in SQL Server. They had it working
temporarily using the Microsoft ODBC - OLEDB driver, but that's not working
100%.
I'm wondering if the problem might be the provider string in setting up the
SQL Server linked server. Looking at the IBM/Rocket documentation I'm not
seeing a single word about what this provider string is supposed to look
like. The client currently has this provider string for the UniOLEDB
When you say two systems, are saying two different hosts? If so, then
maybe it's the data source definition. Maybe the one that doesn't work
has the wrong IP, or username and password.
I'm wondering if the problem might be the provider string in setting up
the
SQL Server linked server.
statements or XML
SQL to export massive amounts of data.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Thursday, April 15, 2010 9:09 AM
To: U2 Users List
Subject: Re: [U2] [ud] Unidata as a SQL Server
Kevin;
I haven't connect UD to SQL server since version 6.0.12 so - hopefully - my
comments are dated. We had a VB app that connected using UniOLEDB. I had
some trouble with different versions - 1 would work with Access but not
Excel and another was the opposite. Setting up the connection
Thank you all for the insights; all information is appreciated.
Going back to the beginning, I have been told all along that the original
SQL Server connection works perfectly for my contact. However, when I RDP
to that server and try to run the exact same query, it fails with this
message:
Msg
By user do you also mean computer? It could be as simple as a wrong version
of UniOLEDB installed on the other PC. Of course, I'm assuming that you
still have to install the development kit/dll's to get everything to
work...
Colin
-Original Message-
From: Kevin King
Thank you all for
Well, no. If this other person RDPs into the box, authenticates into SQL
Server, and runs the query, purportedly it works. If I RDP into the box,
authenticate into SQL Server and run the exact same query against that
linked server, it fails with the message as shown earlier.
Permissions?? Do you have access to the uci.config file?
Terminal Server setup so that the UD development kit was installed for the
other user and not yours?
Try creating an empty text file on the desktop called testconnection.udl.
Then run it. You should get a Data Link Properties box. Make sure
I do have access to uci.config. Not sure how the IBM/Rocket drivers were
installed but there's been no indication that it would have been installed
only for a single user.
I'll try the testconnection.udl thing. Thanks for that.
-K
___
U2-Users
Colin, I got the connection string and while it tests the connection just
fine, when I try to use the connection in SQL Server the error is the same:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider IBM.UniOLEDB for linked server KTEST reported an
error. The provider reported an unexpected
Lettau
ERP Systems Manager
polkaudio
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Saturday, April 03, 2010 7:31 PM
To: U2 Users List
Subject: [U2] [ud] Unidata as a SQL Server Linked Server via
...@listserver.u2ug.org [mailto:
u2-users-boun...@listserver.u2ug.org] On Behalf Of Kevin King
Sent: Saturday, April 03, 2010 7:31 PM
To: U2 Users List
Subject: [U2] [ud] Unidata as a SQL Server Linked Server via OLEDB
I have a customer who is trying to configure a couple of SQL Server
instances
Well, that doesn't seem to be the problem. Here's what I'm getting:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider IBM.UniOLEDB for linked server PSI reported an
error. The provider reported an unexpected catastrophic failure.
Msg 7330, Level 16, State 2, Line 1
Cannot fetch a row from
We've worked out this issue.
It appears that - at least in this case - the OLE DB connection being used
by SQL Server was in fact using the ODBC data source as defined on that Win
box. The ODBC data source, however, was setup to connect to a specific
database (account) and SQL Server was
I have a customer who is trying to configure a couple of SQL Server
instances to access Unidata 7.1 on AIX via OLEDB by setting up Unidata as a
linked server in SQL Server. The exact same OLEDB (and ODBC) driver is
installed on both systems and is configured identically between the two.
One
40 matches
Mail list logo
