eScript random runtime crash with SBL-OSD-01000 error code.
(Doc ID 779492.1)
Last updated on FEBRUARY 07, 2019
Applies to:Siebel Scripting, MME - Version 184.108.40.206 SIA  and later
Information in this document applies to any platform.
""Checked for relevance on 04-Jan-2015""
We've been struggling with an apparently random behavior from eScript. OM crashes leaving an SBL-OSD-01000 error code.
Sometimes it seems that scripting in the area, may it be an Applet, BC or BS, doesn't work. As a workaround, we copied all the script to the preinvokemethod and from that moment on we've never experienced the crash anymore.
It also happens that sometimes, calling a function declared in the area doesn't work if we don't explicitly specify were to look for it. As an example, we have a customized tracing function, 'AddToLog', that seizes to work randomly if we don't call it like this.AddToLog('ÃÂ¦'); from the events scripting area, crashing OM and launching the same SBL-OSD-01000 error.
A third situation that also has induced to this crashes with SBL-OSD-01000 error is to use ActiveBusObject which is, randomly and for no known reason, null.
We are able to reproduce these errors on every Siebel server, but not on dedicated web clients.
We are quite concerned about this erratic behavior as we can't be sure how it'll work in production environment. Furthermore, our workaround for the first problem placing all lines of code in the event handling scripting area (preinvokemethod, invokemethod and so on) is having a major impact on scripting organization and readability.
We are working on Siebel 220.127.116.11, with an Oracle 10g database, all on Windows platform.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document