Event ID 48420

[irishhooligan]

SCCS 5.0 connected to a 81C Succession 3.0 using Call Pilot 2.02 w/ACCESS ports.

Were receiving the following error in the event log:

The description for Event ID ( 48420 ) in Source ( NGen ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 48420 , MSG , DBG , ICCM Task Flow Executor (TFE)[] , 1, , , 4, 0, .\nitfe_cltasktsm.cpp/callProcessingEventHandling : line 1127, Unfound call id: 589507264.

We are seeing a lot of events being throttled to the tune of 38,68,93,etc.. Unfortuantely the event description really doesn't provide any information except the Unfound call id:

I ran a call by call report in SCCS and couldn't find the call id.

Any thoughts?

Also, if any one knows of a NTP that describes how the persmission need to be set in the registry please provide the NTP number. Thanks and sorry for the long post.

 

[croat1]

Is your TFE service (on SCCS server) going to unknown when this happens?

 

[irishhooligan]

TFE still shows up in SMonW. I couldn't find an error log to show TFE crashing, expect for the 48420 ID's.

What do you think?

 

[2005mgf]

48420 is a DEBUG type event. It means that an event (such as CONNECTED/REROUTE/RESTORED/OFFERED/IVR_COMPLETE) was received for a call which SCCS no longer is aware of. SCCS becomes aware of a call when it receives the Incoming Call notification from the switch. It should maintain a reference to the call until the call is cleared. It looks like the reference to the call has already been removed when the event is received.

Best thing to do is to identify one such call and investigate everything that happened to the call. Try and identify what is the invalid operation that is being attempted.

Check your scripts. In particular, ensure that transfers and IVR are being handled correctly.

Finally, the way to see the full text of the message is to use the Event Browser in SCCS client rather than the Windows EventVwr.

 

[irishhooligan]

Thanks for the info. The event in the client provides no additional information.

Also, I tried to find the Call ID in the call by call report but it did not show. Is there any other report that can trace the call by the call ID?

BTW..we are recieving hundreds of different debug errors.

 

[Revolution1200]

Hi,

We currently use sccs 4.2 and we receive these same debug messages (48420) - roughly about 50 of these an hour.

we have the vendor coming on monday night to install a PEP to supposedly fix this problem

I will let you know.

Stuart