Applies to: Any PACS integration after a PACS-side upgrade, license renewal, or major version change
Symptom: Sync fails in a way that doesn’t match any of the known configuration issues covered elsewhere in this series — often after the customer upgrades or renews their PACS license, with errors like deserialization/formatter exceptions or task-cancellation faults that don’t point to an obvious setting.
Why This One Is Different #
Every other article in this series covers a fix you can make yourself. This one is here to set honest expectations: when the root cause is a PACS API or version incompatibility — for example, the PACS vendor changed something in a new release that Data Manager’s connector doesn’t yet account for — this is not something a site administrator can resolve through configuration. It requires an engineering-level investigation and, in some cases, a Data Manager connector update.
What to Do #
Rather than spending significant time trying configuration fixes for this category, gather the following and contact the Telaeris Helpdesk right away:
- The exact error text (deserialization/formatter exceptions and
TaskCanceledExceptionfaults are common signatures of this category) - Your PACS vendor and version, and the version you upgraded from if this started after an upgrade
- Whether this started immediately after a PACS upgrade, license renewal, or Windows/SQL Server upgrade
- A copy of the Data Manager sync log covering a failed sync attempt
Providing this up front — rather than after working through the other checklist articles without success — gets this routed to engineering faster.
