Thank you Phil.
I informed the client and he tried to install the DTA on a workstation without Fortis Scan installed, but received the same error. I asked him to uninstall the scanner software and try to let windows recognize and install it and then launch the scan app to see if it helps.
It looks like the FAQ article hasn't been updated as of today 10/30.
This is v6.12 which has migrated more of the admin tool functions to the configurations page and to my knowledge that full text view is either no longer available or has been moved elsewhere.
Once a Fortis migration has completed via the migration helper, is there a way to research and determine how far along the full text ocr process has progressed against the entire document population?
We just completed the initial migration of ~674k documents on Friday and the docuware imaging worker processes(4) are plugging away at that population, pegging the CPU cores at 99%, which of course makes the system sluggish.
Having this knowledge might encourage the administrator to bump the CPU core count to help power through the bulk of documents more quickly.
This is what managed to get me some relief from the error state maze. Since I couldn't edit, delete or anything other than start/stop which produced errors continually.
What I did was to 'deactivate' each workflow, start each 'deactivated' workflow and let it complete, which presents a 'success' result(go figure).
Once out of the error state, I edited each one without changing any of the configuration and saved.
Once completed, I activated them again and all was well.
I hope this helps someone else as it is quite an aggravating situation.