Could't Invoke Assignment Manager to Assign Service Request
(Doc ID 727864.1)
Last updated on OCTOBER 01, 2018
Applies to:Siebel Assignment Manager - Version 184.108.40.206 SIA  to 220.127.116.11  [Release V7 to V8]
Information in this document applies to any platform.
***Checked for relevance on 03-Jun-2013***
After encountering a cluster server crash which forced a restart of the application server it was no more possible to invoke Assignment Manager to Assign Service Requests.
Error reported includes:
 Could not route message to AsgnSrvr with registered key (null)
 no other server
 Stack trace:
Service [Synchronous Assignment Manager Requests].InvokeMethod(), Built-in function
BusComp [Service Request].BusComp_WriteRecord(), Line: 1568
From the logs:
SBL-SRB-00047: Could not route message to AsgnSrvr with registered key (null)
GenericLog GenericError 1 0 2008-07-15 07:53:48 (scbcomp.cpp (822) err=7100011 sys=0) SBL-SCB-00011: Failed to connect to pipe (SEBL_32_2460) on process 2460.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|