I love getting these error messages when using the Dynamics SDK!
I immediately know where to go to resolve the problem when it happens 🙁
If you are trying to diagnose precisely where the issue is in your code, the “Reason” member won’t have this data – probably because it’s not at the top of the stack and you need to dig deep to see what’s what.
To get to the nitty gritty of what is happening you will need to dig into the InnerFault of the Detail member to see what has really happened.
I know, trivial, but a pain when you forget after awhile that you need to dig deeper into these problems.
The real solution is to build a stronger errorhandler that goes through all these members to bubble back up to your (my) application what has “really” happened so you can resolve and move forward with quickly.