Skip to content

ILLiad Known Issues

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

4 results found

  1. 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)

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →
  2. 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)

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →
  3. 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)

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →
  4. 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)

    We’ll send you updates on this idea

    0 comments  ·  Admin Tools  ·  Admin →

Feedback and Knowledge Base