KM1002480 

- How to resolve call

consolidator alarms or
ConsolidatorDBConnector alarms

Audience
customer

Description
Information on Recorder call consolidator and how to troubleshoot Recorder call consolidator alarms (for
example - ConsolidatorDBConnector).

Applies To
WFO v15.x; Impact 360 V11.1

Cause
There could be various reasons for call consolidator issues or alarms. This article will review most of the
common ones: One of the services is not running, communication is down between different components
and web service is down on the application server.

Solution
The call consolidator is responsible for inserting the metadata information of a call into the database. The
call consolidator is a service on each recorder. The service is called "Recorder Consolidator Service" The
service read the XMLs files with the call details that the recorder is creating and send the information over
HTTP/S  to the data model webservice that reside on the application server. The data model Webservice
then mark the information in the contact database (CentralContact)
Whenever having call consolidator issues or alarms check the following:

1. Check that the Recorder Consolidator Service is up and running on the recorder (it should be running on all
recorders servers).

2. Check that the DataModelWS_Pool is up and running on each application server (Start->run->inetmgr-
>application Pools)

3. Check that the contact database is available and running  (CentralContact) -  

* If all the above were checked and no issue found, then it might be a network disconnection between
Recorder and App server or App server and SQL.


Did this article solve your problem?

0 Members were helped by this document

Online
Dhexter Villa 
4 comments

1 member is here

Top Comments
Offline
Lorincz, Gabor
4 months ago
+1
In my case CentralContact dbase rejected connection attempt with error 9002. Transaction log was f

Offline
Lorincz, Gabor
4 months ago
In my case CentralContact dbase rejected connection attempt with error 9002. Transaction log was
full.

Offline
Boaz
4 months ago
in reply to Lorincz, Gabor
Good point! Any issue with the database (log/data file is full) will cause a problem with the
marking. We will add it to our "TO DO" list to add a section about potential issues with the
database.

Offline
Lorincz, Gabor
4 months ago
In my case CentralContact DB rejected the connection attempt with sql error 9002. Transaction log
was full.

Offline
Lorincz, Gabor
4 months ago
In my case CentralContact DB rejected the connection attempt with sql error 9002. Transaction log
was full.