Kbase 19053: Openlink does not work if Progress installed remotely
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
19/01/2000 |
|
Openlink does not work if Progress installed remotely
SUMMARY: Openlink does not work if Progress installed remotely
Knowledge Base number: 19053
Creation Date: 23-Aug-1999
Author: Enrique Birlanga
This document applies to: Progress DB and Openlink Driver V3.2.
Version and Release Number: Progress DB V8.3A and 9.0B
INTRODUCTION:
This knowledgebase is for informational purposes only. Progress does
NOT SUPPORT Openlink. This kbase will try to explain why Openlink
does not work on a remote installation with a Progress DB. For any
problem that you may encounter, you should contact Openlink for
assistance.
STEP BY STEP DETAILS:
Many customers that uses Progress, may perform a network installation
in order to have all the Progress executables on the network and
avoid local installations.
It has been detected that when running the Progress executables from
the network, Openlink is not able to connect its agents to the
Progress DB returning the error 53.
unable to get server handle for generic_pro83a (error 53)
This is a vague error returned by Openlink that most of the times
indicate wrong settings or bad configuration into the Openlink
settings.
This has been proved to work with the same installation locally
instead of the network.
An issue has been logged with Openlink and they are investigating
the issue. Web#2661.
A workaround to this problem is to have PROMSGS & PROCFG in the
oplrqb.ini set to a local path. You may copy the files Promsgs and
Progress.cfg locally on the machine where the Request Broker is
running.
Additional investigations (RWE 18-01-2000) show that for Progress versions 8.2x and higher and Progress versions 9.x on Windows Openlink's database agents read the Progress
environment variables from the registry and if the Progress environment variables it finds there are still pointing to a mapped network drive (tested with Netware) the failure
debugging info will return error 53. The solution is to remove that registry entries completely to force Openlink's database agents to read the progress.ini or change them manually
to point to the environment on the local disk.
EBI (23-AUG-1999)
Progress Software Technical Support Note # 19053