Kbase P9986: Errors 293 or 473 when deploying SmartObjects application with a Runtime license
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
FACT(s) (Environment):
OpenEdge 10.x
Windows
Progress 9.x
SYMPTOM(s):
Workgroup database license installed
Client Networking license installed
** "<file-name>" was not found. (293)
** "adm2/smart.p" was not found (293)
** "adm2/data.p" was not found. (293)
** "adm2/query.p" was not found. (293)
R-code file not located for "<procedure-name>". (473)
R-code file not located for "adm2/smart.p". (473)
CAUSE:
Development was done with ADM2 but the required files have not then been deployed to the installation; or the location where these files are has not been included in the PROPATH.
When deploying applications in a runtime environment (e.g. with a Client Networking license) that use the Version 9.x ADM2 technology, it is the Application Partner (AP) or Independent Software Vendor's (ISV) responsibility to ensure the end-user is supplied with the necessary ADM2 runtime support programs from the AP or ISV's development license.
These files are not installed with a runtime license such as Progress Client Networking. This is intentional. The ADM2 supported programs are shipped only with Progress development licenses (i.e. ProVISION, ProVISION Plus).
FIX:
To deploy ADM2 (run the Smart Object code) at the client site:
Copy over the ADM2 folder (under GUI for Windows NT and TTY for UNIX) from the development license to the appropriate directory on the client site.
For example:
(The Windows client machine has client networking installed)
1) Copy over the ADM2 folder (**%DLC%/gui/adm2) from the development license to the client machine into the %DLC%/gui/ directory or to the subdirectory of the client application. Make sure path is part of PROPATH.
2) Run the .r code
To compile ADM2 at the client site, follow these steps:
1) On development machine, encrypt and then copy the following files to the client machine:
%DLC%/src/adm2 (copy just the adm2 directory)
%DLC%/gui/get (**this file has no extension)
%DLC%/gui/set (**this file has no extension)
%DLC%/gui/fn (**this file has no extension)
%DLC%/gui/fnarg (**this file has no extension)
%DLC%/gui/adecomm (copy the directory)
2) Make sure to copy over the ADM2 folder into the "src" directory on the client machine. Keep the identical directory structure.
The last 4 files (get, set, fn, and fnarg) are needed at the client site in order to compile. You can put them anywhere provided they are defined within the PROPATH.
3) Use the -rx option when you compile with client networking.
4) After you compile, remove these files from the system (they are no longer needed).