Resolved issues
This topic lists previously reported issues that are resolved when you install Tungsten Output Manager 2025.2.
ID | Title | Description |
---|---|---|
2185342 | Login form did not resize properly | When resizing the Output Manager login form, the title bar image did not resize. Also, the form did not have a minimum size. |
2183518 | EWS email attachments were not spooled when other email components were not selected | When an EWS source email had been configured such that other email components had not been selected, the attachments sent to that email did not come through. |
2180282 | Unable to process email with escape character in an inline image CID | If an email contained inline images with escape characters in the CID value, it failed to process those images as inline attachments. It also produced the error message ID 5100: MessageId: 5100Message: An unexpected error occurred while processing email on IMAP4 source Estates TEST. Package consolidation failed unexpectedly. See associated exception for details. |
2177771 | Inline images in a forwarded email appeared out of order | When an email with an inline image was forwarded with an additional inline image, the images appeared out of order. |
2176581 | Unable to process EWS email attachments with illegal characters in file name | When receiving emails through EWS with attachments with invalid characters in their file name, Output Manager generated an error and was unable to fully receive the document. |
2174383 | Unable to process IMAP4 emails with invalid characters in the email header | When sending emails with an invalid character for XML to the email address configured for the IMAP4 source, emails were not processed and gave the following error in the message log: MessageId: 5100. Message: An unexpected error occurred while processing email on IMAP4 source Email-IMAP. Package consolidation failed unexpectedly. |
2174372 | Reporting Aggregator was misidentifying old versions of instance databases as standalone databases | When aggregating data from a newer version of Output Manager to a pre-ControlSuite version, the ReportingAggregator could misidentify the instance database as a standalone database. |
2165574 | Underscore character was not visible after transforming certain documents from PostScript to PDF | When transforming documents from PostScript to PDF, after bringing the PS documents to the Output Manager source to trigger the business rules, the underscore in the certain documents was not visible in the transform PDF. |
2164049 | Unable to process Office 365 email attachments with invalid characters in the file name | Office 365 email attachments containing invalid Windows characters (?,|, *, and so on) resulted in the attachments not being processed by Output Manager. |
2164048 | Unable to process IMAP4 emails with empty body | In a rare situation, the email body was treated as an inline attachment by the email client, and the email body appeared empty in the IMAP4 email. |
2156576 | When configuring Output Manager services, the HA settings sometimes were not saved | When configuring high availability (HA), the ODBM setting for the VIP did not hold its configuration, the HA Name field turned Red on Close, and then cleared the field. |
2151034 | Form feed was inserted at wrong location when merging text certain files | Some documents merged with the Form Feed several lines into the second document. |
2141324 | Duplex was not getting set properly in PDL when using the User Information Stamping rule action | When using the User Information Stamping rule action, the duplex option in the PCL6 code was not getting set properly. As a result, a simplex job was changed to duplex after the User Stamping action ran. |
2133998 | Output Manager Job Monitor port required VC++ 2010 runtime | The Job Monitor port was missing VC++ 2010. |
2127306 | Documents remained hidden after restoring deleted user | After restoring a deleted user, documents assigned to them were not visible. |
2109621 | Output Process Email Notification did not work for TIF files | Output Process Email Notification did not work for TIF files because the TIF data type was not available in for Output process action execution. |
2109610 | The Dithering setting value was reset when opening the Transform Options dialog | Dithering value did not remain visible if changed to a value other than default 50. |
2085656 | User could assign a secondary billing account, without assigning the associated primary billing account. | In the "Select billing accounts to assign" dialog, user had the option of setting the billing accounts on a document when a secondary account could be chosen without the associated primary account, which was not consistent with the rest of ControlSuite. |