I had an issue today where anytime the user tried accessing one of our tools the error below occurred.
The issue in this instance was that the user worked at a global company and had different Regions. In this instance he was logged into the North American region and once changed to his region, his commands functioned again.
