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

    Server failed to execute request after nn seconds", "Remote Service Error (98)"

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20, 21, 22, 23

    Description:
    You get the message in some GUI function:
    "Remote Service Error (C1020 text 98) Server failed to execute request after nnn seconds" (where "nnn" is a number like 50 or 200).

    Resolution:
    This message indicates that the server was taking too long to respond: either because there was an unusual amount of other activity competing with this transaction or because this transaction itself was requiring an unusually large amount of resources.
    If the transaction is being performed at a busy time, you may want to try it at a less busy time....

     

    The error occurs when the processing time exceeds the  $alephe_root/pc_server_defaults/PC_SERVER_TIMEOUT:

    setenv PC_SERVER_TIMEOUT nnn  .


    You may want to increase the value. The only downside is that "bad" transactions -- transactions which are looping, etc. -- can run even longer. In general, such transactions are relatively rare.
    v16 rep_change 1270 (KB 9107) suggests that PC_SERVER_TIMEOUT not be set higher than 600 (10 minutes).

    Two specific functions where we have seen this problem are the approval of large invoices and the display of long loan lists. The Knowledge Base has a variety of other cases of “server failed to execute” in specific cases.

    Another cause could be a missing Oracle index for a record which the transaction is reading or writing. You can check this with UTIL-A-17-14. If an index is missing, use UTIL-A-17-2 to build it.

    • Article last edited: 10/8/2013