Cisco Cisco Unified Contact Center Express 9.0(1) 문제 해결 가이드
Introduction
This document describes how to troubleshoot CRS upgrade, backup, and restore issues.
Prerequisites
Requirements
Cisco recommends that you have knowledge of these topics:
Cisco Unified Contact Center Express
•
Cisco IP Telephony Backup and Restore System (BARS)
•
Components Used
The information in this document is based on Cisco Unified Contact Center Express versions 3.x, 4.x,6.x, and
7.x.
7.x.
The information in this document was created from the devices in a specific lab environment. All of the
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
devices used in this document started with a cleared (default) configuration. If your network is live, make sure
that you understand the potential impact of any command.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
CRS 3.x and 4.x: Common Errors Received During Backup,
Restore, and Upgrade
Restore, and Upgrade
TCP Socket closed unexpectedly
When a Backup/Restore/Upgrade (B/R/U) fails, you might receive a message (displayed in red text) on the
BARS Screen that states
BARS Screen that states
TCP Socket closed unexpectedly. Restore/Backup/Upgrade
failed.
This message is generic and displayed in case of any failure in the backup/restore/upgrade operation. It is not
an indication of the TCP connection breaking off or any network connection issues between the CRS and the
BARS machines.
an indication of the TCP connection breaking off or any network connection issues between the CRS and the
BARS machines.
Applet Communication Error
Problem
CRS backup/restore/patch/upgrade fails in BARS due to a timeout waiting for applet communication (CRS
Java applet fails to be loaded to the browser in which BARS admin runs within 5 minutes). The BARS admin
shows that it extracted the archive files in the status window, and it appears to hang for about 5 minutes before
it reports the failure. The MCVD / MARC log file shows the failure reason as "timed out initializing applet's
communication." This issue is documented in Cisco Bug ID CSCef91551 (registered customers only) .
Java applet fails to be loaded to the browser in which BARS admin runs within 5 minutes). The BARS admin
shows that it extracted the archive files in the status window, and it appears to hang for about 5 minutes before
it reports the failure. The MCVD / MARC log file shows the failure reason as "timed out initializing applet's
communication." This issue is documented in Cisco Bug ID CSCef91551 (registered customers only) .
This issue can occur if the browser that is used to run BARS admin does not include the required settings.