UCCX Script Editor Version 10.5 Will Not Launch

Introduction

This document describes a problem encountered when you launch the Cisco Unified Contact Center Express (UCCX) Script Editor Version 10.5(1).

Problem

You are unable to run the UCCX Editor Version 10.5(1) (CiscoUnifiedCCXEditor.exe).

Symptom

When launched, the UCCX Editor window appears for less than a second and disappears. The application tries to launch but it disappears.

Solution

In order to solve this issue, you must check if the CCX Editor's files are present in the folder: C:\Program Files (x86)\wfavvid_1051. In order to check this, right-click the Editor icon (shortcut) and navigate to Properties > Target. The install folder should be directly in C:\Program files(x86).

Sometimes, the path can be incorrect. For example: C:\Program Files (x86)\Cisco\Unified Serviceability\JRtmt\wfavvid_1051.

Take these steps in order to resolve this issue:

1. In order to uninstall the CCX Script Editor application on the workstation, navigate to Control Panel > Add/Remove programs.
2. Re-install the Editor application (Run as administrator) directly into the Program Files and explicitly define the path: C:\Program Files (x86)\wfavvid_1051.
3. Run the application in order to test.

Root Cause

The issue is related to the default location of the installation (path). It looks for files hardcoded to the location and does not launch if those files are not found. By default, the CCX Editor must be installed in the location: C:\Program Files (x86)\wfavvid_1051. If that is not the case, the Editor will not run correctly. In order to test this, the issue can be recreated if you copy the wfavvid_1051 folder elsewhere.

Also it has been noticed that if the Real-Time Monitoring Tool (RTMT) was previously installed on the workstation, the UCCX Editor will prompt the user to install it in the erroneous path: C:\Program Files (x86)\Cisco\Unified Serviceability\JRtmt\wfavvid_1051.

After you install in that incorrect location, a launch of the Editor fails. At this time, you should take the steps mentioned previously in order to resolve the issue. Although there is a workaround in place, an enhancement defect has been opened to simplify and address installation-related issues: CSCur86817.