In Open UI, Dispatch Board Is Causing Siebel To Crash And Take Us Back To Homepage (Doc ID 2114701.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Field Service - Version 8.1.1.14.5 [IP2014] and later
Information in this document applies to any platform.

Symptoms

On : 8.1.1.14.5 [IP2014] version, Field Service

In Open UI, we are unable to navigate to March 14, 15, 16, 17 on the Dispatch Board without causing Siebel to crash and take us back to Homepage. It also kicks off other users at random.

ERROR

- CALL STACK -
sslcshar +0x25e59 = CCFFileReferenceMgr::GetFileNameInArr() +0x59
sslcshar +0x2532d = CCFPropertySet::GetELCookie() +0x8d
swcabcfr +0x39433 = CSSSWEFrameGantt::DoPackageUtillData() +0x1d3
swcabcfr +0x37f40 = CSSSWEFrameGantt::GetUtilizationDefinition() +0x360
swcabcfr +0x34454 = CSSSWEFrameGantt::CreatePropertySet() +0x3e4
SWCAFSFR +0x1626e = CSSInvokeMethodUtility::~CSSInvokeMethodUtility() +0x1414e
swcabcfr +0x35139 = CSSSWEFrameGantt::RefreshGantt() +0x4f9
swcabcfr +0x32bf8 = CSSSWEFrameGantt::DoInvokeMethod() +0xe8
SWCAFSFR +0xfa3c = CSSInvokeMethodUtility::~CSSInvokeMethodUtility() +0xd91c
sscaswbc +0x36e27 = CSSSWEFrame::InvokeMethod() +0x157
sscaswbc +0x36ca5 = CSSSWEFrame::InvokeMethod() +0x15
sscaswbc +0x302200 = CSSSWEComponent::InvokeMethod() +0x20
sscaswbc +0x101a56 = CSSSWEFrameMgrInternal::InvokeAppletMethod() +0xa26
sscaswbc +0xda26e = CSSSWECmdProcessor::InvokeMethod() +0x80e
sscaswbc +0xd8c87 = CSSSWECmdProcessor::_ProcessCommand() +0xaf7
sscaswbc +0xdd3a0 = CSSSWECmdProcessor::ProcessCommand() +0xca0
sscaswbc +0xdd98b = CSSSWECmdProcessor::ProcessCommand() +0xfb
sscaswbc +0x2a4432 = CSSServiceSWEIface::Request() +0x342
sscaswbc +0x2a653e = CSSServiceSWEIface::DoInvokeMethod() +0xf0e
sscfom +0x1976d = CSSService::InvokeMethod() +0x2cd
sstcsiom +0x7653 = CSSSIOMSession::ModInvokeSrvcMethod() +0x123
sstcsiom +0xc234 = CSSSIOMSession::RPCMiscModel() +0x4e4
sstcsiom +0x1832 = CSSSIOMSession::HandleRPC() +0x402
sssasos +0x71a0 = CSSSISObject::HasErrors() +0x46f0
sssasos +0x59e1 = CSSSISObject::HasErrors() +0x2f31

fdr

98417 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_SESS_CT_EVT Trigger CT Event 289337752 2 Action Query
98418 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_CACHE_QUERY Cache Query Parse Tree 396912388 0 :[Area] = WO Save Attempt""
98419 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_BC_EMPTY_WS BusComp Empty WorkSet 403771144 0 Action
98420 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_SCRIPT_ALLOC_INFO Details on prev alloc (compare int2) 417019760 0 BusComp [Action] #BusComp_ChangeRecord#
98421 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_BC_REC_DSTR WorkSet Record Destruction 403771144 446417184 Action
98422 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_SCRIPT_ALLOC_INFO Details on prev alloc (compare int2) 417019760 0 BusComp [Action] #BusComp_ChangeRecord#
98423 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_BC_REC_DSTR WorkSet Record Destruction 403771144 446420864 Action
.
.
.
98452 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_SCRIPT_ALLOC_INFO Details on prev alloc (compare int2) 417019760 0 BusComp [Action] #BusComp_ChangeRecord#
98453 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_BC_REC_DSTR WorkSet Record Destruction 403771144 446417184 Action
98454 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_SCRIPT_ALLOC_INFO Details on prev alloc (compare int2) 417019760 0 BusComp [Action] #BusComp_ChangeRecord#
98455 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_BC_REC_DSTR WorkSet Record Destruction 403771144 446420864 Action
98456 1456770175 4460 Fdr_OBJMGR Object Manager FdrSub_SCRIPT_ALLOC_INFO Details on prev alloc (compare int2) 417019760 0 BusComp [Action] #BusComp_ChangeRecord#
98457 1456770178 4460 Fdr_FDR Fdr Internal FdrSub_FDR_CRASH ** CRASHING THREAD ** 0 0


STEPS

The issue can be reproduced at will with the following steps:


1. Navigate to Site Map > Dispatch Board > Dispatch Board, the Dispatch Board opens with today's date.
2. Click on Select Service Region to select National region, change date to March 14, 2016 by clicking on calendar icon by today's date, and choose March 14. There is no drilling down involved or anything else.
3. The stop watch comes up and stays for sometime, and next is the Homepage/login page displays which means the Application Object Manager crashed.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms