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

    Error trying to connect to server: "Event not found."

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

    Problem Symptoms:
    An "Event not found" message occurs in trying to connect to the server, such as:

    setenv: Event not found or
    0: Event not found

    Cause:
    "Event not found" indicates a problem with one of the setenv lines either in $alephe_root/aleph_start or ./aleph_start.private.

    * In the case of "setenv: Event not found" one of the setenv's in aleph_start had been commented out using an exclamation mark ("!"). To comment out a line in a script such as this, a hash mark ("#") needs to be used.

    * In the case of "0: Event not found", the setenv was defective:

    setenv IP2_STARTUP_LIBS ... (should be SIP2_STARTUP_LIBS ...)

    (Note: The error should not prevent the performance of functions on the server unrelated to the erroneous setenv.)

    Resolution:
    1. Correct the erroneous aleph_start or aleph_start.private setenv line.
    2. Do:
    > source aleph_start
    or run aleph_shutdown/aleph_startup.

    Additional Information

    See KB 4112 ("Comment character in ALEPH tables") in regard to the use of "!" vs. "#" in commenting lines.**

    Category: System Management (500)


    • Article last edited: 10/8/2013