-
-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error indexing pages with 2sxc instances not yet configured #1802
Comments
thx, we'll look into this - don't want to clog up the event-log :) |
I just tried to reproduce this and couldn't get the error index entries. I was using DNN 9.4 RC1 and 2sxc 10.05, but I'm sure nothing changed. Could you re-verify or help me reproduce this issue? |
Closed because of inactivity, will reopen if it surfaces again. |
This issue has appeared on a new DNN v09.06.01 install running 2SXC v11.02.00. Blank 2SXC module fills event log with errors starting with, "Search: Error while indexing module..." |
I am still having this issue and thousands of entries get added every couple hours. I am now running v11.11.0. |
New site in development running DNN 09.08.00 and 2SXC 11.11.1, log has thousands of entries like the one below. This particular app uses a view with a Default data stream from a query, but I am not sure if that makes a difference. The only way I can keep my log from filling up is to only run the search scheduler once a day, which is not an ideal work around.
|
Hi folks, can anyone else verify this issue? Our site is in production now but I've had to throttle the search indexer to daily to keep the logs from filling up. |
Something seems to cause trouble finding the current culture. I'll have to look deeper into it, and/or find a way to only log a certain amount of errors and then stop. |
and prevent search index from logging more than 10 issues
I just implemented limiting events logged to 10 (but you could override it in code, in case you really need to debug deeper - after 10 entries it explains how to do that). |
Thank you so much. I am wondering if the issue with the culture is also related to the DNN issue I raised about portal aliases since I know there were some issues in a couple of the latest releases with redirect issues: |
I'm submitting a ...
[x] bug report
...about
[x] DNN parts
Current behavior
If you create a page and click "add module", select "Content" and confirm, the module is added to the page without being configured. When leaving in this state, the DNN search indexer logs an error: Error while indexing module 1636 on tab 420, portal 5
StackTrace:
at ToSic.SexyContent.Environment.Dnn7.DnnBusinessController.GetModifiedSearchDocuments(ModuleInfo moduleInfo, DateTime beginDate) in C:\Projects\2sxc-dnn742\Website\DesktopModules\ToSIC_SexyContent\2sxc Dnn\Environment\Dnn7\DnnBusinessController.cs:line 104
at DotNetNuke.Services.Search.ModuleIndexer.IndexSearchDocuments(Int32 portalId, ScheduleHistoryItem schedule, DateTime startDateLocal, Action`1 indexer)
InnerMessage:Object reference not set to an instance of an object.
InnerStackTrace:
at ToSic.SexyContent.Environment.Dnn7.Search.SearchController.GetModifiedSearchDocuments(IInstanceInfo instance, DateTime beginDate) in C:\Projects\2sxc-dnn742\Website\DesktopModules\ToSIC_SexyContent\2sxc Dnn\Search\SearchController.cs:line 69
at ToSic.SexyContent.Environment.Dnn7.DnnBusinessController.GetModifiedSearchDocuments(ModuleInfo moduleInfo, DateTime beginDate) in C:\Projects\2sxc-dnn742\Website\DesktopModules\ToSIC_SexyContent\2sxc Dnn\Environment\Dnn7\DnnBusinessController.cs:line 98
Source:ToSic.Sxc.Dnn
Expected behavior
no error is logged
Please tell us about your environment:
Windows Server 2012R2
The text was updated successfully, but these errors were encountered: