09-10-2012 12:59 PM - edited 03-14-2019 10:29 AM
Hi All,
Last week (on Thursday) our Historical Data stopped capturing any details?
I have captured a screen shot of the report. You can see that the agent logged in time is 111:47:23 (at 3:47:23pm EST). Any help fixing the issue would be greatly appreciated!
Thanks in advance!
Craig
09-10-2012 07:23 PM
Hi Craig,
From the other thread you have opened, looks like you have CRS 5.x High availability setup.
https://supportforums.cisco.com/thread/2170238?tstart=0
As there were few services down in second node, now that it got fixed.
Please try fetching the HRC reports through the HRC client and check again.
Thanks,
Anand
Please rate helpful posts !!
09-11-2012 07:23 AM
Hi Anand,
Thanks for the information, and you're correct that we're usuing a HA setup.
You mentioned that I should, "Please try fetching the HRC reports through the HRC client and check again."
How do I do that?
Thanks in advance!
09-11-2012 07:34 AM
Hi Craig,
If you have already installed HRC (Historical Reporting Clinet), use the Reporting User credentials to login into it and fetch the report for the required duration.
For installing HRC,
Login into UCCX Admin->Tools->Plug-ins->Cisco Unified CCX Historical Reports
You can verify if the client PC\desktop for using the HRC from the below link,
Hope this helps.
Anand
Pls rate helpful posts !!
09-11-2012 08:32 AM
Hi Anand,
Yes, I have that installed, and ran the reports again from both the primary and secondary server. I'm still not getting the information? I get 0's across the board for agent stats, and the login time is still showing the same results.
When I validate in CRS -> Control Center I validated the CRS SQL Server - Agent, CRS SQL Server - Config,
CRS SQL Server -> Historical, and CRS SQL Server - Repository are all up (on both the Master and Slave).
The CRS Engine on the secondary server is out of date (it shows 12/15/05 10:20pm). Should I stop and start the CRS Engine, and will that fix the historical reports not working?
Thanks!
09-11-2012 08:40 AM
Hi Craig,
Subscriber Goes Down
When the subscriber goes down for more than the 2- or 4-day retention period,
reinitialize the subscriber in CRS Administration (Datastore Control Center web
page) and reinitialize the subscription for all the datastores.
Access the Datastore Control Center by selecting System > Datastore Control
Center from the CRS Administration menu bar.
Reinit Subscriber—Click this button to reinitialize the subscriber with a
copy of data from the Publisher. (This causes the data on the subscriber to be
overwritten by the data from the Publisher.)
Note Only use this button if you have determined that the Subscriber needs this
data from the Publisher (if the Subscriber and the Publisher are not
synchronized).
Hope this helps.
Anand
Please rate all helpful posts by clicking on the stars below the helpful posts !!
09-12-2012 10:46 AM
Hi Craig,
Were you able to fetch HRC reports?
Thanks,
Anand
09-13-2012 07:02 AM
Hi Anand,
Yes, that worked!
I selected the "reset publication" option on all 3 functions (historical, repository, and agent), so it can push the replication.
I did run a test to find all data are there
Thangs again for all your help!
09-13-2012 07:33 AM
Hi Craig,
Glad to know that, please mark this query as answered and rate all the helpful posts :-)
Thanks,
Anand
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide