Last updated on MARCH 02, 2017
Applies to:Siebel Assignment Manager - Version 126.96.36.199 SIA  and later
Information in this document applies to any platform.
Customer was calling Assignment Mgr component from Siebel workflow using synchronous 'Server Request'. They were seeing Assignment Mgr failures and errors in Server Request Broker logs.
The issue / error message still happened even after the enterprise restart/reboot this morning. This issue had caused Leads exceptions when ever they ran the Assignment Manager job with a couple of hundred records to over a thousand. The issue had been intermittent and not reproducible in any other environments.
1) The following error was found in the Enterprise log error:
“SBL-SVR-00052: Internal: Invalid proc handle”. Then AsgnSrvr is terminated. So it never stays online. Thus SR Broker can never see it, and Assignment Manager does not work.
2) The following errors were prevalent in the Workflow, SRBroker and Assignment Manager logs:
"LM Automation Process Failed: Error invoking service 'Server Requests', method 'SubmitRequest' at step 'Invoke Assignment Rules.'.(SBL-BPR-00162)
"GenericError 1 0000123d4b9425bc:0 2010-03-12 00:10:30 (asgnsrvr.cpp (914) err=851969 sys=0) SBL-OSD-00001: Internal: Function call timed out (0)"
SBL-SRB-00061: Process AsgnSrvr on Siebel Server AMSPROINT1 terminated
SBL-BPR-00162: Error invoking service 'Server Requests', method 'SubmitRequest' at step 'Invoke Assignment Rules.'.
“13400: [TCPIP-server] bind() to INADDR_ANY:49152 failed for sd=5464 (err=10048 | Address is already in use (TCP/IP address/port).)”
“SBL-SVR-09016: Failed to get task instance: task number 1516240902. The task may have exited or does not exist.”
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms