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. Error connecting to GUI: " Access denied for remote file"; global-90

    Error connecting to GUI: " Access denied for remote file"; global-90

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    1. Additional Information
    • Article Type: General
    • Product: Aleph
    • Product Version: 17.01

    Description:
    When you try to connect with the GUI to any database on a particular server, you get "Remote error global -90; access denied for remote file".

    When you try to connect to the Admin module to check permissions, you get the same error.

    Resolution:
    Is the "setenv security_path_g" in the alephe/pc_server_defaults (UTIL J-5) specified correctly? Specifically, if the alephe was copied from another server, was this security path changed to be correct for this server?

    Note: What you see in the security path is all the directories users have access to through the pc_server, separated by semicolons.

    If this is occurring in importing tables in trying to start the Cataloging client, then the directory to which you don't have access appears in another window behind the error window with the text "Transfer File, that begins Source Name: /alephnn/u5n_5/xxx01/pc_tab/cat". This directory is one to which you need to have access but don't.

    In another case, the "setenv security_path_g" had:

    setenv security_path_g "$TMPDIR;$FILE_TMPDIR;${ALEPH_MOUNT}/${ALEPH_APP
    _VERSION};${USER_MOUNT}/abc;"

    echo ${USER_MOUNT}/abc

    showed this:

    /aleph/prod//abc

    Note the double slash ("//"). This was because aleph_start had:

    setenv USER_MOUNT /aleph/prod/

    changing this to:

    setenv USER_MOUNT /aleph/prod

    and doing "source aleph_start" corrected the problem.

    Additional Information

    faq


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Error Code 173 Called Program File Not Found In Drive/Directory
      • Error creating patron record: "Patron ID Already Exists"
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 17.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