- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2016 09:20 AM - edited 03-14-2019 04:32 PM
UCCX version 10.6.1.11001-31
I have two agents that transferred to a new department.
They have been skilled to the correct resource group and team.
They have been removed from their previous resource group and team.
The agents receive calls correctly from their new department's queue.
Both agents show up in Cisco Supervisor Desktop under their old department, even though they are receiving and taking calls for their new department.
I tried Cisco Desktop Administrator -> Services Configuration -> Synchronize Directory Service
I had them log out of their Phones and Agent Desktop and back in
Tried a dbreplication and this is what we get:
admin:utils dbreplication repair all
-------------------- utils dbreplication repair --------------------
Traceback (most recent call last):
File "/usr/local/cm/bin/DbReplRepair.py", line 267, in <module>
if found >= 0:
NameError: name 'found' is not defined
Any ideas? Thanks
Solved! Go to Solution.
- Labels:
-
Other Contact Center
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2016 06:58 PM
Try restarting below services from Cisco Unified CCX Serviceability:
Cisco Desktop Sync Service
Cisco Desktop Call/Chat Service
If doing this does not fix the issue then go ahead with restarting Cisco Unified CCX Engine or restarting the whole server (whichever is more feasible) during after hours.
Regards
Deepak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2016 04:27 AM
Did you find a resolution to this? I have this problem as well.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-20-2016 06:58 PM
Try restarting below services from Cisco Unified CCX Serviceability:
Cisco Desktop Sync Service
Cisco Desktop Call/Chat Service
If doing this does not fix the issue then go ahead with restarting Cisco Unified CCX Engine or restarting the whole server (whichever is more feasible) during after hours.
Regards
Deepak
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2016 11:47 AM
Thank you for the response. I ended up restarting my UCCX servers, that took care of the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-21-2016 11:47 AM
I ended up restarting my UCCX servers outside of business hours. That took care of it.
