'ServerMain' Not Supported On BService 'Workflow Process Manager' For Cloned WfProcMgr Component (Doc ID 2057192.1)

Last updated on MARCH 02, 2017

Applies to:

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

Symptoms


The Workflow Process Manager component was cloned and when attempting to call a workflow process asynchronously to be processed by this custom component, the following error occurs in the log file:

ERROR
-----------------------


ObjMgrBusServiceLog Warning 2 0000000355b616e8:0 2015-07-27 13:41:17 (service.cpp (233)) SBL-DAT-00323: The method 'ServerMain' is not supported on Business Service 'Workflow Process Manager'.

ObjMgrBusServiceLog InvokeMethod 4 0000000355b616e8:0 2015-07-27 13:41:17 Business Service 'Workflow Process Manager' invoke method 'ServerMain' Execute Time: 0.000 seconds.

ObjMgrBusServiceLog InvokeMethod 4 0000000355b616e8:0 2015-07-27 13:41:17 End: Business Service 'Workflow Process Manager' invoke method: 'ServerMain' at 152b6ca8

GenericLog GenericError 1 0000000355b616e8:0 2015-07-27 13:41:17 Object manager error: ([0] The method 'ServerMain' is not supported on Business Service 'Workflow Process Manager'.(SBL-DAT-00323) (0x750143))

GenericLog GenericError 1 0000000355b616e8:0 2015-07-27 13:41:17 ( (0) err=2818155 sys=7668035) SBL-OMS-00107: Object manager error: ([0] The method 'ServerMain' is not supported on Business Service 'Workflow Process Manager'.(SBL-DAT-00323) (0x750143))

GenericLog GenericError 1 0000000355b616e8:0 2015-07-27 13:41:17 (bsvcmgr.cpp (1393) err=2818251 sys=0) SBL-OMS-00203: Error 7668035 invoking method "ServerMain" for Business Service "Workflow Process Manager"

GenericLog GenericError 1 0000000355b616e8:0 2015-07-27 13:41:17 (bsvcmgr.cpp (1236) err=2818251 sys=0) SBL-OMS-00203: Error 7668035 invoking method "ServerMain" for Business Service "Workflow Process Manager"

we've set up a cloned WfProcMgr component to better distribute the load of components for Marketing tasks. See attachment of the definition of the component.





STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Clone Workflow Process Manager component
2. Call a workflow process asynchronously to be processed by this custom component

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