Please enter search query.
Search <product_name> all support & community content...
Updating assembly references in the AcceleratorService.exe.config file after Discovery Accelerator 15.1.2 upgrade
Article: 100074073
Last Published: 2025-06-23
Ratings: 0 0
Product(s): Enterprise Vault
Description
After upgrading to Discovery Accelerator 15.1.2, some assembly references are not updated. To ensure proper functionality, the versions of these assembly references need to be manually updated in the AcceleratorService.exe.config
file.
Solution
Step 1: Stop the Enterprise Vault Accelerator Manager Service (EVAMS):
- Open the Windows Services Manager.
- Locate and stop EVAMS.
- Navigate to the Discovery Accelerator installation folder (default location:
C:\Program Files (x86)\Enterprise Vault Business Accelerator
) and take a backup of theAcceleratorService.exe.config
file.
Step 2: Edit the AcceleratorService.exe.config
file:
Open the AcceleratorService.exe.config
file using Notepad or a text editor.
Step 3: Update assembly references:
- Update
System.Runtime.CompilerServices.Unsafe
reference:- Locate the line containing the following entry:
<assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.0.4.1" newVersion="4.0.4.1" />
<codeBase version="4.0.4.1" href="Production/System.Runtime.CompilerServices.Unsafe.dll" /> - Update it to:
<assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-6.0.0.0" newVersion="6.0.0.0" />
<codeBase version="6.0.0.0" href="Production/System.Runtime.CompilerServices.Unsafe.dll" />
- Locate the line containing the following entry:
- Update "MimeKit" reference:
- Locate the line containing the following entry:
<assemblyIdentity name="MimeKit" publicKeyToken="bede1c8a46c66814" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-3.4.2.0" newVersion="3.4.2.0" />
<codeBase version="3.4.2.0" href="Production/MimeKit.dll" /> - Update it to:
<assemblyIdentity name="MimeKit" publicKeyToken="bede1c8a46c66814" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-4.7.0.0" newVersion="4.7.0.0" />
<codeBase version="4.7.0.0" href="Production/MimeKit.dll" />
- Locate the line containing the following entry:
- Navigate to the
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
section and add the following:
<dependentAssembly>
<assemblyIdentity name="BouncyCastle.Cryptography" publicKeyToken="072EDCF4A5328938" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
<codeBase version="2.0.0.0" href="Production/BouncyCastle.Cryptography.dll" />
</dependentAssembly>
Step 4: Save and restart EVAMS:
- Save and close the
AcceleratorService.exe.config
file. - Restart EVAMS from Windows Services Manager.
Verification
- Ensure that EVAMS starts without errors.
- Check logs for any assembly reference issues.
This completes the necessary modifications after upgrading to Discovery Accelerator 15.1.2.
References
JIRA : CFT-6638