LADD error messages

The following error messages which you may encounter on the LADD system are explained, with information on how to resolve the error and also on when to report occurrences of error messages to the Libraries Australia HelpDesk. These error messages are:

  1. Error – org.omg.CosNaming.NamingContextPackage.NotFound –IDL: omg.org/CosNaming/NamingContext/NotFound:
  2. Error – com.fdgroup.corba.CorbaException – Unable to get GSA
  3. Error – Timeout – The previous session has timed out or been disconnected by the server
  4. You have been banned because: no reason given: please contact your library for assistance
  5. Authentication declined: invalid username and/or password
  6. HTTP Status 500 – Internal Server Error
  7. Error – javax.servlet.ServletException – Update authorization status failed: ILL is already authorized
  8. Error – java.sql.SQLException – ORA-00933: SQL command not properly ended

  1. 1. Error –org.omg.CosNaming.NamingContextPackage.NotFound
    – IDL: omg.org/CosNaming/NamingContext/NotFound: 1.0

  2. clip_image002_006
    Description: While actioning requests within LADD, you encounter an error indicating unable to connect to ‘IDL’ or ‘ILDRMS’.
    Explanation: One of the processors responsible for the Requests functionality in LADD has encountered a problem and needs to restart. This error will occur if you attempt to action an item, navigate, or perform a search at the exact time the process is restarting. It should have no adverse effect on requests but, if you were actioning a request at the time you will need to check that the action processed correctly. This can be checked by looking at the audit details within the request.

    Reportable: Only if this error is being experienced for an extended period of time, or if when you attempt to go back into a request this error appears again.
    Solution: Use the left hand side menu or the top links to navigate away from the page that is displaying the error and attempt to action the request again.

  3. Error – com.fdgroup.corba.CorbaException – Unable to get GSA

  4. clip_image002_007
    Description: While performing a BibSearch within LADD, you encounter an error indicating unable to get ‘GSA’ or ‘CGSA’.
    Explanation: One of the processors responsible for the BibSearch functionality in LADD has encountered an error and needs to restart. This error will occur if you attempt to run a BibSearch at the exact time the process is restarting.
    Reportable: Only if this error is being experienced for an extended period of time, or if when you attempt another BibSearch this error appears again.
    Solution: Use the left hand side menu or the top links to navigate away from the page that is displaying the error and attempt to run the BibSearch again.

  5. 3. Error – Timeout – The previous session has timed out or been disconnected by the server

  6. clip_image002_008
    Description: You were logged into the system, and when you tried to work on a request the system displays a ‘Timeout’ error.
    Explanation: The system has timed out since the time you started using the system. This occurs when there is a delay between the time logged in and the time you complete the process you started. The default logout time is 1 hour of inactivity. However, this ‘Timeout’ error can also occur if you were performing an action in any screens in the LADD system at the exact point that one of the web processes went down.
    Reportable: Only if this error is being experienced for an extended period of time.
    Solution: Use the left hand side menu and select the ‘Logout’ icon, or select the hyperlink ‘here’ within the text line ‘please click here for a new session’.

  7. 4. You have been banned because: no reason given: please contact your library for assistance

    clip_image002_009
    Description: After entering in a barcode/password a Windows error box appears stating that you are banned.
    Explanation: This message indicates that you no longer have access to LADD.
    Reportable: Only if you have an active LADD account and this error message is able to be replicated.
    Solution: If you have an active LADD account, select the ‘ok’ icon and enter the correct barcode/password into the Login screen. If you do not have an active LADD account you should stop your attempts to login to the system.

Authentication declined: invalid username and/or password

clip_image002_010
Description: After entering in a barcode/password a Windows error box appears stating ‘authentication declined’.
Explanation: The processor which matches the barcode/password the user enters into the Login screen of the LADD system is unable to authorise the barcode/password entered by the user. If the incorrect barcode/password is entered this error will appear. Note: barcode/password must be entered in upper case.
Reportable: Only if you have an active LADD account and this error message is able to be replicated.
Solution: Select the ‘ok’ icon and enter the correct barcode/password into the Login screen.

6. HTTP Status 500 – Internal Server Error

clip_image002_011

Description: While logged into the system you encounter an ‘Internal Server Error’.

Explanation: This is a system error that can occur when the system ‘crashes.’ Several factors can contribute to this type of error.

Reportable: Yes immediately. Please cite: “Internal Server Error”.

Solution: There is nothing that can be done locally. The system has to be rebooted at the server.

7. Error – javax.servlet.ServletException – Update authorization status failed: ILL is already authorized

clip_image002_012

Description: You may encounter this error after you have just actioned a request.

Explanation: You have tried to do two actions too closely together before the first action was finished processing.

Reportable: No.

Solution: Allow the system time to process an action before performing another action. If you see this error return to the request you were working on to determine its current status and action it again as necessary.

8. Error – java.sql.SQLException – ORA-00933: SQL command not properly ended

clip_image002_013

Description: You may encounter this error when you attempt to open the Details view of a request.

Explanation: This error is due to the requesting location sending a request with a requested delivery method of ‘Requester provides additional description:’Web PDF”. This is not an IPIG standard and as such corrupts the request. This request is unable to be actioned any further.

Reportable: Only if the same requester sends a large number of requests with this incorrect requested delivery method.

Solution: Contact the requesting location and ask that they send through a new request with a valid IPIG requested delivery method ie ‘electronic mail’.