Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Historical Repoting Crashing with Error 5022

When trying to run a report, Historical Reports crashes. The error message is

"An Exception Error occurred. Application exiting. Check the log file for error 5022."

I'm using verion 3.1(3.2) with MSDAC 2.7

16 REPLIES
Cisco Employee

Re: Historical Repoting Crashing with Error 5022

Pls check if you are running into this

ddts:CSCef56507

New Member

Re: Historical Repoting Crashing with Error 5022

That bug only seems to apply in 3.5, and we're running 3.1

Anyway, I think the problem is I had upgraded to 4.0, then downgraded to 3.1 and there appears to be a conflict in the libraries. After doing a fresh install on the PC, it no longer happend.

Bronze

Re: Historical Repoting Crashing with Error 5022

I just hit this same bug in 4.0(4) We'll probably upgrade to 4.0(5) in a couple weeks.

Here is the bug toolkit link:

http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCef56507

New Member

Re: Historical Repoting Crashing with Error 5022

Worked like a charm.

New Member

Re: Historical Repoting Crashing with Error 5022

Did you modify the Detailed Call CSQ Agent xml file as well? What did you change?

The change in the IVR_Detailed_Call_by_Call_CCDR_en_us.xml worked like a charm.

New Member

Re: Historical Repoting Crashing with Error 5022

Could I get some feedback on this post please?

New Member

Re: Historical Repoting Crashing with Error 5022

Hello,

I have the same problem, but the workaround is not working.

Just one question: this problem applied just for 1 kind of report or is for all the reports? Because I have the problem with all reports...

I have changed this on the file:

SELECT distinct origcallednumber FROM db_cra.dbo.contactcalldetail

to this:

SELECT distinct top 10 origcallednumber FROM db_cra.dbo.contactcalldetail where origcallednumber not in ('')

Thanks in advance for your help,

New Member

Re: Historical Repoting Crashing with Error 5022

Hello,

I have the same problem, but the workaround is not working.

Just one question: this problem applied just for 1 kind of report or is for all the reports? Because I have the problem with all reports...

I have changed this on the file:

SELECT distinct origcallednumber FROM db_cra.dbo.contactcalldetail

to this:

SELECT distinct top 10 origcallednumber FROM db_cra.dbo.contactcalldetail where origcallednumber not in ('')

Thanks in advance for your help,

New Member

Re: Historical Repoting Crashing with Error 5022

Did anyone find a fix for this. I too am getting the same error for all reports.

New Member

Re: Historical Repoting Crashing with Error 5022

I too have experienced that same issue, however only with customer reports.

Did you ever get this resolved?

New Member

Re: Historical Repoting Crashing with Error 5022

no, nobody came to my rescue. The customer didn't pursue the problem.

New Member

Re: Historical Repoting Crashing with Error 5022

I will keep you posted. I am having this problem but only with custom reports. I am using Cisco Historical Reports 5.0 (2.5), which uses SQL instance for accessing the DB.

New Member

Re: Historical Repoting Crashing with Error 5022

I am recieved the same error, have tried varying the Crystal Version from 11.0.0.1282 to 11.5.8.826. I also am using UCCX 5.0(2).

Thanks,

Mark

New Member

Re: Historical Repoting Crashing with Error 5022

Hi,

i'm having the same error the customer is using windows vista Inspirat Ultimate. and IPCCX 5.0(2)SR01_Build053 with Historical Reports 5.0(2.5). i have the problem with all the reports we did no changes on settings of reports, does any one have the solution for this issue?

Thanks.,

New Member

Re: Historical Repoting Crashing with Error 5022

Just a follow up to my previous post. Our issue was only with custom reports that we created. We created our custom reports by copying an existing rpt template, however it appears that HRC did not like this. We then created the custom reports from scratch and that resovled our 5022 error and successfully ran the reports.

NOTE: Cisco uses Crystal Reports XI.

This is what we have.

Report Editor - Crystal Reports XI

IPCCS - 5.0(2)SR01ES01_Build016

HRC - 5.0(2.5)

New Member

Re: Historical Repoting Crashing with Error 5022

The alterations to the client files explained in the BUG workaround solved my problems. I've changed the "IVR_Detailed_Call_by_Call_CCDR_en_us.xml" and the "ICD_Detailed_Call_CSQ_Agent_en_us.xml" files :

SELECT distinct top 3000 callednumber

FROM db_cra.dbo.contactcalldetail

where origcallednumber not in ('')

does anyone knows what is the maximum argument for the "top" instruction that you can put in the SQL Query above descripted?

814
Views
5
Helpful
16
Replies
CreatePlease login to create content