Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    "No template exists named patron-address-direct" (in general)

    • Article Type: General
    • Product: Aleph
    • Product Version: 21

    Problem Symptoms:
    An "XML/XSL errors" message appears when attempting to print reports, for example, the loan-report or cash-summary report.

    This is the detailed error message:

    Error at xsl:call-template on line 253 of file:/C:/AL500-21/alephcom/files/ASH50/PrintTemplates/eng/funcs-misc.xsl:
    No template exists named patron-address-direct
    Transformation failed: Failed to compile stylesheet. 1 error detected.

    Cause:
    If the /C:/AL500-21/alephcom/files/xxx50/PrintTemplates/eng/funcs-misc.xsl (on the PC) contains a call-template name="patron-address-direct" reference, then the funcs-address.xsl in this same directory needs to include the line:

    <xsl:template name="patron-address-direct">

    Resolution:
    1. Replace the xxx01 (or xxx50*) ./form_eng/funcs-address.xsl with the ./usm01/form_eng/funcs-address.xsl (which includes the "patron-address-direct" reference -- which the original version of funcs-address.xsl in the xxx50 form_eng did not).
    2. Run util i/6 to recreate the html.pck.
    3. Restart the GUI client.

    * If the xxx50 path_convert file lacks a redirect to the xxx01 form_eng, then the xxx50 form_eng is the active directory.

    Additional Information

    This was an intermediate step in the diagnosis.... In the C:/AL500-21/alephcom/files/xxx50/PrintTemplates/eng/funcs-address.xsl on your PC, change the:

    xsl:call-template name="patron-address-direct"

    to:

    xsl:call-template name="patron-address"

    (don't restart the client) and try running one of the problem reports.

    This worked, but since we couldn't find a way to prevent the funcs-misc.xsl generated on the PC from including "patron-address-direct" -- even when the ./form_eng/funcs-misc.xsl did not! --, this changed version would be overwritten every time a new html.pck was imported from the server. Thus, we implemented the solution described above.

    Category: Circulation (500)


    • Article last edited: 11/20/2014