Skip to content

ILLiad Known Issues

← Atlas Systems

Search known issues

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

7 results found

  1. Routing rule errors may be misleading in the logs

    Routing rules errors are logged as "Invalid match string" errors even when the error is not caused by an issue with the match string.

    Bug# 26555

    1 vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  2. WebView2 dependency of ILLiad Client installer attempts to run even if WebView2 is already installed

    Attempting to install the ILLiad Client with Powershell and SCCM causes issues during the WebView2 installation even if WebView2 is already installed on the system before installing the ILLiad Client. This issue prevents the client installation from being completed.

    Bug# 26820

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  3. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  4. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  5. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

  6. 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

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    planned  ·  0 comments  ·  Admin Tools  ·  Admin →

  7. Some characters are not correctly encoded when logging.

    Some characters (such as those with diacritics) are not properly encoded in log files.

    Workaround: Add <encoding value="utf-8" /> under the <appender> element in the default log.config files.

    Bug# 21306

    0 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

ILLiad Known Issues

Categories

Feedback and Knowledge Base

(thinking…)