Siebel Administration >  Getting Error In RCR SBL-SRB-00061: Process WfProcBatchMgr On Siebel Server SWS00640 Terminated

Getting Error In RCR SBL-SRB-00061: Process WfProcBatchMgr On Siebel Server SWS00640 Terminated

APPLIES TO:
Siebel Workflow - Version 8.1.1.11.9 [IP2013] and later

SYMPTOMS
On : 8.1.1.11.9 [IP2013] version, Siebel Workflow

Getting error in RCR SBL-SRB-00061: Process WfProcBatchMgr on Siebel Server SWS00640 terminated.

Process WfProcBatchMgr on Siebel Server SWS00640 terminated." while executing batch job.

ERROR
-----------------------
SBL-SRB-00061

CAUSE
The crashing PID is 7932 thread is 15844.
The crashing log for the crashing PID thread 7932 15844 is WfProcBatchMgr_0011_11534365.log
The fdr for the crashing thread is T201805240853_P007932.fdr
The call stack for the crash is crash_7932.txt

The fdr shows the crash happened while executing the business service 'FINS Teller UI Navigation', method 'RefreshCurrentApplet'

511126 1527234859 15844 Fdr_WORKFLOW WorkFlow FdrSub_WORKFLOW_STEP_NAME Step Name 0 0 Refresh View #WF Step Name#
511127 1527234859 15844 Fdr_SRF Siebel Repository FdrSub_SRF_LOAD_OBJ Load Repository Object 0 0 FINS Teller UI Navigation Business Service
511128 1527234859 15844 Fdr_SRF Siebel Repository FdrSub_SRF_LOAD_OBJ Load Repository Object 0 0 CSSServiceTlrUiNvg Class
511129 1527234859 15844 Fdr_SRF Siebel Repository FdrSub_SRF_LOAD_OBJ Load Repository Object 0 0 SSFATLRBS DLL
511130 1527234859 15844 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_SVC_CNST BusSvc Construction 328357544 0 FINS Teller UI Navigation CSSServiceTlrUiNvg
511131 1527234859 15844 Fdr_WORKFLOW WorkFlow FdrSub_WORKFLOW_SVC_NAME Service Name 1104 0 FINS Teller UI Navigation RefreshCurrentApplet
511132 1527234859 15844 Fdr_OBJMGR Object Manager FdrSub_OBJMGR_SVC_INVOKE Service Invoke Method 328357544 0 FINS Teller UI Navigation #RefreshCurrentApplet#
511133 1527234860 15844 Fdr_FDR Fdr Internal FdrSub_FDR_CRASH ** CRASHING THREAD ** 0 0

The WfProcBatchMgr_0011_11534365.log shows executing the following main workflow process and Search Specification:

TaskConfig TaskCfgParamInit 3 000003ca5b07362c:0 2018-05-25 01:46:17 Workflow Process Name : SKTL Resume Order Wrapper WF
TaskConfig TaskCfgParamInit 3 000003ca5b07362c:0 2018-05-25 01:46:17 Search Specification : [IsStatusSeasonal]='Y' AND [Account Type Code]='Service' AND [Account Status]='Active' AND [SKTL Reconnect Date]=Today() AND [CheckInFlightOrders]='N'

and the log stops at the step 'Refresh View' of sub process 'SISOMBillingSubmitOrderWebService':

EngInv EngInv 3 000003ca5b07362c:0 2018-05-25 01:53:27 Workflow engine requested to perform method '_RunSubProcess'.

EngInv Arg 4 000003ca5b07362c:0 2018-05-25 01:53:27 Input: @0*0*1*1*0*0*11*ProcessName33*SISOMBillingSubmitOrderWebService12*0*0*0*7*OrderId9*1-4JPGBUV13*SKTLOrderType15*Seasonal-Resume9*Object Id9*1-4JPGBUV7*RCRFlag1*Y16*Fulfillment Mode7*Deliver9*OrderType15*Seasonal-Resume12*Order Number12*1-989873895112*SKTLSerAccID10*1-76V-175614*SKTLCusReqDate10*05/25/201819*Parent Order Status0*11*SKTLDueDate10*05/25/201821*Order Revision Number1*1

PrcExec Create 4 000003ca5b07362c:0 2018-05-25 01:53:29 Instantiating process definition 'SISOMBillingSubmitOrderWebService'.

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'sHPSErrorMessage' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 N

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'FullfilMode' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Fulfill

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'PDSInterfaceIO' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 PDS Order - No Hierarchy

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'sReqXMLPresent' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 N

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'SynchOrder' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 FALSE

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'sValidateErrorMessage' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 N

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 Setting runtime value of property 'Namespace: 'USER' Name: 'sResXMLPresent' Datatype: 'String'' to:

PrcExec PropSet 4 000003ca5b07362c:0 2018-05-25 01:53:29 N
.
.
.

StpExec Create 4 000003ca5b07362c:0 2018-05-25 01:54:19 Instantiating step definition 'Refresh View'.
StpExec Task 4 000003ca5b07362c:0 2018-05-25 01:54:19 Invoking method 'RefreshCurrentApplet' on business service 'FINS Teller UI

This kind of workflow process is usually executed within Application Object Manager, and should be executed successfully. When you want to execute such a workflow process as a backend task which requires no UI interactions, then revise the workflow process to remove the UI context step(s), then it should work in backend task.

Siebel application is crashing when we use "FINS Teller UI Navigation" method - "RefreshCurrentApplet" in WF (TNZ Fibre Retrieve Cust Location Interface WF).
If this step is skipped in the WF, it doesn't crash.

SOLUTION
The workflow processes that need to be modified are all the workflow processes that are related to the workflow process containing the UI Context step executing the workflow process 'SISOMBillingSubmitOrderWebService'.

1. In this case, make a copy of the workflow process 'SISOMBillingSubmitOrderWebService' and give it a different name, revise it to remove the 'Refresh View' step from workflow process, deploy and activate the revised workflow process.
2. Make a copy of the parent workflow process that executes the workflow process 'SISOMBillingSubmitOrderWebService' and give it a different name, revise it to use the new workflow process from 1, deploy and activate the revised workflow process.
3. Make a copy of the main workflow process 'SKTL Resume Order Wrapper WF' and give it a different name, revise it to use the new workflow process from 2, deploy and activate the revised workflow process.
4. Start WfProcBatchMgr task for executing the new workflow process from 3.

The reason to make a copy is because you want to separate the workflow processes you execute in Application Object Manager (front end) that have UI context, and the workflow processes you execute in backend without UI context. So in AOM, your implementation will invoke workflow processes with UI context, and in WfProcBatchMgr, you will execute workflow processes without UI context.

Please note that you main workflow process 'SKTL Resume Order Wrapper WF' is complex with a lot of nested workflow processes, with custom design and implementation. It is highly recommended to test it in Development to make sure WfProcBatchMgr task works successfully before deploying it in Production.