This issue can be identified by the borrowing system error: "Received unexpected undo shipped message for transaction from [lender symbol]".

The issue occurs if the current lender of the request (in OCLC) is the same that was stored on the request when it was shipped and checked in and, the value in OCLC is stored as lower case but the value in ILLiad is stored as uppercase. This causes the request to not match and prompt the undo shipped note.

Workaround: Some sites have reported that changing to another skin and back to original skin allowed Login As to work again.

The Client Error log may say the following: A thread exception has occurred.
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

Bug#3980

External systems running on the user's machine such as McAfee AntiVirus can affect web traffic. Since Docline is running through the web, users may receive a script error upon login. If the user clicks No or closes the script error, they will receive a blank Account Type box.

Bug# 4111
v8.7.3 and Docline 6.0

When dragging the last server from the included listbox to the available servers listbox and then saving, an error will occur.

v9.1
Bug# 4808

RAPID Lending requests are not downloading correctly for shared server sites who share a RAPID symbol but have different branches.

v9.1
Bug# 4834

The HTTP headers could potentially pose a risk of cross-frame scripting (XFS) in the ILLiad web pages.

v9.1
Bug# 4848

Document type tag can be a potential risk of cross-site scripting (XSS) in the ILLiad web pages.

v9.1
Bug# 4766

The Odyssey Manager does not check to see if the Library is a Trusted CopyrightPayer so the CopyrightAlreadyPaid checkbox never gets checked when the file has been received. As a result, the Journal Titles received from a Copyright Payer end up on the Copyright Reports.

Bug# 4491

The DLL is trimming any leading or trailing spaces from the password field within the web, whereas the client just runs the password as it's entered with the spaces. For example, if my password is "ABC" when logging in the client "ABC " fails, whereas it works in the web pages because the space is being removed.

Note: A space can exist within the password itself, e.g., "P@ss W0rd", as long as it's an accepted requirement in the Customization Manager. The spaces within the password will not be trimmed by the DLL.

Bug# 4490

Bug#4263
v9.0.3 & 8.7.3

When a user who has an ILLiad login and an AuthType of Default tries to log in to the ILLiad web pages when WebAuthType=RemoteAuth, they are able to log in without being prompted to change their password (when trying to log in for the first time after the upgrade).

v9.0
Bug#4214

An error message/feedback pop-up will appear when a staff user attempts to group transactions by a field (e.g., username) in dd stacks searching. The log will record this error as "Transaction number 0 not found".

v8.7 & 9.0
Bug# 4172

Bug#4007

The RegEx used assumes the first angle bracket as part of the tag instead of a bracket inside a tag parameter. This impacts email and SMS templates.

v8.6
Bug#1470

The ILLiad ExternalRequestController is attempting to retrieve statuses for external requests that had never been created in Aeon. The check is parsing the ExternalID as an integer but when null, fails.

This error occurs with Aeon and ILLiad integrations.

v8.7.2
Bug# 3829

Bug#3775

OCLC Requests that have a Worldshare ILL Status of Closed and disposition of Supplied cannot be opened in the OCLC Request form.

Bug#3787

The transaction status that displays on the lower left of the status bar on a request form is not visible when using some skins due to the color contrast with the default black text. See the attached example of the Office 2013 Dark Gray Skin. This status is visible in the Standard Display using Office 2016 Colorful and Office 2016 Dark.

v9.0
Bug#3991
Bug#4166

Bug#4006