Hi @jianhuang,
Thanks for getting in touch! We have had a couple of customer report for what looks like to be the same exception here, this may be the issue you are referring to. We still haven’t managed to get to the bottom of it, however something that has help on certain environments is to upgrade the version of .Net to 4.7
If that fails to work, you could also try adding the following to Calamari.exe.config on the failing server:
<assemblybinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentassembly>
<assemblyidentity name="System.ValueTuple" publickeytoken="cc7b13ffcd2ddd51" culture="neutral"></assemblyidentity>
<bindingredirect oldversion="0.0.0.0-4.0.2.0" newversion="4.0.2.0"></bindingredirect>
</dependentassembly>
</assemblybinding>
Would you be able to give this a go and let me know if it helps resolve this issue?
Looking forward to hearing from you.
Best regards,
Daniel