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 attempting to override it with a path to a different account. That override apparently doesn't work so well. So we created a new ODBC connection that points to the right account and SQL Server is now able to use that linked server to pull information from the appropriate location.
On Mon, Apr 5, 2010 at 8:58 AM, Kevin King <[email protected]> wrote: > 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 OLE DB provider "IBM.UniOLEDB" for linked server > "PSI". > > "unexpected catastrophic failure"? > > -K > -- -Kevin http://www.PrecisOnline.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
