11-09-2010 06:35 AM - edited 03-14-2019 06:51 AM
I'm running CRS 7.0(1)SR05 and have found out that since sunday (daylight savings time), our historical reporting is saying that "There were no report data to view in the date range selected.....". I know there is data since we take generally between 300 - 500 calls a day. Any ideas?
Thanks in advance,
Michael
Solved! Go to Solution.
11-09-2010 06:54 AM
Hello Michael,
First, check in SQL db to see if data is available for those dates. If there's data there, we know the problem is with the Historical Reporting.
- Do you have an HA node?
Please go to System> Datastore Control Center> Publisher Activation page from Appadmin. It will display the Historical datastore; are there any error messages shown? What is the replication status? You can send a screenshot.
Pablo
11-09-2010 07:41 AM
Actually it seems you do have an HA server.
You can check the ContactCallDetail table in db_cra.
Please try this; select the Publication Snapshot Agent and click the Reset Publisher button - click OK. It could take about a minute to refresh. Hopefully when it comes back, the error should be gone. This should fix the replication problem. Please also check the Repository and Agent datastores to see the status and try the same if necessary. Check if that makes any difference.
HTH
Pablo
11-09-2010 06:54 AM
Hello Michael,
First, check in SQL db to see if data is available for those dates. If there's data there, we know the problem is with the Historical Reporting.
- Do you have an HA node?
Please go to System> Datastore Control Center> Publisher Activation page from Appadmin. It will display the Historical datastore; are there any error messages shown? What is the replication status? You can send a screenshot.
Pablo
11-09-2010 07:05 AM
11-09-2010 07:41 AM
Actually it seems you do have an HA server.
You can check the ContactCallDetail table in db_cra.
Please try this; select the Publication Snapshot Agent and click the Reset Publisher button - click OK. It could take about a minute to refresh. Hopefully when it comes back, the error should be gone. This should fix the replication problem. Please also check the Repository and Agent datastores to see the status and try the same if necessary. Check if that makes any difference.
HTH
Pablo
11-09-2010 07:51 AM
That fixed it. Thanks for your help.
11-09-2010 08:04 AM
Thanks great Mike!
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