Cisco Desktop Call/Chat Service Error!

Unanswered Question
Apr 4th, 2006
User Badges:

Can someone can help me ? I got this error and I don't know how to fix it, thanks.


I'm using IPCC Express Premium 4.0(3)_Build080

------------------------------

Event Type: Error

Event Source: Cisco Desktop Call/Chat Service

Event Category: None

Event ID: 4

Date: 4/4/2006

Time: 11:38:18 PM

Description:

FCCS260 Caught Exception <COMM_FAILURE> sending message to application <AGENT_DESKTOP_1251>, logout application.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4.5 (2 ratings)
Loading.
aboschetti Mon, 08/21/2006 - 01:26
User Badges:

Hi,

I've the same problem with IPCC Express Premium 4.0(4)SR01_Build029.

Have you solve your problem ?

I've tried to access to Bug Toolkit but I've not found it !

Please let me know

francis.labelle... Mon, 08/21/2006 - 05:29
User Badges:

The way to fix it is to open some tcp port in the Windows firewall of your agent worksation.

I think that you have to open port 59001. But I'm not sure..

scoe Mon, 02/23/2009 - 05:02
User Badges:

Hi,


Did you get to the bottom of this? We had the same thing with the message.


"FCCS260 Caught Exception sending message to application , logout application".


Thanks,


Stuart

ajohn1976 Mon, 02/23/2009 - 08:14
User Badges:

Please check on bug ID CSCsh02642, still an open bug with Cisco.


CAD logins and state changes severely lagged

Symptom:

CAD software would "hang" for an extended period whenever a state change was

requested or any other interaction took place with the server like delivering a call and

popping to the front.


Conditions:

CRS 4.0(4)SR1

CCM 4.2(1)SR1

DC Directory

2000.4.2 SR7

JATPI 2.2(1.15)


NIC cards and their respective LAN switch ports are hardcoded to 100/full


The actions are eventually successful but take place 30-60 seconds

after requested, for instance, the CAD software may pop to the front with the call data

30-60 seconds after the agent has answered the phone. When this happens, we see a number

of errors from the Call/Chat service in the Application Event Log in a form like this:


"FCCS260 Caught Exception sending message to application

, logout application. "


Workaround:

Variants on this message are logged in the Event Log and in \program

files\cisco\Desktop\log\FCCServer000X.log. We seem to be able to restore normal service by

restarting just the Call/Chat service.

Status

Open

(More)

Severity

3 - moderate



Product

Cisco Unified Contact Center Express


Technology



1st Found-In

4.0(4)

4.0(4)SR1


Fixed-In

4.0(5)SR1


Component(s)

cad


Regression

Y


Actions

This Discussion