Timeline for Rebuild Reporting Database procedure fails with "Aggregation task not found" error
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Nov 30, 2017 at 14:41 | comment | added | Michael Smith | If that's the case, is it likely that adding those tables would also resolve the issue? | |
Nov 30, 2017 at 7:14 | answer | added | Hishaam Namooya | timeline score: 3 | |
Nov 30, 2017 at 6:29 | comment | added | Hishaam Namooya | Your issue is with the Sitecore.WFFM.Analytics.Aggregation.Processors.FormEvents. Try to comment it and see if the error goes away. Note that you need to see the version of the release note of the module WFFM you are using because if the table is no more present that mentioned pipeline should not be present or you may have miss the creation of the table formevents. I have not used WFFM on sitecore XP but please see into the notes. As a workaround, comment out the WFFM aggregation pipelines | |
Nov 29, 2017 at 19:34 | comment | added | Michael Smith | Sure. Added to the main question, as it was too large to put in a comment. | |
Nov 29, 2017 at 19:34 | history | edited | Michael Smith | CC BY-SA 3.0 |
added 5895 characters in body
|
Nov 29, 2017 at 15:49 | comment | added | Hishaam Namooya |
Can you share the different aggregation processors that you have. It is at the following xpath: pipelines -> group groupName="analytics.aggregation" -> pipelines -> interactions
|
|
Nov 29, 2017 at 15:01 | comment | added | Michael Smith | We don't have a stack trace on the aggregation error, but I've added a bit of context. | |
Nov 29, 2017 at 15:01 | history | edited | Michael Smith | CC BY-SA 3.0 |
added 2511 characters in body
|
Nov 29, 2017 at 14:20 | comment | added | Dmytro Shevchenko | If you have a complete stack trace, please edit your post to include that. | |
Nov 29, 2017 at 12:27 | answer | added | Ankit Joshi | timeline score: 0 | |
Nov 28, 2017 at 13:49 | comment | added | Hishaam Namooya | You need to have those aggregation pipelines to be fixed. The reason is because this is executed sequentially. So, if one gets an error, the other aggregations will not be executed | |
Nov 27, 2017 at 21:10 | comment | added | Naim Alkouki | check this article kb.sitecore.net/articles/977445 Good luck, Naim | |
Nov 27, 2017 at 16:16 | history | asked | Michael Smith | CC BY-SA 3.0 |