WAMs – Known reasons for Unable to Transform Input XML

Date:November 2007
Product/Release:LANSA for the Web (WAMs) - V11
Abstract:Known reasons for error 'Unable to Transform Input XML'
Submitted By:LANSA Technical Support

WAM applications fail and the browser displays error message:

Unable to Transform Input XML

Known reasons for this error:

  • WAM has not been compiled or the compile failed. A successful compile is indicated by a green tick next to the WAM in the repository viewer. If a green tick is not displayed then the WAM must be recompiled.
  • A webroutine or Weblet used by the WAM has not been checked in or has not been published
  • When you create a WAM and compile, the objects are all created, but the layout is not included as part of a checkin/checkout by itself. The layouts need to be checked out as a separate object to the system running the WAM application.
  • Standard Weblets were not imported properly. Ensure the file std_keys.xsl exists in {lansa_root}/x_win95/x_lansa/x_{partition}/web/lansa/{technology service}/{language}. If the file std_keys.xsl does not exist in this folder, you should re-import the Weblets (via System Initialization)
  • New languages - When creating new languages for a partition, ensure that a partition initialization is done prior to creating WAMs to ensure the standard Weblets exist for the new language. This saves having to republish the WAMs.
  • Ensure the xsl.cache directory in the IISPlugin subdirectory allows security rights for the IIS anonymous user to write there. If this is the case, to resolve, give the user (IIS default user - usually IUSR_<machine name> user) write and modify privileges for this xsl.cache directory.
  • The XSL may need to be republished. Try republishing.
  • The XSL has not been created in the correct directory. Ensure that the XSL files have been written to the language directory for the partition.

For example:

{lansa_root}\WebServer\IISPlugin\xsl.cache\x_{partition}\web\lansa\{technology service}\{language}

Note: If there are separate systems, the {system}_{port} part will look different for different users depending on their IIS Plug-in configuration.

For example:

{lansa_root}\WebServer\IISPlugin\xsl.cache\{system}_{port}\x_{partition}\web\{provider}\{technology service}\{language}