DNN Forums

Ask questions about your website to get help learning DNN and help resolve issues.

Issues with DNN Search Functionality

 4 Replies
 1 Subscribed to this topic
 18 Subscribed to this forum
Sort:
Author
Messages
New Around Here Send Private Message
Posts: 7
New Around Here

The portal is currently running on DNN version 9.9.0. I initially upgraded to version 9.10.2, but during the update in the browser, I received a 502 error. After refreshing the page, everything seemed fine. I then attempted to remove Telerik, and while installing the Resource Manager module, the 502 error reappeared. After another page refresh, the issue seemed resolved. Ultimately, I decided to restore the site to version 9.9.0 using a previously made backup.

After checking the logs, I noticed a recurring general exception related to Lucene that has been appearing for months.

- Here is an example of the error:

General Exception AbsoluteURL DefaultDataProvider DotNetNuke.Data.SqlDataProvider DotNetNuke AbsoluteURL: DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke ExceptionGUID:9811f6a1-7486-4312-8a50-938b6b6fa240 AssemblyVersion: PortalId:-1 UserId:-1 TabId:-1 RawUrl: Referrer: UserAgent: ExceptionHash:EGZHbM0vOAj2Aq6c6aIdYvTUvNA= Message:Index was outside the bounds of the array. StackTrace: at Lucene.Net.Util.BitVector.Get(Int32 bit) at Lucene.Net.Index.SegmentTermDocs.ReadNoTf(Int32[] docs, Int32[] freqs, Int32 length) at Lucene.Net.Search.TermScorer.NextDoc() at Lucene.Net.Search.ConjunctionScorer..ctor(Similarity similarity, Scorer[] scorers) at Lucene.Net.Search.BooleanScorer2.CountingConjunctionSumScorer(List`1 requiredScorers) at Lucene.Net.Search.BooleanScorer2.MakeCountingSumScorerSomeReq() at Lucene.Net.Search.BooleanScorer2..ctor(Similarity similarity, Int32 minNrShouldMatch, List`1 required, List`1 prohibited, List`1 optional) at Lucene.Net.Search.BooleanQuery.BooleanWeight.Scorer(IndexReader reader, Boolean scoreDocsInOrder, Boolean topScorer) at Lucene.Net.Index.DocumentsWriter.ApplyDeletes(IndexReader reader, Int32 docIDStart) at Lucene.Net.Index.DocumentsWriter.ApplyDeletes(SegmentInfos infos) at Lucene.Net.Index.IndexWriter.ApplyDeletes() at Lucene.Net.Index.IndexWriter.DoFlushInternal(Boolean flushDocStores, Boolean flushDeletes) at Lucene.Net.Index.IndexWriter.DoFlush(Boolean flushDocStores, Boolean flushDeletes) at Lucene.Net.Index.IndexWriter.PrepareCommit(IDictionary`2 commitUserData) at Lucene.Net.Index.IndexWriter.Commit(IDictionary`2 commitUserData) at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.Commit() at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork() InnerMessage: InnerStackTrace: Source:Lucene.Net FileName: FileLineNumber:0 FileColumnNumber:0 Method: Server Name:

- The scheduler shows the following error during content indexing:

Search: Site Crawler
Starting. Content change start time 9/19/2023 12:22 PM
  Deleted Objects: 0
  Tabs Indexed: 6
  Modules (Metadata) Indexed: 5
  Modules (Content) Indexed: 41
  Users: 64
Total Items Indexed: 116
EXCEPTION: Index was outside the bounds of the array.

Problems with the Search Bar:
  The search bar does not return any results.
  Clicking on the "search" option in the site settings menu does nothing and generates an error in the browser console -> 
API/PersonaBar/SiteSettings/GetBasicSearchSettings:1 Failed to load resource: the server responded with a status of 502 ()

 

Any suggestions or similar experiences that could help me resolve these issues would be greatly appreciated.

Thank you in advance for your help!


Note: The site was previously moved from one server to another, and uses EasyDnnNews module

Veteran Member Send Private Message
Posts: 350
Veteran Member
A 502 error indicates something wrong, most likely, beyond the purview of DNN. It is most likely due to the way the web server and/or proxy is setup. By the way, I highly recommend upgrading to the latest version of DNN (currently 9.13.3).

David Poindexter


Creator:


Senior Member Send Private Message
Posts: 1542
Senior Member
I agree with David. Upgrading DNN can often resolve a lot of issues. It really should be kept up with. Troubleshooting an older version is not really a great idea, unless it's a configuration issue. In this case, there's clearly something much larger in scope.
Growing Member Send Private Message
Posts: 82
Growing Member
Resetting Lucene might help, or get you past that error to find the cause of the 502.

First, please take a backup !
Then...

In Scheduler
DISABLE the Search: Site Crawler

Delete contents of /App_Data/Search
(might need to put site offline or recycle the application pool first to do this)

In SQL Console

-- start reindex for all portals, file crawler
DELETE SH FROM ScheduleHistory SH
INNER JOIN Schedule S
ON SH.ScheduleID = S.ScheduleID
WHERE S.TypeFullName = 'DotNetNuke.Services.Search.SearchEngineScheduler,DOTNETNUKE'
OR S.TypeFullName = 'DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE'

In Scheduler
RE-ENABLE the Search Crawler

In Site Settings -> Search -> Basic Settings
re-index Content
AND re-index Host Content

In Settings -> Servers
Clear Cache

In Scheduler
Check that the Scheduler has actually started !!!


THAT MIGHT BE ENOUGH, OR IF Search Crawler shows a write.lock error like this ...
Search: Site Crawler
Starting. Content change start time 1/25/2024 7:43 PM
EXCEPTION: Lock obtain timed out: NativeFSLock@[path]\App_Data\Search\write.lock

In Settings -> Servers -> Web Servers
UNLESS you run a web farm there should only be 1 entry for your web server which should have url that matches the live site address - edit if not the case
then restart the application
Check the Scheduler again
make sure it started (start it if needed)
Advanced Member Send Private Message
Posts: 128
Advanced Member
I would always try and upgrade to the latest version before I start troubleshooting. It sounds like you can upgrade?, but the removal of the Telerik causes an error?
Can you give us more information about the upgrade error, I think that is the one that you need to solve first.

These Forums are dedicated to the discussion of DNN Platform.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. If you have (suspected) security issues, please DO NOT post them in the forums but instead follow the official DNN security policy
  2. No Advertising. This includes the promotion of commercial and non-commercial products or services which are not directly related to DNN.
  3. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  4. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  5. No Flaming or Trolling.
  6. No Profanity, Racism, or Prejudice.
  7. Site Moderators have the final word on approving / removing a thread or post or comment.
  8. English language posting only, please.

Would you like to help us?

Awesome! Simply post in the forums using the link below and we'll get you started.

Get Involved