Hi Eric,
Based on the scenario you describe, this type of situation can occur when something in the environment has changed (i.e. a Windows Update, .NET version change, a change to the underlying software being automated, etc.). Although this KB article is specific to the Excel VBO, it contains a list of environmental factors to check: "
How do I fix error "Exception has been thrown by the target of an invocation" when running a Process?"
Working with your IT/Infrastructure team to determine if anything in the environment has changed since this was last working correctly would be a good troubleshooting first-step, as well as providing the exact error message reported by the user interface (including the full list of actions within the Detail button's additional stack trace screen).
If these (and the resulting) suggestions provided in the Community don't help to resolve this issue, we would encourage you to submit a Support ticket about this with
the necessary details so we could investigate it further.