For example, this might happen if you have Net Express or Studio Enterprise Edition installed and COBCONFIG is set for it.
To work around this issue, ensure that Visual COBOL is not running and then modify the configuration file by doing one of the following:
set cobconfig_error_report=false
This happens when you edit files such as .dat that have a file association with Net Express or Studio Enterprise Edition. This can also happen when invoking a utility within the Net Express or Studio Enterprise Edition products as an external tool from Visual COBOL.
You can workaround this problem in Visual COBOL as follows:
Set COBREG_PARSED= Call [PathToUtility] %1
Where PathToUtility is the path to the Net Express or Studio Enterprise Edition utility.
This ensures that the proper environment is established when running that tool.