Solved my own problem
It appears as though any user that did not previously configure some portion of DBA using ISTECH abilities will get this error because, at least in our case, the ISTECH file was not in the ISTS folder on the server or on the affected workstations.
Simply copying the file from a workstation that had updated to the ISTS on the server solved the problem.
Hopefully, Lynn will confirm.