I'm not sure how to get to the bottom of this problem but regardless of the three-letter-acronym sitting on top of .NET it usually a dependency issue or an issue brought on by renaming that breaks reflection.
The fact you don't get any debugging information won't make it easy to sort out, though.
Some of SA's options just plain won't work in some scenarios and we recommend starting with the bare minimum and adding more options until the assembly stops working.
If it is broken by obfuscation, then you have to work out which types need to be excluded, which can be a pain.
Merging tends to wreck type equivilency, resulting in bizarre and inconsistent errors.