Yesterday, I faced a really weird problem while trying to debug a script.
Problem:
Clicking on Debug Menu > Start, started the client session but the “Waiting for Runtime to Respond” Dialog (as shown below) box used to get stuck in Siebel tools and debugging never started 
If I closed the application instance that was opened then I the dialog box said Failed and the error message shown below popped up
The process exited unexpectedly.
The command ‘C:\PROGRA~1\Siebel\7.8\WEBCLI~1\bin\siebel.exe /c “C:\Program Files\Siebel\7.8\web client\BIN\ENU\scomm.cfg” /b “C:\Program Files\Internet Explorer\IEXPLORE.EXE” /u username /p password /d Local /h’ exited before completing its connection back to the development instance.(SBL-DEV-00128)
It seemed like client instance was not able to give the control back to Siebel tools.
I just didn’t make sense. If I clicked “Cancel” button on dialog box nothing happened. I was stuck there for 3 hours and started getting really frustrated 
to the extent of thinking about un-installing and installing tools and client again
Solution:
Searching Support web and Web didn’t yield any results as usual 
The solution turned out to be pretty simple :P in the end during some testing few days back I had made EnableScripting parameter of my CFG as “FALSE”. It seems like there must some internal script written in the application that must be returning the control back to Siebel Tools and disabling the script execution made Siebel Tools wait for some particular signal was was not being returned.
So, just setting the parameter EnableScripting as True solved the problem
I hope this knowledge will make somebody suffer less than I did 
Keep commenting and reading !!!
(5 votes, average: 3.8 out of 5)
Loading ...
5 Comments at "EnableScripting CFG parameter and Debugging"
Hi neel.,
Im a newbie in siebel and i hope this tip helps when i get to real time production.
thanks a lot and keep it up.
Hello Neel,
I think before starting the debugger, if we write the /H parameter, the “Waiting for runtime to respond…” would disappear after your application gets launched.
Setting Enablescripting to FALSE will not allow you to test your script changes.
I hope this helps.
thanks,
Prasad.
Oops, sorry did not refer your comments completely. You are correct, setting EnableScripting to TRUE would also help.
thanks,
Prasad.
Thanks for the information - i was also stuck at this for some time now.
Severus
I’ve had a similar problem for years. It tends to happen when I switch between debugging in multiple environments (from Dev to Test for example and switching users). The final solution I came across is to delete C:\sea752\tools\BIN\devtools.prf, this always fixed my “Waiting for Runtime to respond” problem.
Comment Now!