Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph

     

    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Bad messages in Circ Logger, such as "Regular return, User denied permission ...

    Bad messages in Circ Logger, such as "Regular return, User denied permission ...

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    We see incongruous messages in the Circ Logger (z309), such as the following:

    z309_text .............Regular loan
    z309_data .............User name 11/06/2007 07:32 PM does not exist.

    z309_text .............Regular return
    z309_data .............User denied permission for function '01/22/200

    z309_text .............Late return
    z309_data .............Library not accessible.

    Resolution:
    In each case, the text of the ./error_eng/global message is being used when the text should be coming from the ./error_eng/circ_logger file:

    circ_logger: 0001 0000 L Regular loan, due date $1.
    global: 0001 0000 L User name $1 does not exist.

    circ_logger: 0003 0000 L Regular return, return date $1
    global: 0003 0000 L User denied permission for function '$1/$2'.

    circ_logger: 0006 0000 L Late return, Original due date:$1. Actually returned on: $2
    global: 0006 0000 L Library not accessible.

    It may be that this could occur if the system were unable to find any circ_logger file, but it seems that even when there is one it can happen....

    We have found that this problem occurs when the site has an $alephe_root/error_eng directory which is populated with obsolete versions of the error_eng files (see KB 8192-824), and the new circ_logger file is not included in this $alephe_root/error_eng directory. It seems that it should find the $aleph_root/circ_logger file in this case but for some reason is looking in the $alephe_root/global instead.

    The solution is to take the steps described in in the article " Customization of pc_b_eng and error_eng files in version 17-up **MASTER RECORD** " (KB 8192-824) , after which, the $alephe_root/error_eng/ will be pretty much empty and the system will find the $aleph_root/error_eng/circ_logger, as it should.

    Analysis for staff by Jerry KB Notes.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Bad gateway message in Web OPAC
      • Badly formed number" error in Linux, running multi-process batch job *MASTER*
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 18.01
      2. contype:kba
      3. Prod:Aleph
      4. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved