Error connecting LANSA Client V11.3 to deployed Windows LANSA application
|Date:||30 August, 2007|
|Product/Release:||Visual LANSA V11.3|
|Abstract:||Even if your application is deployed with LANSA Client support, LANSA Client may display an error message when attempting to create a new query|
|Submitted By:||LANSA Technical Support|
After deploying your LANSA application with LANSA Client support, LANSA Client may not be able to run queries against this application. You might be able to connect but you will receive an error when you try to create a new Query. A typical error messages might be:
(0042) - Unable to load/locate OBJECT ACCESS MODULE (OAM) DC_F12
This can be caused by:
- Missing DEF_CLT definitions on the Deployment PC
- Absence of LANSA Client OAM DLLs in the deployed application
Or possibly a combination of both, so if you are receiving this error you should check both possibilities.
- Ensure that you import the DEF_CLT definitions on the
Deployment PC prior to building the package.
- Include all of the OAM DLLs as Non-LANSA objects in the
package. The OAMs
that must be included are:
These DLLs should be deployed to the System Execute directory.