Kbase P93223: 4GL code calling ADMProxy.ADMClient com-handle fails on AppServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/15/2005 |
|
Status: Unverified
FACT(s) (Environment):
Windows
SYMPTOM(s):
4GL code calling ADMProxy.ADMClient com-handle fails on AppServer
The automation server for <automation object name> is not registered properly. Please reinstall this server or try registering it again. (5893)
The automation server for ADMproxy.ADMclient is not registered properly. Please reinstall this server or try registering it again. (5893)
Same 4GL code runs ok from Procedure Editor
Using a third party product called ADMproxy
CAUSE:
The problem is with how the ADMProxy software registers itself. It is supposed to store its ProgId and CLSID registry keys under HKEY_CLASSES_ROOT AND HKEY_LOCAL_MACHINE. However, it is missing all the keys under HKEY_LOCAL_MACHINE.
When Progress call CLSIDFromProgID (which is the routine that fails when is called from the AppServer) that routine will look under HKEY_LOCAL_MACHINE if the process is running as SYSTEM. Since there is no ADMProxy keys under there the routine fails.
FIX:
Contact the company that makes this ADMProxy software. They need to fix their registration code.