Siebel SQLs/Error Messages >  SBL-ESC-00202 Error opening trigger file for writing

SBL-ESC-00202 Error opening trigger file for writing
No Information

SBL-ESC-00203 Required parameter Privileged User or Privileged User Password is missing.
Workflow and other components crash on task exit : CCFMap<CCFElemStr, CCFElemPtr<void> >::Lookup

APPLIES TO:
Siebel Finance Service - Version 8.1.1.11.9 [IP2013] and later
Siebel CRM - Version 8.2.2.14 [IP2014] and later
Information in this document applies to any platform.
SYMPTOMS
Observing a crash of the Workflow Process Manager component process, at task exit.

 

Unmangled stack trace example :


Called from:
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsslcosd.so[0x558fba09]
[0xffffe600]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsslcshar.so(CCFMap >::Lookup(unsigned short const*, void*&) const+0x1b)[0x556d8b6b]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsscfcmn.so(CSSMapStringToOb::Lookup(unsigned short const*, CObject*&) const+0x30)[0x55955dc0]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsscfom.so(CSSModel::RemoveSessionGlobal(SSstring const&)+0x4d)[0x59ccd56d]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libssscscom.so(ccfOMSess::Logout(int)+0x5f)[0x59c7ff6f]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsssabsvm.so[0x59c73736]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsssabsvm.so(bsvmMTServer::BatchCleanup(void*, int)+0x5d)[0x59c72b4d]
siebmtshmw(smiMainThread::CompBatchCleanup(void*, int)+0x2a)[0x806b47a]
siebmtshmw(SmiRequest::CallBatchCleanup(int)+0x61)[0x8084741]
siebmtshmw(SmiRequest::CallBatchEntryPts(scrRecovInfo*)+0x165)[0x80843c5]
siebmtshmw(SmiRequest::CallBatchEntryPts()+0x1c7)[0x80841b7]
siebmtshmw(SmiRequest::ProcessRequest(long, SrmSisConnHndl*, CSSSISRequestMsg*, unsigned long, unsigned char*, unsigned int)+0x6ba)[0x808345a]
siebmtshmw[0x80884c3]
siebmtshmw(_smiBatchQ::ProcessRequest(void*, void*, void*&)+0x43)[0x8088d83]
siebmtshmw(_smiWorkQueue::ProcessWorkItem(void*, void*, void*&)+0xc4)[0x8080ed4]
siebmtshmw(_smiWorkQueue::WorkerTask(void*)+0x3ca)[0x808080a]
siebmtshmw(SmiThrdEntryFunc(void*)+0x5f7)[0x806f8d7]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsslcosd.so[0x55908476]
/opt/siebel/8.1.1.11/ses/siebsrvr/lib/libsslcwsl.so[0x5555899f]
/opt/siebel/8.1.1.11/ses/siebsrvr/mw/lib/libmfc400su.so(_AfxThreadEntry(void*)+0xe9)[0x55db0b79]
/opt/siebel/8.1.1.11/ses/siebsrvr/mw/lib/libkernel32.so(MwThread(void*)+0x1fe)[0x56b79cee]
/lib/libpthread.so.0[0x790912]
/lib/libc.so.6(clone+0x5e)[0x7024ae]TAG


CAUSE
This crash is resulting from a bug fix that was implemented in 8.1.1.11 Patch Set 9

Prior to this, if a Server Job was created, where the Job parameter 'Password' or 'Privileged User Password' is specified, the value is held as clear text in the Request Parameter table.

From 8.1.1.11 Patch Set 9, these password parameters are held as encrypted in the Request Parameter table.

The bug that has changed the password parameter encryption at DB level is :

BUG 17789532 - 8.1.1.11 GENRATE TRIGGERS FAILS AFTER UPGRADE

 

This bug is referenced in this document :

Generate Triggers and Workflow Jobs Fail with error SBL-SEC-10018 After Upgrade to 8.1.1.11 (Doc ID 1603872.1)

 

This crash results from a Repeating Job (Repeating Component Request) that has been created in an earlier version of Siebel than 8.1.1.11 Patch Set 9, and specifies 'Password' or 'Privileged User Password' in it's parameters. The parameter remains as plain text in the Request Parameter table, but 8.1.1.11 Patch Set 9 or above is expecting the value to be encrypted.

 

If you have upgrade from pre 8.1.1.11 Patch Set 9 to 8.1.1.14 or above, in our tests, we do no observe a crash. Siebel 8.1.1.14 is slightly more resilient of the incorrect value. As opposed to crashing, the job will error, for example :

 

SBL-ESC-00203: Required parameter Privileged User or Privileged User Password is missing.

 

SOLUTION
The solution is :

 

(1) Cancel the Repeating Job.

(2) Copy the Repeating Job and re-enter the password ('Password' or 'Privileged User Password') and then Submit the Repeating Job

 

The password will now be encrypted and the component will cease to crash / error.