dbaspot
Tags Register FAQ Calendar Search Today's Posts Mark Forums Read

Progress: ODBC Error When connection SQL Server OPENQuery - Other Databases

This is a discussion on Progress: ODBC Error When connection SQL Server OPENQuery - Other Databases ; Our company is using the DataDirect OpenEdge ODBC driver 10.1B as a interface between Progress and SQL Server. A linked server was created in SQL Server to connect to the ODBC driver The database developer had issued a query from ...


Home > Database Forum > Other Databases > Progress: ODBC Error When connection SQL Server OPENQuery

Reply

 

LinkBack Thread Tools Display Modes
  #1  
Old 10-05-2009, 10:23 AM
Database Newbie
 
Join Date: Oct 2009
Posts: 1
dan.damico is on a distinguished road
Default Progress: ODBC Error When connection SQL Server OPENQuery

Our company is using the DataDirect OpenEdge ODBC driver 10.1B as a interface between Progress and SQL Server. A linked server was created in SQL Server to connect to the ODBC driver

The database developer had issued a query from SQL Server SELECT * FROM OPENQUERY(linked_sever, 'select * from pub.tb')

It was determined several days later that this query was hung by noting in SQL Server that the user had cancelled the query and the wait time was still growing. Upon review the _sqlsvr2.exe was hung. The only way to free it up was to kill that process and then bounce sql sever to free it up.

The following error were reported by the database developer.

OLE DB provider "MSDASQL" for linked server " prog_dbconn " returned
message "[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver]Driver's SQLSetConnectAttr failed.".
OLE DB provider "MSDASQL" for linked server " prog_dbconn " returned
message "[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver][OPENEDGE]Broker rejects connection.".
OLE DB provider "MSDASQL" for linked server " prog_dbconn " returned
message "[DataDirect][ODBC Progress OpenEdge Wire Protocol
driver]Optional feature not implemented.".


The developer had mentioned something about the possibility that there may be data existing on the Progress database that is outside the the table/column specification. From what I understand Progress is not a strongly typed db so this can occur. I am wondering what the odds are that the ODBC driver is choking on data that falls outside of the schema definition trying to pull it out and return it to SQL Server

I am wondering if anyone has faced these error before and me able give some guidance.
Reply With Quote
Reply

Tags
datadirect, openquey, progress, sql server linked server

Thread Tools
Display Modes


Similar Threads

Thread Thread Starter Forum Replies Last Post
SQL Server Native Client is not supported on the current processor Database Administrator sqlserver-faq 14 06-25-2008 01:13 PM
SQL2005 UNC connectivity failing Database Administrator sqlserver-server 19 02-09-2008 01:03 PM
SQL Server 2005 SP2 update failed Database Administrator sqlserver-server 8 12-30-2007 04:12 PM
Re: KB927779 fails to install Database Administrator sqlserver-faq 0 12-12-2007 01:22 AM
store result of query in variable Database Administrator Oracle Server 6 12-04-2007 01:34 PM


All times are GMT -4. The time now is 12:12 PM.