Hi Peter,

I recently upgraded my installation to 5.0.1 and went to search for documents using hte Lucene search engine and am no longer getting anything back.  I got the Luke Debugger and when I go to open the index I get the following error: No sub-file with id _3j75.f17 found.  Is it possible that the Index needs to be rebuilt and if so how do I do this?  I don't think it's a problem wtih DMX as the search engine works fine on my local dev box.  One other itme to note, where the search is not working the files are not located in default location.  I don't know if that has anything to do with it but wanted to pass that along.

Thanks,

Arick

 

 

Hi Arick,

Reindexing can be done through a script (DMX menu, Admin > Run Scripts). The index files are stored under Portals/[id]/DMX/Lucene. If you delete all of that and reindex everything will be refreshed. But a regular reindex should also do the job.

What might plague you is file permissions if you roll out your installation using xcopy from staging/dev server to production. Frequently fiel permissions change and some components may break.

If you keep having issues in production you might want to have a look at Indexing Service. It is more of a hassle to set up, but it should be less prone to file issues.

Peter

Peter,

Deleting the files and re-indexing fixed the search from the DMX Tool menu. I am still having a problem using search within DNN. With the DMX script to add DMX Search to the DNN Search results page, and search the same item I never get any results back. This again is something that is working locally but not in my production environment. Any suggestions? Let me know if you need a login/password to investigate further and I will send you that information.

Thanks again,
Arick

Hi Arick,
Yes, send me details at peter at bring2mind dot net and I'll have a look.
Peter

Hi Peter,

After doing a bit more research on this I may have uncovered the problem behind why the DNN search is not working. When I look at the DMX_SearchResults table on the production SQL Database I see results after I search using the built in DMX Search. When I use the DNN Search that table is automatically cleared. When I preform this same action on my development box the table remains populated. Not sure if this is the root cause but I hope it points us in the right direction to solving this issue.

In case I haven't mentioned it before the server having the problems started at version 3, upgraded to version 4 and now running 5. My development version started at version 4.

Thanks,
Arick

Hi Arick,
It does point to an issue. I'll make a note of it.
Thanks,
Peter

Great, is there anything I can do in the mean time to get this functionality working? A stored procedure or file that can be fixed?

Thanks,
Arick

Hi Arick,
I can't think of anything. Note that a session ID is used to keep track of search results. Is there a difference in the availability of session IDs? Is the app pool recycling constantly?
Peter

Hi Peter,

Thanks for getting back to me. I don't believe there is a difference in Session ID's but since the DMX_SearchResults table is being cleared it's hard to say what is actually happening. Are you using a custom stored procedure to write to this table or integrating into a DNN stored proc? My best guess with the fact that the table is being cleared out and not repopulated is a stored proc is not setup correctly, but I'm at a loss for which one could be doing that as I did not find any procedure that wrote to the DMX_SearchResults table. If you can let me know which procedures you tied into I could continue to troubleshoot and compare my working vs. non working sites on this issue.

Thanks,
Arick

Hi Arick,

Search results are filled to the table by the search provider. What happens with filling is that:
1. All search results from previous days are deleted (i.e. SearchID does not start with today's date)
2. All search results from the current Session ID are deleted (i.e. today with session ID appended)
3. Search results are inserted into SearchResults table

Both the integrated search in the DMX module as well as the module on the search results page use the same logic. So the clearing of the table is probably the result of the fact that no results were found. There have been issues with the search in DMX 05.00.00 but these have been repaired since.

Peter

Peter,

That's the logic that I thought was happening which confirms there is a disconnect between the DNN Search and the DMX Module Search engine. I will continue to investigate on my end to try and resolve this issue, unless there is something else you can think of that I can look into.

-Arick

Hi Arick,
If need be I can have a look if I can see the installation from here. Give me some time though as I'm working away my backlog this week after coming back to the office from a break.
Peter

Peter,

Thank you, let me know if you need anything from me.

Arick

Hi Arick,

Could you contact me by email with details so I can see the installation? I can't replicate this, so the only way I could help is by going into your installation to look.

Peter

Hi Peter,

Here is what I've done thus far in an attempt to fix this problem, and am now at a loss on what to look at. I've moved testing installation to my development box,copied all DNN files from my development install to my testing installation and re-indexed the DMX installation. The DNN Search returns results but when I search for documents I am still not getting any documents returned. Is there a particular DMX stored procedure or table that I should be looking for in an attempt to resolve this problem? I'm contemplating backing up the database and files, removing DMX and re-installing DMX from scratch to see if that resolves my problem. I'm fairly confident the issue is something left over from an upgrade process. I have upgraded from DNN 3 to 4 and DMX from 3 to now 5. I'm open to any suggestions or thoughts as to what can be done to resolve this issue. I am at a loss for where to begin searching for this problem.

Thanks,
Arick

Hi Arick,

First try to determine where the issue is. Do this by (1) using Luke to see if content is being indexed and (2) by checking DMX_SearchResults to see if search results are being handed down by the search provider. There is no 'SPROC' for searching as it is a process in stages. But if you know at what stage it goes wrong we may be able to narrow it down.

Note that DNN search (i.e. the regular DNN search results module on the page with the same name) is independent of anything you do with DMX. Or were you refering to the DMX instance on the DNN search results page?

Peter

Hi Peter,

Here is what I know 1) Luke returns results when searching. 2) If I use Tools->Search from within DMX the DMX_SearchResults Table is populated; however, when I use the DNN Search I get no results in the DMX instance on the DNN Search Results page, and DMX_SearchResults is empty. So the stage at where it's breaking is when DMX_SearchResults is cleared and re-populated for the DMX Search instance on the DNN Search Screen. Please let me know if you need the URL and login again for this machine, I will be happy to send this your way.

Thanks,
Arick