Known Issues - Adept Clients and Servers
The issues listed below have been reported but remain unresolved. Each issue is identified by its Issue Key, which is used internally by the Synergis team.
Unless the Issue Key appears in the Resolved Issues section of the latest Release Notes, all previously reported Known Issues from earlier versions still apply to the current software release.
Issue Key | Issue Description |
A11-1178 | In Mozilla Firefox, the Adept Client Services Download dialog does not appear, preventing users from installing required software for document access. This issue does not occur in Chrome or Edge. Customers using Firefox should be aware of this limitation. |
A11-1924 | The Related Fields plugin cannot connect to Oracle 19c databases when the database server is hosted separately from the Adept server. Users will encounter a connection error during configuration. |
A11-2973 | The Audit Trail record for the Markup Document command incorrectly includes a 36-character ID in the Info field that serves no purpose to users. Please disregard this GUID. |
A11-2974 | Due to a Log4J vulnerability in the Adept Authenticator feature of the Adept Web Server, the offending file has been removed. Customers who use username-only authentication for Web client users will need to switch to another authentication method. |
A11-3028 | Adept applications do not support ARM-based processors. |
A11-3096 | When editing an existing AFS Satellite configuration, the Protocol field incorrectly defaults to TCPIP instead of the previously configured HTTP or HTTPS. If not manually corrected, this misconfiguration can prevent the Hub from communicating with the Satellite. |
A11-3158 | In Adept Desktop, the "Blank Entry" folder in the FileGuide may display a file count that is double the actual number of documents in the vault. This occurs when the field used for the FileGuide is blank for some documents. There is currently no workaround. |
A11-3250 | Users signing in with Single Sign-On (SSO) cannot select a language during login. The language selection option is unavailable on the SSO screen in both the desktop and web versions of Adept |
A11-3312 | Adept is unable to rename files larger than 4 GB in the work area, resulting in errors when attempting to rename ZIP archives. This occurs even though the files can be renamed in Windows. |
A11-3505 | An installation problem exists with the Bill of Material Automation plugin for Adept Desktop. Customers using this plugin should contact Adept Support prior to upgrading to ensure uninterrupted use of this functionality. |
A11-3580 | Outlook may crash when attempting to send a Transmittal PDF that exceeds the email server's attachment size limit. To avoid this, reduce the PDF's DPI or request an increase in the server's attachment size limit. |
A11-3610 | When creating a file using the "Out From Library" option in Adept Web, the Required Fields dialog does not appear—even when Required Fields are configured. As a result, files may be created without the required field data. See also A11-3613. |
A11-3613 | When creating a file using the "Out From Library" option in Adept Taskpane, the Required Fields dialog does not appear—even when Required Fields are configured. As a result, files may be created without required field data. See also A11-3610. |
A11-3726 | Copying or checking out large files to Shared Work Areas in Adept may take 10 times longer—or more—than performing the same operation to a local work area. This delay can result in timeouts or canceled operations. A preliminary solution has been identified and will undergo thorough validation to ensure reliability and performance before release. |
A11-3739 | In Adept Web, the Date field in the Required Fields dialog accepts invalid text input. If a non-date string is entered and the calendar icon is clicked, the field may display an incorrect value (e.g., 1899-11-30), and the OK button may become enabled, allowing invalid data to be saved. |
A11-3774 | When Adept Web removes refresh tokens via the WebAPI, expected exceptions are logged as unhandled errors in the Windows Event Log. These entries do not indicate a system failure but may make normal behavior appear as errors, complicating issue detection. |