My Oracle Support Banner

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 7.7.2.6 SIA [18372] to 8.1.1.10 [23021] [Release V7 to V8]
Information in this document applies to any platform.
***Checked for relevance on 03-Jun-2013***

Symptoms

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:

[1] Could not route message to AsgnSrvr with registered key (null)
[2] no other server
[3] Stack trace:
Service [Synchronous Assignment Manager Requests].InvokeMethod(), Built-in function
BusComp [Service Request].BusComp_WriteRecord(), Line: 1568

From the logs:

ObjectMgr
SBL-SRB-00047: Could not route message to AsgnSrvr with registered key (null)

SRBroker
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.

Cause

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
Symptoms
Cause
Solution


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.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.