Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

In Cisco Unity 4.x, after GC reconnect, the resync fails to update on the Cisco Unity server which causes Cisco Unity to go into license violation

Core Issue

The subscriber and Cisco Unity server information (Digital Networking Data) fails to update on one Cisco Unity server. This can include any of these:

  • extensions

  • recorded names

  • dialing domains

  • license pooling data

This causes Cisco Unity to go into license violation.


If the Global Catalog (GC) monitor (AvDsGlobalCatalog) can not contact its GC twice, it discovers a new GC with which to sync. Since Update Sequence Number (USNs) are not consistent across DC/GCs, when Cisco Unity connects to a new GC, it must complete a full resync in order to ensure proper synchronization.

When the GC monitor reconnects because of two failed connection attempts, the LastUSN value in the UnityDb configuration must be set to 0. But, at times this does not happen. if the GC that Cisco Unity reconnects with has a lower USN, this can cause a critical replication to fail, because Cisco Unity believes its data in SQL is more recent.

This issue is tracked in Cisco bug ID CSCsc17174.

Complete these steps for one possible workaround for this issue:

  1. Open dohproptest.exe from \commserver\techtools.
  2. When prompted for a password, click OK.
  3. Click Ignore.
  4. Click GC Monitor.
  5. Click TotalResync.

This issue is resolved in these versions:

  • 4.2(0.21)
  • 4.0(5)ES57
  • 4.0(5)ES60
  • 4.1(1)ES32

Open a case with Cisco Technical Support with the TAC Service Request Tool in order to obtain an appropriate Engineering Special patch.