The Debugger Not Started warning is issued in the following situations:
You should set the eSpace Operation property ‘Debug Mode’ in Service Center and republish it so it can be debugged. Debugger was not started.: property Debug Mode of the eSpace was not set last time the eSpace was published. The eSpace was opened in the browser but the debugger was not started.
In Service Center, go to the eSpace tab Operation and check the property Debug Mode. Afterwards, 1-Click Publish your eSpace before trying to Run it again.
This Service Studio debugger version is not compatible with the current Platform Server version. Debugger was not started.: you are trying to run your eSpace in a Platform Server with a debugger version that is not compatible with Service Studio's. The eSpace was opened in the browser but the debugger was not started.
Check with your Service Center administrator to determine what version is being used and to find out which parts of the software must be upgraded so you can debug your eSpace.
The debugger could not access your eSpace. It was not started.: you were running your eSpace but the debugger was not able to access it, so it was not started. However, the Run command proceeded, the browser was opened and a request was done.
Check whether the eSpace is executing in the browser instance launched by Service Studio. If it is, try to Run your eSpace again.
Debug an eSpace | About Warning Messages