Answer
Check for a mismatched 32-bit vs 64-bit component dependency — in one confirmed case, a reference to the log4net .dll was the actual culprit, and installing the corresponding 32-bit components alongside the existing 64-bit CWS/runtime/client setup resolved the exception. A fully 64-bit-looking CWS installation can still have an individual dependency expecting a 32-bit counterpart, which won't necessarily show up clearly in the report-specific logs.