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

    OvP: cancelling hold produces "An unexpected error has occured."

    • Article Type: General
    • Product: Voyager
    • Product Version: 8.2.0

    Problem Symptoms:
    * Cancel hold in Primo MyAccount results in "An unexpected error has occured"

    Cause: is missing configuration for hold cancellation messages.

    1. Connect to Voyager server.
    2. cd /m1/voyager/xxxdb/tomcat/vxws/context/vxws/ui/
    3. Compare eng/ to exl_default/
    4. Reconcile eng/
    5. Be sure that request cancellation response messages are in eng/
    page.myAccount.reqPending.cancel.failure=Failed to cancel request.
    page.myAccount.reqPending.cancel.success=Request cancelled.
    6. Save changes.

    Additional Information

    eng/ messages can be customized. For that reason, at upgrade, this file is not overwritten, but must be updated from exl_default/ (similar to the way Tomcat WebVoyage skins must be updated at upgrade).

    See also Article #5365, "Upgrading Voyager and also have Primo?"

    Category: Interoperability (Voy) - Voyager

    Subject: Primo (Voy) - Voyager

    • Article last edited: 7/18/2014