When using NCIP to interact with a library management system (LMS), you may encounter errors. This guide describes common categories of NCIP errors. Note that the exact error text may vary depending on which LMS is being used.
If an NCIP error occurs, you will see a red banner across the top of the screen when trying to complete the related action.
To get more details about the error, click on “View audit trail.” Note that some errors are sent with messy formatting and extraneous text. Look for strings prefixed with “detail” or “type” to extract meaningful content.
Here is an example of a typical NCIP error displayed in the audit trail:
Please see the NCIP integrations page for more detail about each NCIP service and for links to NCIP configuration instructions for each supported library management system.
NCIP Client failed to call NCIP server or parse returned results. This error indicates that the system could not connect to your LMS at all. Verify that the NCIP information in your settings app is correct and that you are using HTTP or HTTPS as required.
Unknown partner (Alma). This-Alma specific error usually indicates that the Application Profile configured in settings in incorrect. Verify the correct profile name within Alma and update settings if necessary.
Unknown User. The user ID associated with the request could not be found in your LMS. Confirm that the user ID is correct and associated with a user account in your LMS.
LookUpUser Processing Error Scheme / User Authentication Failed (Alma). Set the Look Up User parameter to "no" for Require Authentication in your resource sharing partner.
Unknown user. The user ID associated with the request could not be found in your LMS. Confirm that the user ID is correct and associated with a user account in your LMS.
User is ineligible to borrow. The patron ID associated with the request does not have the correct privileges for a hold to be placed. Verify that your local circulation policies are configured to allow the hold.
Element rule violated (Sierra and Millennium). An "element rule violated" error is indicative of an issue with improper data being transmitted. One of the conditions that can cause that is an invalid pickup location code.
Cannot accept item: No items can fulfill the submitted request (Alma). Despite the wording of the message, all occurrences of this error to date have been due to a known patron whose borrowing privileges have expired.
Failed To Update Hold Database (Sierra and Millennium). (waiting for an explanation of this from III)
Failed to Create Virtual Item Record (Sierra and Millennium). This error will be triggered if the LMS' counter for the virtual record number has been corrupted. Resetting the counter will resolve the error.
Error creating the hold request : No holdable items (WMS). The library’s WorldShare Circulation configuration is preventing the hold. The most likely explanation is that the library has not updated their WMS configuration to account for ReShare integration: https://help.oclc.org/Library_Management/WorldShare_Circulation/Configuration/Integration_with_ReShare/Set_up_integration.
Unknown item. The item barcode is not recognized by the LMS. Verify that you have a valid item barcode that exists in your LMS.
Unknown user. The institutional patron barcode used by ReShare is not recognized by your LMS.
User is ineligible to borrow. The institutional patron account being used does not have the correct privileges to borrow the item. Verify that your local circulation policies are configured to allow the loan.
No institutional patron ID. You have not configured an institutional patron ID for the item to be checked out to. See Configuring institutional patron IDs for more information.
ERROR: Calendar timetable is absent for requested date (FOLIO). This could be caused by two different issses: (1) the institutional patron account is either expired or will expire before the calculated due date of the supply item, or (2) your FOLIO instance does not have a calendar enabled far enough in the future for the calculated due date of the supply item.
Item is already checked in. As of Release 1.8, ReShare should no longer return an error if the NCIP checkinItem response returns an Item is already checked in message. (Some LMSs may return a differently worded error message; these may still cause an error in ReShare.)