Kbase 16663: Error 4389 Intersolv ODBC driver 16bits + Local OID
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  5/10/1998 |
|
Error 4389 Intersolv ODBC driver 16bits + Local OID
Possible reasons of error 4389 to occur while using the Intersolv ODBC
16bits product with a LOCAL Open Interface Driver (OID) against a
LOCAL Progress database.
**********************************************************************
While configuring your (new) ODBC product and testing it against a
Progress database, you may receive the following error message:
> Remote connection has not been established or has been lost.
> (4389)
There are many reasons for that error message to occur. Some of them
are related to the settings needed by the Intersolv ODBC driver and
some others to the configuration requested at runtime for a Local OID.
**********************************************************************
1- General configuration to set for the Intersolv ODBC driver:
----------------------------------------------------------
- WINGATE.DLL has to be in the WINDOWS/SYSTEM, WINDOWS directory or an
other directory pointed by the PATH.
- The DLC environment variable has to be set at DOS level.
This environment variable is used by Intersolv to point to the
startup.pf and the progress.cfg files in the DLC directory where
you installed the Progress product on your PC.
e.g. DLC=C:\DLC
2- Configuration to set for a local OID:
------------------------------------
- WOIDRVR.EXE must be in the WINDOWS directory or in any directory
pointed by your PATH environment variable. This Executable is
usually located in the DLC\BIN directory of your Progress product.
You have then 3 solutions:
+ Include the DLC\BIN directory in your PATH.
e.g. PATH=%PATH%;C:\DLC\BIN
+ Copy the WOIDRVR.EXE in the WINDOWS directory.
+ Copy the WOIDRVR.EXE in the working directory of the application
that will call the ODBC driver (MS QUERY for instance) and
include the working directory in your PATH variable.
e.g. PATH=.;%PATH% (if this is not already the case)
- PROGRESS.INI must be in the WINDOWS directory or in any directory
pointed by your PATH environment variable. The progress.ini is
used by the WOIDRVR.EXE to have the correct Progress environment
at runtime. This file is usually located in the DLC\BIN directory
of your Progress product.
Here also you have 3 solutions:
+ Include the DLC\BIN directory in your PATH.
e.g. PATH=%PATH%;C:\DLC\BIN
+ Copy the PROGRESS.INI in the WINDOWS directory.
+ Copy the PROGRESS.INI in the working directory of the
application that will call the ODBC driver (MS QUERY for
instance) and include the working directory in your PATH
variable.
e.g. PATH=.;%PATH% (if this is not already the case)
Note: Regarding the configuration you have to set for a LOCAL OID,
copying the WOIDRVR.EXE and the PROGRESS.INI in the WINDOWS
directory is not recommended because it may cause some problems
to any other progress products installed on the same machine.
PS: Configuration issues for a REMOTE OID that induce the same error
message are clarified in some other Knowledge Base entries regarding
the Operating system under which the OID/OIB is running.
Sebastien Haefele
(17 Feb 1997)
Progress Software Technical Support Note # 16663