14 (0xE) Content Generator doesn't support required jack

Description

See also error 13. This error indicates that the ALP module that handles the resource pointed by the URL refuses to communicate with the ALP engine. 

Probable causes

This error like the error 13 is an indication for a configuration problem. These errors may happen if the ALP module needed for the URL processing has failed. Most often this error occurs when an alp.site or alp.application file is edited manually or replaced by inappropriate file in a mistake. When the ALP Settings shell extensions are used no configuration mistakes that would lead to this error or error 13 may happen.

Where to look for problems:

1. See the default alp.site file in the directory containing the core ALP DLL - iewebsrv.dll (Program Files\newobjects\ALP for installed versions or the CommonFiles directory in autoruns). Check the CONTENTGENERATORS section and see if there are any modules listed there. From ALP 1.2 the standard ALP modules are embedded in the ALP core and there is no need of any entry in this section in order to support ASP and CGI. If you have any entries remove them. In ALP 1.1 and earlier versions you must have 2 modules listed in the LIBRARIES subsection. If you are using ALP 1.1 or earlier and there are no entries better obtain a clean default alp.site file from the ALP distribution and replace the file.

2. Check the alp.site file that defines the Virtual ALP site for your application. Usually it should not contain any entries in the CONTENTGENERATORS section unless you use custom build ALP native extensions.

3. Check the alp.application and see if the CG module registered to handle the resource pointed by the URL is has correctly specified class name. If not sure about the name check the documentation for the class names of the standard ALP modules (see ALP modules in the help file index).

Our experience shows that this error is most often caused by replacing a default alp.site file by alp.site file that contains a DEVELOPER license. Remember the alp.xxxx files in the directory that contains the ALP engine binaries are not to be changed! The DEVELOPER license is imported in the Virtual ALP sites and applies to the virtual ALP site and not to the ALP engine as whole. This licensing behavior allows single copy of the ALP engine to run applications licensed by different vendors, so the default alp.site cannot hold a DEVELOPER license by design. If you have done so replace the alp.site file with a clean copy and put the license in the Virtual ALP site's directory where your application resides and not in the ALP engine's directory. The best way to avoid this is to use the ALP Settings shell extension to import the DEVELOPER license from the template file you have received from us into the Virtual ALP site of your application(s).