cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
387
Views
0
Helpful
8
Replies

Synchronizer is unable to establish connection to peer in UCCE AW

I have an application using the CCMP API to create Persons and Agents. It polls until CCMP reports a "Ready" state indicating the synch to the UCCE back-end has been completed or my 60-second timeout occurs. Normally, this takes under 5 seconds. I allow 60 seconds for unusual circumstances where the UCCE AW might be busy or the network is experiencing latency. I rarely, if ever, see a timeout.

A couple of days ago the transition from "Pending Active" to "Ready" was taking upwards of 10 minutes and I began seeing a flood of events below occurring once per second:

Log Name:      Application
Source:        Cisco Systems, Inc. ICM
Date:          10/2/2024 1:42:00 PM
Event ID:      32802
Task Category: Message Delivery
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      xxxxxawhdsdds.ucce.local
Description:
Synchronizer is unable to establish connection to peer.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Cisco Systems, Inc. ICM" />
<EventID Qualifiers="57604">32802</EventID>
<Level>2</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2024-10-02T18:42:00.131267300Z" />
<EventRecordID>132298564</EventRecordID>
<Channel>Application</Channel>
<Computer>xxxxawhdsdds.ucce.local</Computer>
<Security />
</System>
<EventData>
<Binary>060480034C27000000000000228004E130C90FC4FA14DB01140000000000418072706C0055434345313135415748445344445300</Binary>
</EventData>
</Event>

 

I dug backward to the point where this issue started and found a System Log event with a description:

"An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed."

 

I don't know if these are related or not, but I assume they may be. The flood of "Synchronizer is unable to establish connection to peer." errors cycles previous Application log events and don't see a correlation between these messages and the System log message.

I have read multiple posts about the order in which the servers should be brought up and agree with the bottom-up philosophy, but am not a UCCE or CCMP expert.

What is the correct order to bring up the servers in a UCCE and CCMP system?

How can I reduce the time it takes to synchronize a CCMP-initiated change with the UCCE back-end? 

How can I eliminate the flood of "Synchronizer is unable to establish connection to peer." errors?

Thank you.

1 Accepted Solution

Accepted Solutions

What log is showing you that synchonizer error? Is it the AWHDS, the Rogger, something else? Here's a Cisco document that talks about the different types of processes (which tie to the different logs on the different servers), in case it helps you.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_11_6_1/Configuration/Guide/ucce_b_serviceability-guide-for-cisco-unified1/ucce_b_serviceability-guide-for-cisco-unified1_chapter_0101.pdf 

View solution in original post

8 Replies 8

What version are you on? And are you seeing any errors/issues when you make changes outside of CCMP (like if you make a change on AW HDS A, you see it on AW HDS B fairly quickly if you refresh?

We are running version 12.0.1 UCCE:2000 Agents with only side A configured. We use this as a Lab to develop solutions using the API.

I rebooted the AW HDS and the changes are now going through promptly, but I am still seeing the event log flood with the Synchronizer is unable to establish connection to peer errors.

 

This may be a dumb question, but if you only have A side set up, how could the systems be synchronizing with a peer?

Not a dumb question. If I could figure out why and how an attempt to sync is being made, I can stop this repeated logging.

Are there any other "Peers" that a single-side setup could be synchronizing?

 

What log is showing you that synchonizer error? Is it the AWHDS, the Rogger, something else? Here's a Cisco document that talks about the different types of processes (which tie to the different logs on the different servers), in case it helps you.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_11_6_1/Configuration/Guide/ucce_b_serviceability-guide-for-cisco-unified1/ucce_b_serviceability-guide-for-cisco-unified1_chapter_0101.pdf 

I am seeing this critical error repeated in the Windows Application Event Log.

Thank you for this processes doc. I will review it and try to narrow down this synch error.

I hope it is helpful. You may also want this Cisco dumplog directions document too (there are other ways to get the logs, like portico, but sometimes the old school/CLI way is better).
https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-intelligent-contact-management-enterprise/20406-1.html

Thanks bill.king1. This dumplog data will be beneficial moving forward and hopefully, a huge timesaver. I appreciate your help on this.