About Me

My photo
Grant, Florida, United States
I have been in the technology industry for almost 10 years always jumping at the opportunity to learn something new. I founded the Space Coast SQL Users Group to keep me from getting obsolete. When I am not in “Tech-Mode” I love spending time with my family golfing, bowling, boating, fishing, scuba diving, motorcycling and whatever else we come up with.

Monday, March 15, 2010

Cisco Unified CCX Historical Reports Problems

Cisco Unified CCX Historical Reports – printing problems
In order to print a report to a network printer you must set the hrcConfig file to
UseSharedMemory = 1
Default setting is 0

If your DB is using Windows NT Authentication you need set hrcConfig file to connection method = 1
Default setting is 0 which is mixed mode

If you ever need to restore your UCCX CRA_DB and create reports that match Cisco Unified CCX Historical Reports here’s the short cut.
set the hrcConfig file LogLevel = 3 , ( logLevel = 3 then debug messages, warnings and errors)
Launch Cisco Unified CCX Historical Reports on a client, select and run a report
Find the CiscoAppReports0 file by default the file is located in
C:\Program Files\Cisco UCCX Historical Reports\logs\(Machine name)_CiscoAppReports0
You will see the stored procedure that was executed in the file; it will look something like this:
Exec db_cra.dbo.sp_agent_summary '$StartDate', '$EndDate', $SortBy, N'$ResourceGroup', N'$AgentName', N'$SkillName', N'$TeamName', $TopRatio, $BottomRatio, $TopHold, $BottomHold, $TopTalk, $BottomTalk, $TopWrap, $BottomWrap, $TopHandle, $BottomHandle 117: 3/15/2010 3:44:09 PM %CHC-LOG_SUBFAC-7-UNK:DB Layer Current Query=Exec db_cra.dbo.sp_agent_summary '03/14/2010 12:00:00 AM', '03/15/2010 12:00:00 AM', 0, N'NULL
Copy and paste in the management studio run against the DB of the server.
Execute the query and the results will match what would have been available in Cisco Unified CCX Historical Reports
The above scenario is great if you are running UCCX using MSDE and the db purges after 2gb or if you have just migrated and do not want to import historical data.
Additionally you can prove or disprove the application is having problems not the database.
Just make sure you have a backup scheduled to run daily so you can restore prior to running the report.

4 comments:

rreif said...

Hi Bonnie,

I try to monitor the internet for those UCCX users who are not happy with the inherent reporting tool. I want to reach out the "experts", like yourself, to let you know we can assist. We develop a suite of Call Center applications that can greatly enhance the reporting aspects of the UCCX. Both Historical & Ad-hoc Custom reporting tools as well as Current Status tools to view real time statistical information. If you would like further information call me.
Ron Reif / SMSI / 651-635-2822 / rreif@smsi.com.

Ralphael Anton Sugito said...

Hi Bonnie,

I tried to install UCCX Historical Reports in windows 7 Enterprise 64 bit. However, I always get this error


Error 1722:There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action caInstallDBDriverMsiexec,location:...\hrcdbdriverin...

Ralphael Anton Sugito said...

Hi Bonnie,

I tried to install UCCX Historical Reports in windows 7 Enterprise 64 bit. However, I always get this error


Error 1722:There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action caInstallDBDriverMsiexec,location:...\hrcdbdriverin...

SeNnDoh said...

Hi, need your advice on this..

Lets say I want to create a custom report and I can use the stored procedure namely sp_common_skill_csq_interval(). However, the SP didnt return the required field I need to complete the report. I need the avg call time which I can found it in another SP. But that SP1 didnt have what SP2 have and vice versa.

So how to overcome this? Any suggestion?

Thanks in advance.