Hello OutSystems Community,
Recently we get debugger error directly in Service Studio, when trying to start the debugger. Its strange that it happens in one module, but in another module in same end user application, the debugger could be started with no problem. Any ideas to solve this issue - would be helpful.
Thanks & Regards
Pavithra
Hello,
You can refer to this documentation:
https://success.outsystems.com/support/troubleshooting/application_development/debugger_in_service_studio_is_not_working/
And also this discussion:
https://www.outsystems.com/forums/discussion/67463/a-debug-session-cant-be-started-due-to-communication-problems/
Maybe they can help you out.
Hi @Pavithra Balasubramanian
Hi faced something similar, I can't remember if was the same or not and the way I fixed was clone the module and republish.
Hi Pavithra,
Judging the error, the server returns an HTML error page instead of the intended XML. Are you running on-premise or in the cloud? Can your app reached through a browser from the same location as you are debugging? Does the app use SEO?
Hello Pavithra Balasubramanian,I’ve faced this issue before and in my case it was related to module synchronization between producer and consumer layers.
The error:
“The content type text/html; charset=utf-8 does not match the content type of the binding (text/xml; charset=utf-8)”
Usually indicates that instead of returning XML (expected by the binding), the platform is returning HTML — often an error page.
Things I recommend checking:
1️ Which layer are you debugging?
Is it the Producer (Service/Core) module?
Or a Consumer (Reactive/Traditional Web) module?
This matters because sometimes the consumer is referencing an outdated version of the producer.
2️ Republish all dependent modules In my case, the issue was solved by:
Republishing the Producer module
Republishing all Consumer modules that reference it
This forced metadata synchronization and fixed the binding mismatch.
3️ Check for compilation errors in dependencies Sometimes a module compiles, but a dependency has issues and returns an HTML error page during debug.
4️ Clear environment cache / restart IIS (if on-prem) If applicable, restart the environment to clear cached metadata.
In short: This error usually happens when the debugger expects XML but receives an HTML error page instead — most commonly due to outdated references or dependency inconsistencies.
Republishing the full dependency chain solved it for me.