3rd party software causes LCOTP.exe to fail
|Date:||27 February 2007|
|Product/Release:||Any LANSA application or product using the local LANSA listener|
|Abstract:||LCOTP.exe job fails immediately after connecting to local listener due to 3rd party LSP DLLs|
|Submitted By:||LANSA Technical Support|
When making a SuperServer or LANSA Open connection to a Windows host (either to your own local PC or a remote host), the Listener launches LCOTP.exe which immediately fails. This can happen, for example, when executing a WAM in the XSL Editor against your own PC as the backend host for testing purposes.
The error is sometimes highlighted with return code 28 (x'1C') with associated error
Error:10038 CPIC Error:28 in recv
It is possible for 3rd party software to install DLL's which intercept and manipulate all data sent over a network. These DLLs are technically known as Layered Service Providers (LSPs). LSPs can be installed by any software but common uses are for network card drivers, malicious software (malware and spyware) and file sharing programs. It has been found that incorrect, missing or corrupt DLLs can cause problems to other programs (including LANSA) which need to send data over the network. Multiple LSPs can exist on a PC. In this case, they are processed as a chain.
There are utilities available which detect if a problem exists with an LSP or an LSP chain. These tools performs a basic check to ensure the LSP DLL exists. ie. the tool detects problems in your LSP chain. If it detects a problem it displays the problem DLL and offers the user the choice to correct the LSP chain. LANSA does not provide a utility to check and correct defective LSP chains. However, some tools are freely available for download from the internet and can be easily found by searching with the term "LSP fix".
Note: Using such LSP correction utilities is a non-LANSA activity and should be used with care. LANSA makes no guarantee, implied or otherwise as to the effectiveness or suitability of any LSP correction utility and cannot be held responsible for any system corruption caused by the use of an LSP correction tool.
If a problem LSP DLL is found, contact the software vendor responsible for that DLL. If you have installed any new software recently, check if any updates are available for that software.