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# 85780 votes
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
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# 128410 votes
The link to the TRS Terms and Conditions webpage is broken in the Process Copyright ribbon and on the Borrowing Request Form Copyright tab.
Bug# 121200 votes
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# 119100 votes
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# 115720 votes
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# 100200 votes
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# 102810 votes
In OverduesList.cs, the gridViewRequest_CustomColumnDisplayText function may throw a null reference exception when it attempts to call ToString() on e.Value.
Bug# 85640 votes
A blank error message pops up when you:
- Open ILLiad Client
- Enter a valid username
- Leave password blank
- Attempt to login
Bug# 83630 votes
There is no specific ordering that determines the way the web alerts appear within the client.
Bug# 67250 votes
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
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# 56420 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# 47270 votes
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# 46500 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.
Bug# 44810 votes