Severity Minor
Description An error has occurred in the SLEE Service.
Impact A call may have been dropped. Possible loss of a DSP channel.
Recovery Action Perform the following:
If the Description in the Alarm Monitor states "Fails to chain to program", start Application Builder and resave the application.
If the description contains the text "Unhandled user event <#> on line <#>. Currently running AppID <#> and is not followed by event 56008, then this event can be ignored. Otherwise look at event 56008 for further details.
If the description contains the text "Error loading RLL file", change the Alarm Monitor filtering to show information events, look for "SLEE crash has been recovered" event (56005) on the same line. If found, no further recovery action is required.
If this problem persists, contact customer support.
Technical Support Action Check the returned error code in the event label and take appropriate action. Start the SLEE trace utility to gain more information about this error.
Severity Info
Description A program crash has occurred and has been recovered in the SLEE service.
Impact A call may have been dropped.
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Info
Description The SLEE service has started successfully.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Info
Description The SLEE service has terminated.
Impact Not applicable
Recovery Action Not applicable
Technical Support Action Not applicable
Severity Info
Description An error occurred in a SLEE application. There is no error handling in that application. The default error handling will chain back to the idle application. The current application terminates but the system has recovered from this error.
Impact None. The system recovers from the application error.
Recovery Action Not applicable
Technical Support Action Not Applicable
Severity Debug
Description A suspicious strncpy was detected. The destination string was null terminated to prevent any further errors.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description After starting a new SLEE interpretor thread as part of error recovery, the previous thread generated an exception while freeing memory.
Impact Part of free memory store will become unusable.
Recovery Action Debug event. No action required.
Technical Support Action Not Applicable
Severity Debug
Description SLEE event polling is turned off. It may impact TelAgent or AdminAgent applications.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Minor
Description SLEE event polling is turned off in idle application. The last running application has a bug.
Impact It may impact TelAgent or AdminAgent application.
Recovery Action Contact Customer Service Representative or just restart SLEE service.
Technical Support Action Use SLEE Trace utility and try to reproduce the problem: restart SLEE service, start SLEE Trace utility and set event 56012 as a trigger.
Severity Debug
Description The idle application encountered an error while requesting the hardware interface layer to wait for a service request.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Debug
Description The idle application encountered an error while requesting the hardware interface layer release resources for the previous call.
Impact Not Applicable
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description The SLEE could not initialize main thread on SLEE startup. SLEE will not initialize properly.
Impact SLEE service has not started properly. Applications will not function.
Recovery Action Look for other events in the log. Rebooting the server may help.
Technical Support Action Not Applicable
Severity Info
Description At startup, the SLEE service queries the configuration manager to see if the database is full or not.
Impact None. The database is assumed to be not full so that updates can be attempted to the database. PDLs are written to the database. Other failures to update the database will be reported.
Recovery Action Not Applicable
Technical Support Action Not Applicable
Severity Major
Description A program crash has occurred and has been recovered from the Telephony server.
Impact Not Applicable
Recovery Action Report this crash to customer support.
Technical Support Action Not Applicable
Severity Major
Description SLEE could not initialize handles to object modules on SLEE startup. SLEE will not initialize properly.
Impact SLEE service has not started properly. Applications will not function.
Recovery Action Look for other events in the log. Rebooting the server may help.
Technical Support Action Not Applicable
Severity Debug
Description SLEE could not release handles to object modules on SLEE shutdown.
Impact Not Applicable
Recovery Action Look for other events in the log. Rebooting the server may help.
Technical Support Action Not Applicable
Severity Major
Description SLEE could not obtain handles to object modules on SLEE startup. SLEE will not initialize properly.
Impact SLEE service has not started properly. Applications will not function.
Recovery Action Look for other events in the log. Rebooting the server may help.
Technical Support Action Not Applicable
Severity Major
Description Application unexpectedly received user-defined event, but there is no handler defined for it.
Impact Application's default handling of unexpected events might cause the call to drop.
Recovery Action Contact Nortel Product Support if the problem persists.
Technical Support Action Collect event log and start the SLEE trace utility to gain more information of this error in case it occurs again.