odbc progress openedge wire protocol driver

I'm thinking this is a session issue, but I wouldn't know where to begin fixing it. The reason for all this is that not many people access the Progress database via ODBC/JDBC and SQL92 - the vast majority uses the native ABL ( 4GL ) interface to talk to the Progress database. There's no sp_reconnectlinkedserver, and I can't replicate this issue outside the job running the individual procedures works when the database gets back up. You either must do a complete or a custom installation and select the drivers manually. I attempted to call sp_dropserver, sp_addlinkedserver, and sp_testlinkedserver in quick succession, which does not throw an error, but the job thinks it successfully completes when it didn't. DataDirect ODBC Progress Wire Protocol driverConnection refused.

Msg 7303, Level 16, State 1, Procedure sp_testlinkedserver, Line 1Ĭannot initialize the data source object of OLE DB provider 'MSDASQL' for linked server 'PROGRESS_TEST'. I can execute sp_testlinkedserver and get an error, so I can detect WHEN it happens: OLE DB provider 'MSDASQL' for linked server 'PROGRESS_TEST' returned message 'Unexpected Network Error. OLE DB provider 'MSDASQL' for linked server 'PROGRESS_TEST' returned message 'Socket closed.'. OLE DB provider 'MSDASQL' for linked server 'PROGRESS_TEST' returned message 'Server crash likely.'. I get many multiples of these three messages:

job continues to not connect to Progress DB until manually disabled and re-enabled.I was testing connectivity issues when I ran into this problem: Every so often, a merging job runs on SQL Server to push the changes to the Progress linked server. To keep two tables across two servers in sync, we have a trigger that adds a change to a MergeTable.

Odbc progress openedge wire protocol driver