ILLiad Known Issues
158 results found
-
Rapid Manager initializes new lender records with NULL values for Odyssey trusted sender settings In some cases, Rapid Manager will create new lender address records with NULL values set for TrustedSender and TrustedSenderOverride, which can break the logic to determine if a given sender is trusted if there are many records that have the same URL for the Odyssey IP. This is because the code will use the IP address associated with an incoming request to look up all lender address records using that same IP address as their Odyssey IP rather than looking up address records based on the symbol.
In the case of items sent by RapidX, there can be hundreds of…
0 votes -
Byte arrays passed to .NET methods are converted to null due to an NLua bug Byte arrays (often referred to as Byte[] in Microsoft's .NET documentation) passed from Lua to .NET methods are converted to null, causing those .NET methods to fail when included in addon code.
This is a known NLua bug present in the version of the NLua component used by the ILLiad application, detailed here: https://github.com/NLua/NLua/issues/438.
Bug# 24017
0 votes -
Rapidly clicking Docline buttons can cause ILLiad Client to crash Clicking a button on the Docline interface three or more times in rapid succession causes the ILLiad Client to crash when the WebView2 browser control is used.
Bug# 23031
0 votes -
Changes to the Location field dropdown selection on the Users to Clear form will revert if another dropdown is modified Changes to the dropdown selection in the Location field on the Users to Clear form will revert if the value of another dropdown on the form is modified.
Bug# 23285
0 votes -
PDFs from HathiTrust experience visual bugs during import PDFs from HathiTrust do not properly display in the ILLiad Client's Scanning form during import and may contain visual bugs such as blank pages, but will send and deliver as expected in ILLiad 9.2.
Bug# 22934
0 votes -
Error is returned in logs for PDF files using non-numeric filenames during ElecDel cleanup process When PDF files using filenames that contain non-integer values are handled by the ILLiad System Manager's electronic delivery file clean-up process, the following error will be returned in the logs:
"ERROR AtlasSystems.ILLiad.SystemManager.Cleanup - ERROR PROCESSING C:\ILLiad\PDF<FILENAME>.pdf -- Skipping -- Could not parse transaction number from the filename.
System.FormatException: Input string was not in a correct format.
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at AtlasSystems.ILLiad.SystemManager.Cleanup.ProcessPdf(FileInfo fileToProcess)"Bug# 22556
0 votes -
Improperly formatted routing rules can lead to email spam When a routing rule is improperly formatted and returns an error, the transaction will not complete the routing process and will remain "stuck" in its original status. This can lead to email spam if the original status is a queue that sends an email notification to the user (e.g., Awaiting Customer Contact) as the notification will be sent repeatedly until the request is manually routed out of the original queue.
Bug# 22851
0 votes -
Address matching for some Docline requests may fail For some Docline requests, only part of the shipping address is matched and saved from the request text on the Lender Selection form, which then causes address matching to fail when that request is imported from Docline into ILLiad.
Bug# 22013
0 votes -
Database Manager may fail to delete CopyrightSessions records The ILLiad Database Manager will fail to delete CopyrightSessions records that contain non-integer values in the OrderHeader and OrderDetail fields.
Bug# 21882
0 votes -
Log messages may contain extra punctuation marks Several log messages (e.g., the "Error refreshing system alert list" message) are improperly formatted and contain extra punctuation marks at the end.
Bug# 21726
0 votes -
User notification preferences are not set if user is moved across NVTGC web pages as they register If a user creating a new account on the ILLiad web pages selects a pickup location/NVTGC on the user registration form that is different from the NVTGC associated with the set of web pages being used to register, then notification preferences will not be set when the account is created.
Bug# 21707
0 votes -
Missing trailing slash breaks WebPDFPath key The file path entered in the WebPDFPath customization key will not be recognized unless it contains a trailing slash at the end.
Bug# 21457
0 votes -
Users without layout customization permissions can't view customized layouts in the ILLiad Client Custom layout changes will not show in the ILLiad Client unless the logged-in staff user has the "Can Customize Layouts" permission enabled in the ILLiad Staff Manager.
Bug# 21351
0 votes -
Some characters are not correctly encoded when logging. Some characters (such as those with diacritics) are not properly encoded in log files.
Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.
Bug# 21306
0 votes -
ILLiad API errors when DueDateOverride value is NULL The ILLiad API will return an error when submitting a Loan request for a Lending Library that belongs to a Group with a NULL DueDateOverride value (i.e., when no Lending Due Date Override value has been set for that Group).
Bug# 20813
0 votes -
PDF Utility handling fails for PDFs generated by iTextSharp 4.1.6 The PDF Utility used by the Odyssey Manager will return errors when delivering PDFs generated by iTextSharp 4.1.6.
Bug# 20683
0 votes -
Notification preferences not set for users created from UserValidation with LDAP Notification preferences will not be set for new users created via the UserValidation table if LDAP authentication is being used.
Bug# 20309
0 votes -
Volume information will not import if the DOCLINE citation doesn't contain an issue number After the DOCLINE 6.2.41 update, volume information will not import into the ILLiad request if the DOCLINE citation does not contain an issue number. This affects both ILLiad 9.1 and 9.2.
Bug# 20282
0 votes -
Electronic Delivery Utility routes requests to Delivered to Web before file is processed by Odyssey Manager The Electronic Delivery Utility routes borrowing requests to the Delivered to Web status before the file is successfully processed and delivered by the Odyssey Manager, which can make the file inaccessible to the patron on the web if Odyssey processing fails.
Bug# 20030
0 votes -
Electronic Delivery Utility sends 0 KB files The Electronic Delivery Utility (EDU) will send 0 KB files, which are invalid and may cause processing errors. Instead of sending these files, the EDU should check for 0-byte files or ensure that the size in the file metadata matches the actual file size before sending.
Bug# 20029
0 votes