Could't Invoke Assignment Manager to Assign Service Request

Could't Invoke Assignment Manager to Assign SR.

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(), 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

After a review of siebns.dat, the following section showed that the AsgnMgmt components were 'Online' but not 'Enabled'
----------
[/enterprises/VFECRMPRD/servers/SIEBRPT01/component groups/AsgnMgmt]
Type=empty

[/enterprises/VFECRMPRD/servers/SIEBRPT01/component groups/AsgnMgmt/definition]
Type=empty

[/enterprises/VFECRMPRD/servers/SIEBRPT01/component groups/AsgnMgmt/definition/enable state]
Persistence=full
Type=string
Value="disabled"
Length=16

Details in the Gateway server caches provides statuses and availability of each server and it's components within the enterprise and this is what is used at startup.

The Cluster Server crash corrupted the siebns.dat and so after the restart, the corrupted values for the assignment components 'State' were being used.
Solution

The corrupted siebns.dat file was amended by resetting the assignment manager components 'enabled state' to 'enabled'.

From:

[/enterprises/VFECRMPRD/servers/SIEBRPT01/component groups/AsgnMgmt/definition/enable state]
Persistence=full
Type=string
Value="disabled"
Length=16

To:

[/enterprises/VFECRMPRD/servers/SIEBRPT01/component groups/AsgnMgmt/definition/enable state]
Persistence=full
Type=string
Value="enabled"
Length=16

Once all the changes have been made, the system was restarted in the correct order to bring all components back to an available state.

i.e.
a) Start Database
b) Start Gateway
c) Start Siebel Server

Related Posts