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

    Problem with Aleph 20.2 Version Check

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

    There is an error in the version 20 Aleph GUI, related to the version check. The version check should replace all updated GUI files, including the binaries of the currently opened modules. Generally this works fine, but after switching to a new minor release any open module will not be updated anymore. The distributed Version check replaces all ascii files, but the binaries of only closed modules.

    This error becomes apparent only after the switch to the minor release 20.2. When replacing files from a 20.1 GUI, the version check will work fine, but as soon as you upgrade to 20.2, the version check will have the above-mentioned malfunction.

    As a result of this, you can, for instance, after implementing the Aleph 20.2 Minor Release and doing "Push to Orders" in GUI Circ, get the message “Acquisition application is not currently running. Use the Application Toolbar to run Acquisition Application”. Even if you open the Acquisitions module in advance, the error still occurs and the record is not pushed over.

    See attached Word document.

    You need get a corrected Verutil.exe file. You will find it on our documentation center in the directory "Download Center" / "Service Packs".

    * Copy the file VerUtil.exe from the Documentation Center to your PC station's .\alephcom\bin directory. It will overwrite the existing VerUtil.exe file -- which is correct.

    * Then do Version Check to get the correct versions.

    IMPORTANT NOTE: It is not possible to distribute the Verutil.exe by the version check. You need to copy it manually to the alephcom/bin directory of every GUI pc.

    • Article last edited: 10/8/2013