How to Resolve File Join Errors with Secure Exchanges?

Error adding a signature file or document with Secure Exchanges

If an error occurs when you try to attach a file or document for signature in an email protected by Secure Exchanges, it usually means that the file is already being used by another application or is temporarily blocked by your antivirus software. In most cases, this problem is caused by a conflict with the antivirus software, which prevents Secure Exchanges from accessing the files needed to protect or sign documents.



Setting up exceptions in the antivirus software will permanently resolve this problem.

Steps to Follow

1. Add Secure Exchanges to your antivirus's exceptions

For most antivirus software, you will need to:

  1. Open your antivirus software.
  2. Access settings or configuration options.
  3. Search for the exceptions or exclusions section.
  4. Add Secure Exchanges to the list of exceptions or exclusions.
Here is the list of exceptions to add:

%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.commons.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\phonenumbers.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.barcodes.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.layout.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.forms.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.io.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.pdfa.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.sign.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.svg.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.styledxmlparser.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\itext.kernel.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\OSecureExchange.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\JWT.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\CsvHelper.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\BouncyCastle.Crypto.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\SecureExchangesSDK.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\Newtonsoft.Json.dll
%USERPROFILE%\AppData\Local\Temp\Deployment\*\*\fr-CA\OSecureExchange.resources.dll

If it's not Windows Defender, you need to add Secure Exchanges to the exclusions of your third-party antivirus.

2. Restart Your System

Once Secure Exchanges has been added to the exceptions, restart your computer to ensure that the changes take effect.

3. Try attaching the signature file or document again

  1. Open Outlook and try again to attach the signature file or document to your email.
  2. Protect your email with Secure Exchanges as you normally do.

    • Related Articles

    • Microsoft Office error during Secure Exchanges update (ASR blockage)

      1. Context Microsoft Defender includes a security rule called "Block executable content from email client and webmail" that blocks executable content from email clients. This rule blocks all content considered executable when it originates from an ...

    • Deploying Secure Exchanges via GPO/Intune on Outlook

      If you plan to deploy Secure Exchanges using Group Policy Objects (GPO) or Microsoft Intune, the necessary PowerShell scripts are available at the bottom of this article. For any questions, please contact us at support@secure-exchanges.com

    • How to activate an API license in Secure Exchanges

      Activating an API license allows you to use the advanced features of Secure Exchanges in your applications. Here are the steps to follow: You can find the API and SDK help documentation here: https://help.secure-exchanges.com 1. Log in to the online ...

    • What is Secure Exchanges' Refund and Upgrade Policy?

      At Secure Exchanges, we are committed to providing high-quality service to our customers. Please read our refund policy below: Free Trial Period We offer a free 30-day trial period so you can discover our services. During this period, you can explore ...