Document ID: 116256
Updated: Aug 22, 2013
Contributed by Benjamin Wollak, Maxim Tikhov, and Jason Pare, Cisco TAC Engineers.
This document describes the procedure used in order to recover a failed installation of the Cisco Unified Contact Center Enterprise (UCCE) Diagnostic Framework Portico.
Cisco recommends that you have knowledge of these topics:
- Cisco UCCE
- Diagnostic Framework Portico
- Microsoft Windows Services, Registry, and CLI
The information in this document is based on Cisco UCCE Versions 8.5 and 9.0.
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.
After a fresh installation or Refresh Upgrade, the Diagnostic Framework Portico page might not load. Additionally, the Cisco Intelligent Contact Management (ICM) Diagnostic Framework service might not appear in services.msc.
Access these URLs from the local server that Portico runs on in order to reach the Portico Diagnostic page. Ensure that you update the <UCCE-server-IP> and <Instance-Name> place-holders accordingly for your environment.
If the above URLs do not work, refer to these log files for additional information:
- C:\ icm\serviceability\diagnostics\logs
If either of these logs reference installer errors, you can review the InstallUtil logs. In order to do this, navigate to C: > Windows > Microsoft.NET > Framework > v2.0.50727 > InstallUtil, and open InstallUtil.INSTALLLOGFILE.
Complete these steps in order to install the Diagnostic Framework manually:
- Open a command prompt.
- Enter these commands:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallUtil.exeThe Diagnostic Framework is now installed, as shown in this image:
If the service already exists on your machine, you get this message:
An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The specified service already exists
Installation is performed in a transactioned way; if one of the assemblies fails to install, the installation of all other assemblies is postponed. Uninstall is not transactioned.
If the ICM Diagnostic Portico ListProcesses and Unified CLI show processes commands do not show the status of ICM processes after manual installation is completed, navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > services > DiagFwSvc and verify that the Type is set to 0x0000110 (272).
If a registry change is required, reboot the server in order to commit the change. After the reboot, the status of UCCE processes should display properly.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.