I merged your two identical questions in different forums, as this violates the forum guidelines.
I've only seen this issue when people try to run the "runSimulation" script from the command line, as produced by ADE. You should not do this if that's what you're doing.
Essentially it expects ADE to be there if the simulation is being run in "interactive" mode - ADE can control spectre and get it to change parameters and re-run without needing to exit and restart if this is done - but runSimulation would start expecting ADE to control it.
You can stop this happening by doing:
envSetVal("spectre.envOpts" "controlMode" 'string "batch")
before starting ADE, but that will slow down parametric analysis because it forces spectre to restart for each parameter value.
With APS you don't see the issue because APS always runs in batch mode.
If you're running from ADE and you're getting this message, you should contact customer support.