Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BCM400 Call Centre Reporting Not Working & Skillset Issues

Status
Not open for further replies.

uniquename4me

Technical User
Oct 31, 2013
184
CA
I've got a problem on a 400 4.0 with ACD Pro and only one skillset was giving a greeting and hanging up. I tried to correct it but was unable so I changed the target line and reassigned another skillset. Now I'm trying to delete the skillset and getting unexpected server event 28675. How do I clear this? Is this why the reporting is not working as well?
 
Hi uniquename4me,

The last time I had similar Call Centre issues with this same system, I did a restore from a previous backup and it seemed to help. However, the issue happened again and it turned out to be some faulty sectors on a hard drive... had to re-image on a new one and that fixed it up.

However, before jumping to any such conclusions, maybe we it's not as bad in your case.

If you've changed the target and are using another skillset, and it works - that looks like that's good news.

The only thing I can think of is the old skillset or target lines are perhaps linked/being used by something else??? Maybe go trough and see if there are any settings which depend on those?
 
I've been back to the site and two things. One, the reporting shows two skillset 50's in the list of skillsets being reported on. The second is that the date of Mar6/2013 says the data is corrupt and it won't process past that point whether you try purging or any other method. It won't show traffic beyond that point as well if you ask for a more current report.
 
Which version of RCC are you running. The older MySQL 2.4.360 or MS SQLExpress 2.45.
You can save the database, put in a new template and attempt to retrieve data back from March 6.
Can also try the dbfixutil that sometimes will correct the problem. Otherwise would need to change
the date in the SQL database to a later date then March 6 current time it shows corrupted.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top