ILLiad Known Issues
-
PDF Document Processor prevents PDF from being closed until the Client is closed - Error message 'file in use'
When a PDF has been loaded by a PDF Document Processor (on the scanning form or the electronic delivery form), the filesystem keeps a lock on that file until the ILLiad client is closed. This is because the processor is not closing the file.
Error Log Message Example: The process cannot access the file 'C:\Program Files (x86)\ILLiad\elecdel\o48034.pdf' because it is being used by another process.
Bug# 8578
0 votes -
Request cloning from the staff client will always set the RequestType to Article
Repro Steps
1. Open a loan request in the staff client
2. Clone the request. The behavior is the same regardless of cloning to same user or different user and if the request is/is not opened after the process is completed.4 votes -
Persist Settings bug if a search group is not selected
The "Error saving z39.50 persistent settings to registry" occurs if you don't have a default Z39.50 Search Profile/Configuration and open the request form.
Bug# 10020
0 votes -
FormClearUser doesn't populate Yes/No values for ElectronicDelivery field
The ElectronicDelivery field on the Clear User form does not have any default or selectable values in the dropdown, but will accept Yes or No if manually typed in.
Bug# 10281
0 votes -
ILLiad Client Overdues null reference exception error
In OverduesList.cs, the gridViewRequest_CustomColumnDisplayText function may throw a null reference exception when it attempts to call ToString() on e.Value.
Bug# 8564
0 votes -
Blank Password in Client Forms Prompts Error Message
A blank error message pops up when you:
- Open ILLiad Client
- Enter a valid username
- Leave password blank
- Attempt to login
Bug# 8363
0 votes -
Order of Web Alerts
There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 6725
0 votes -
Application menu button is not visible when using Office 2019 skins
The default white hamburger is not visible against the white background of the skin. This bug impacts the client, staff manager, and customization manager.
v9.0 & v9.1
Bug# 58900 votes -
0 votes
-
The borrowing tab is displaying the list of queues in reverse alphabetical order
On the Borrowing tab, ILLiad is displaying the list of queues in reverse alphabetical order and is adding new custom queues to a new "Requests" group, instead of the existing "Requests" group.
Bug# 5642
0 votes -
Documents can't be delivered electronically, or get stuck in a electronic delivery queue/workflow because of corrupt PDF files
Files that are corrupt can't be retrieved through ILLiad and can potentially cause the client to crash or freeze until the client has been restarted. If the corrupt files were found, canceled, or delivered manually, they will need to be manually updated in the OdysseyRecieved table once the client has been restarted.
Bug# 4727
0 votes -
ILLIAD: Removed profile groups still appear in recently used menu
Profile groups removed from the GAC table still appear in the recently used menu, and the recently used menu appears to grow infinitely. See attached screenshot.
Bug# 4650
0 votes -
Changing skins will cut off the Holdings window, hiding the Delete and Clear buttons from the Selected Lenders box
This issues occurs when you change the skin then navigate to Open request>OCLC tab>Holdings tab.
Workaround: Restarting the client fixes the issue; however, you will need to restart the client each time you change the skin or else the error will occur again.
v9.0
Bug# 44810 votes -
0 votes
-
0 votes
-
Unable to create a Direct Request Profile in the Resource Sharing Settings of the ILLiad client.
Bug#3765
0 votes -
0 votes
-
0 votes
-
0 votes
-
Lender Address form throws an error
FormLenderAddresses will throw an exception when the request tab is opened without the lender being saved first.
0 votes
