A machine where .NET 4.5 is installed uses different assemblies, even if .NET 4.0 is targeted (to make sure about this, go check the Framework folder and use ILSpy, you'll see that some .NET 4.0 assemblies are just placeholders).
From the stack trace it seems that the issue happens inside the constructor of the ActionMessage... if you could build CM from sources and use the generated PDB, maybe you could retrieve an even more meaningful stacktrace.
From the stack trace it seems that the issue happens inside the constructor of the ActionMessage... if you could build CM from sources and use the generated PDB, maybe you could retrieve an even more meaningful stacktrace.