Cisco Cisco Agent Desktop 8.0
Release Notes for Cisco Agent Desktop 7.2(1)
Documentation Updates
decomp.dat
kdecomp.dat
DB_CONFIG
Date:
3 December 2007
Page:
25
Correction: Under the section, “Component Sizing,” the number of agents an LLC can support is
incorrect. The correct number of agents that can be supported by a single LCC is 1,000.
Date:
3 December 2007
Page:
236
Correction:
Add the following new troubleshooting items.
Problem: After simultaneously upgrading CAD and switching to a new ICM instance,
agents cannot log in and the personnel nodes in Cisco Desktop
Administrator are blank.
Administrator are blank.
Solution: Wait for the Cisco Sync Service to synchronize the information from ICM.
Problem: After restoring audio files using CDBRTool, the following line appears at
the end of the log file:
2007-06-07 10:13:13:031 DEBUG [0xe4c] CDBRTOOL::Main:
End of CDBRTOOL (Success=0)
End of CDBRTOOL (Success=0)
Solution: The CDBRTool indicates the status of a backup or restore on the last line of
the log file by printing either (Success=0), (Fail=-1), or (Some Errors=1).
The result (Success=0) indicates that the return code was 0 and therefore
that the run was successful. The result (Some Errors=1) indicates that errors
occurred. If errors occur, the log file also includes the message "Some errors
occurred with loading agents. See log/dbg file for details."
The result (Success=0) indicates that the return code was 0 and therefore
that the run was successful. The result (Some Errors=1) indicates that errors
occurred. If errors occur, the log file also includes the message "Some errors
occurred with loading agents. See log/dbg file for details."
Problem: The SQL replication subscription and REPL-Merge job disappear and the
publisher database cannot replicate to the subscriber database.
Solution: If the publisher database is unable to replicate to the subscriber database for
4 days, the SQL job “Expired subscription clean up” will run and remove
the replication subscription (and subsequently delete the REPL-Merge job).
the replication subscription (and subsequently delete the REPL-Merge job).
If the subscriber server is powered off for the duration, the jobs will not
clean up. The cleanup only occurs when the publisher is able to access the
subscriber server but is unable to synchronize (for example, if the SQL
Server engine is stopped on the subscriber).
clean up. The cleanup only occurs when the publisher is able to access the
subscriber server but is unable to synchronize (for example, if the SQL
Server engine is stopped on the subscriber).
The default timing within SQL Server for the expired subscription cleanup
job is 14 days. Recording & Statistics service replication setup changed that
timer to 4 days as there should only be 7 days of data, and it was determined
that if you hadn't replicated properly in 4 days, you need to set up the
Recording & Statistics service replication again.
job is 14 days. Recording & Statistics service replication setup changed that
timer to 4 days as there should only be 7 days of data, and it was determined
that if you hadn't replicated properly in 4 days, you need to set up the
Recording & Statistics service replication again.