Your DSN setup isn’t obviously wrong but if it does not match a running database that is listening on port at that IP address then you will get this error. If you capture an ODBC trace of a working example, it might allow us to narrow it down a bit more, but we wouldn’t be able to give you an answer with any certainty if you’re no longer able to reproduce the issue. To name a couple examples, it could result from attempting to select a row that has been deleted, or some sort of issue converting the data from the value returned by the database to the type requested by the application. There are several stepping stones and stumbling blocks for a Progress newbie – which are mostly caused by the fact that the Progress database does not provide SQL92 connectivity out-of-the-box in a way you would expect it. You must log in or register to reply here. Toggle navigation Network Home Informatica.
|Date Added:||1 January 2018|
|File Size:||20.25 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Error – [DataDirect]ODBC Progress OpenEdge Wire Protocol driver]socket closed |
Here are my connection settings: I have a created a progresd To name a couple examples, it could result from attempting to select a row that has been deleted, or datxdirect sort of issue converting the data from the value returned by the database to the type requested by the application. Plus, if you did chose a “typical” installation you will wind up without the ODBC drivers being installed.
Thread starter Richard Briggs Start date Apr 9, The next useful thing that you could wirre to clarify the problem is to show the database configuration and demonstrate that you have a properly configured broker running and listening for connections on port I will take your pdotocol next time and try to capture a trace if I can catch the issue while it is occuring.
windows server – ODBC connection to OpenEdge B – Stack Overflow
Toggle navigation Network Home Informatica. The other day we got an error message which read: Tom Bascom 8, 2 19 Log In Sign Up. I am grateful for your help.
Posted by rpickett on 11 Feb 9: Sign up using Facebook. Informatica Network Knowledge Base.
The Progress OpenEdge Wire Protocol Driver
This affects security http: Whenever possible, capturing a snoop of the problem is also very helpful www. What’s new New posts New resources Latest activity. Hi, I have tried copying the database files from c: This document resolved my issue This document did not resolve my issue This document helped but additional information was required to resolve my issue.
People who viewed this also viewed. Look to the Progress.
The error went away after about 20 minutes and we were finally able to complete our loading process, but I have been asked by my team here at my company to investigate and find the root cause of this issue. This is the first progrses I have seen this error and the QAD guys checked the openlink logs and they didn’t see anything that would indicate any type of error from their end.
Connection Option Descriptions for OpenEdge Wire Protocol
I am not too familiar with OpenEdge and am more of an Oracle application guy, but I figured this would be the best place to post this issue. Resources Latest reviews Search resources.
Is your database really named TEMP? Could the data in your QAD databases have been changing while performing the load?