CUIC Import of UCCE Stock Reports Fails with the SELECT Permission Denied on the Object

Available Languages

Download Options

PDF (38.6 KB)
View with Adobe Reader on a variety of devices

Updated:May 15, 2014

Document ID:117646

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Problem

Solution

Introduction

This document describes the problem when the import of standard Unified Contact Center Enterprise (UCCE) reports fails on a new Cisco Unified Intelligence Center (CUIC) installation. The problem is usually outside CUIC, very likely on the Structured Query Language (SQL) database on the Administrative Workstation (AW) where the datasource points. Although it might seem that the import process should not be affected by the SQL configuration on the far end, it does seem to process some checks through the datasource and on SQL.

Problem

If permissions for a user specified in the datasource configuration are not correctly set in SQL, the import might fail with this error:

Import could not be completed: 13 reports failed to import. 
For details check the log files.

The logs might show a message similar to this:

Failed to import report '[...]' : The SELECT permission was denied on the 
object '...', database 'co1_hds', schema 'dbo'. <- XMLTransformerImpl.java:2871".

Solution

Run 'Microsoft SQL Server Management Studio' on the AW to which the CUIC datasource points. If this program is not installed on the AW, you can run it from another machine and simply connect to the AW SQL.
In the 'object explorer', expand the Security folder. Go to logins and determine if the user to be used for the datasource exists. If yes, go to step 4.
Right-click the 'logins' folder and choose new login.... In the new window, search for the account which you want and add it.
Assign the necessary mappings to the login.
Choose the Administrative Workstation Database (AWDB) /Historical Data Server (HDS) database and go to the Security folder.
Under the user folder, add a new user and then search for the user just added. Assign the user the appropriate permissions on both the AWDB and HDS databases.