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# 4481

Bug# 4474

The lending web pages prevent the display of the billing information table when BillingActive is set to false.

Workaround: If BillingActive is set to BillingActiveLending, then the BillingInformation table will always display in the lending web pages.

Bug#4444

The email import behavior when creating a new user from an import request with the EMailImportAutoUserRecord set to yes will cause the generateuser call to appear as though it has failed, but the request is still imported, and assigned to a default user

Should also be noted that this process works correctly when the user already exists in the system. This is only occuring when AutoUserRecord is set to yes, and the Username value from the email does not exist in the database.

Bug# 4441

When a user changes a Lender's password from the ILLiad client, it only changes the password for the NVTGC that the user is logged into the client under, instead of changing it for all NVTGCs. As a result, the lender may be able to log into the client under that particular NVTGC but unable to log into the web.

v9.0 & 8.7
Bug# 4436

Bug# 4393

Workaround: Try different numbers in the parameters of the report.

Bug#3765

The permissions for the dropped tables are not being added back/copied over and have to be done manually after the update.

v9.0
Bug#3903

The invalid username status line doesn't seem to be triggering the SLLoginFailed customization key on the Forgot Password page. The status line does appear if triggered on the logon pages.

v9.0 & 8.7
Bug#4147

v9.0
Bug#3789

In SQL Alias Manager v1.2.2 the textboxes to enter a server address and the database name are not visible.

Workaround: If you shrink the page splitter and move to the left, the textboxes will begin to appear.

Bug#3792

Bug#3583

When printing the PrintAddress.doc template from the client, the PrintAddress.xlsx data source file that is created has the Legacy style headers for both the Legacy queue and the Print queue.

v8.7.2
Bug#3797

The data source for the Billing Manager printing process still defaults to C:\illiad\print\ in the Customization Manager, but newer installations of the ILLiad client don't create this folder. This only occurs for new installations who don't have the print folder from previous installations.

v9.0 & 8.7
Bug#3887

If a system addon is created but FormNames are also entered, the addon will be loaded for both the system script environment and for each form script environment that is specified. An example where this causes errors is when registering system event handlers which can only be registered to a single addon.
 
Forms are not relevent in Library, System, or Server addons.

FormLenderAddresses will throw an exception when the request tab is opened without the lender being saved first.

Bug# 1560