ILLiad Known Issues
149 results found
-
Initial Cleared User email may fail to send when using certain authentication types
When using certain authentication types (including PatronAPI, ILLiadExclusive) with the automatic user clearance feature, the notification preferences for newly registered users on the web will not be set before the Cleared User email is sent, leading to failure to send the email and the following error:
ERROR AtlasSystems.ILLiad.WebPlatform.Controllers.V1.NotificationController - AtlasSystems.ILLiad.DomainLogic.Exceptions.NotificationRequiredException: Exception of type 'AtlasSystems.ILLiad.DomainLogic.Exceptions.NotificationRequiredException' was thrown.
Bug# 15092
0 votes -
Odyssey Manager fails to process files if the associated username contains an apostrophe
The Odyssey Manager will fail to process files for which the associated username contains an apostrophe and will throw an "incorrect syntax" error in the logs.
Bug# 15347
0 votes -
Rapid Manager does not correctly handle Obsolete Request errors when processing renewal responses
If the ESPUpdate table contains any expired Rapid requests, the Rapid Manager will be unable to handle the Obsolete Request error received from the Rapid API and will be prevented from processing any remaining requests.
Bug# 15701
0 votes -
EditPatentRequest.html contains incorrect error parameter for PhotoJournalTitle field
The error parameter for the PhotoJournalTitle field on EditPatentRequest.html has an incorrect value of ERRORLoanAuthor in the ILLiad 9.1 web pages. The correct value for this parameter is ERRORPhotoJournalTitle.
Bug# 14817
0 votes -
SLLogout status line doesn't display in 9.1 web pages
The text configured in the SLLogout status line key will not display on the 9.1 web pages after the user logs out of ILLiad.
Bug# 14798
0 votes -
Requests are sometimes created with a NULL transaction status
Requests in ILLiad may sometimes be created with a blank/NULL transaction status that can then cause issues with web reports, routing rules, and custom searches.
Bug# 14436
0 votes -
WebTNNotesFilter will not apply on Edit pages
When a request is edited on the web, ILLiad will pull in the latest note regardless of the value in the WebTNNotesFilter key.
Bug# 14374
0 votes -
The "Route Request to Review" action in the Automated Request Manager (ARM) causes unexpected behavior in ILLiad
If the "Route Request to Review" action is selected in the configuration settings for the OCLC Automated Request Manager, this can lead to ILLiad unexpectedly closing the affected direct requests.
Bug# 14342
0 votes -
Screenshots submitted through the Feedback form are corrupted when saved
Screenshots submitted through the Feedback form of the Client will display correctly on the form but will be corrupted after the file is saved.
Bug# 14332
0 votes -
Copyright web report exports incorrectly
The Microsoft Excel file produced when exporting results from the Copyright web report populates the results from the Finished Requests table in all three sheets (Finished Requests, Outstanding Requests, and Completed Orders).
Bug# 14244
0 votes -
Google Search v2.1 Addon Broken
There is an issue causing version 2.1.0 of the Google Search addon to pull up a blank, white screen, and disable the addon's buttons.
[NOTE]: This issue is resolved in ILLiad 9.2.
Bug# 13090
0 votes -
PDFs appear distorted in Scanning window
PDFs downloaded from a database sometimes display distorted with dark blobs in the Odyssey Manager Scanning window. The appearance of the PDF returns to normal upon delivery.
ILLiad 9.1
Bug# 12857
0 votes -
Leaving the ILLiad Authentication checkbox unchecked/unchanged when creating a new user will default the user to ILLiad Authentication type.
Leaving the "ILLiad Authentication" checkbox unchecked/unchanged while creating a user in the Client still defaults to ILLiad Authentication when the user is created, even though the option is not checked when saving.
Workaround: Check and uncheck the box before saving.
Bug# 12841
0 votes -
Errors saving DBC on Windows 8/Server 2012
When using Windows Server 2012, an error occurs when saving a DBC file with the Save button in SQL Alias Manager.
Bug# 12126
0 votes -
DBC passwords containing special characters cause database connection errors
DBC passwords containing some special characters (such as semicolons) lead to errors when the DLL attempts to connect to the database.
Bug# 12304
0 votes -
DLL incorrectly displays detailed error information to users
When an error is encountered, the ILLiad DLL is displaying detailed error information that should not be visible to end-users.
Bug# 12291
0 votes -
Alma NCIP Addon sometimes performs improper error handling
In some cases, an error response from the NCIP server is not handled properly by the addon. The NCIP message validation and error handling should be improved to handle these cases.
Bug# 12033
0 votes -
Large number of saved layouts causes a database timeout
If the combined file size of saved layouts is too large, it may occasionally cause database timeouts and revert all Client layouts to the default.
Bug# 11910
0 votes -
Status-specific include pages do not work on SiteMap.html
When using a status-specific include page to display content on SiteMap.html, the default include page and associated links are displayed instead due to an error in the DLL.
Bug# 11764
0 votes -
Errors opening/sending some types of PDFs in the Client
The ILLiad Client may fail to open PDFs downloaded from databases/online sources or PDFs that are password-protected/encrypted, leading to delivery failures when attempting to send the documents via Odyssey. The following errors are returned in the Client log:
-"An error occurred while attempting to load a file."
-"Input data is not recognized as valid pdf."Workaround: Convert the affected PDFs files to TIFF format and upload the converted file into ILLiad.
Bug# 11572
0 votes