ILLiad Known Issues
149 results found
-
The Atlas Authentication Portal is missing the log configuration file
The Atlas Authentication Portal has support for logging, but is not currently distributed with the necessary App_Data folder and log.config file to enable logging.
Bug# 26220
0 votes -
Z39.50 may duplicate item records for holdings
Z39.50 will pull in any hardcoded holding elements in the XML for a holding record, which can cause the first item listed in the record to be duplicated in ILLiad.
Bug# 25965
0 votes -
Certain ILLiad default web page files contain unnecessary FORMSTATE tags
In both the Borrowing and Lending default web pages, there are unnecessary FORMSTATE tags on web page files for request forms such as ArticleRequest.html, BookChapterRequest.html, etc.
Bug# 25397
0 votes -
Submitting an OpenURL request as new RemoteAuth user can lead to a blank form submission
In a Shared Server setup, requests submitted via OpenURL by new RemoteAuth users may be blank after the user creates their account and submits the request form.
Bug# 25395
0 votes -
Timestamps may be inconsistent for actions performed via the ILLiad web interface
The date-times used on Transaction and other records to record timestamps for actions performed via the ILLiad web interface (e.g., updating Transaction Status) may be inconsistent in value when the server timezone differs from the database timezone.
Bug# 25157
0 votes -
Invalid routing rules cause error during custom routing
When a request's transaction status is changed, ILLiad will loop through active routing rules and check for a rule matching the request's TransactionStatus and ProcessType, and then apply the rule when appropriate. However, if that routing rule is invalid because it has null fields (e.g., a null value for TransactionStatus, ProcessType, MatchString, NewTransactionStatus, or NewProcessType), an error will be logged and the routing process will fail.
ILLiad should instead check to ensure the routing rule is valid before applying the rule to the request and, if the rule is invalid, provide detailed information in the ILLiad Client log to state…
0 votes -
Routing rules can be created with only a rule number entered
The ILLiad Customization Manager allows new routing rules to be added to the Routing table with only a rule number entered and all other required fields for the rule left blank.
Bug# 25295
0 votes -
Connection Manager logs warning intended for shared server sites for single server sites upon restart
The ILLiad Connection Manager will log a "Cannot find User views. Verify ILLiad account has permissions to all User views." warning message for single server sites when the Connection Manager service is restarted.
Bug# 24685
0 votes -
ILLiad SAML Module overwrites multiple values for same attribute
If multiple values are received for the same SAML attribute, the ILLiad SAML module will overwrite those values in the order received instead of concatenating them.
Bug# 24338
0 votes -
Deleting a DSP addon that is used in business rules causes database constraint error
Attempting to delete a DSP addon that is being used as a target in DSP business rules will trigger the following database constraint error message in the Customization Manager:
'Error deleting server addon. The DELETE statement conflicted with the REFERENCE constraint "FKDecisionSupportPipelineBusinessRulesAddonTarget".'
Bug# 23937
0 votes -
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