Developer forum

Forum » CMS - Standard features » Search (Weighted) not working (8.5.1.12)

Search (Weighted) not working (8.5.1.12)

E-mail notifications
Jeroen Elias
Reply
Posted on 13/04/2015 15:19:49

Hi all,

After upgrading a solution from DW 7 to DW 8, the weighted search doesn't seem to be working.
I have followed the installation guide (http://developer.dynamicweb.com/Admin/Public/DWSDownload.aspx?File=Files%2fFiler%2fDocumentation%2fInstallation%2f(en-US)+Installation+Guide%2c+Dynamicweb+8+on+IIS+7.pdf) by installing the Indexing Service, together with the Adobe iFilter 6.0. (on Windows 2008R2).
I  created a catalog and I see this catalog being populated. Older Windows versions provided a Query tool for the indexing service, but it's not there any more.

The option "Search (Weighted)" is greyed out in the Modules section in the backend. Is this normal?

Can anyone enlighten me what's wrong here?
 


Replies

 
Nicolai Høeg Pedersen
Posted on 13/04/2015 16:09:53
Reply

Hi Jeroen

If the module is greyed out, it could be why it does not search. If you can provide a link to your solution we can have a look at why the module is not installed.

Also not that, since 8.4.1.8 we have used "Windows Search" instead of Indexing Service because MS have deprecated it on Windows 2012. So on Windows 2012, use Windows Search, on Windows 2008, use Indexing Service.

BR Nicolai

 
Jeroen Elias
Posted on 13/04/2015 16:43:49
Reply

Hi Nicolai,

The link I cannot provide you because this solution runs on the customer's intranet.
The machine in question is a Windows 2008R2 server. Today I installed Indexing Service together with Adobe iFilter 6.0.
The catalog contains documents of the /Filer folder.

 
Nicolai Høeg Pedersen
Posted on 13/04/2015 17:55:12
Reply

Check in module table if weighted search is installed.

Or make a copy of the site available online for us to check out.

 
Jeroen Elias
Posted on 14/04/2015 11:05:31
Reply

The module is there in the table:
SELECT * FROM [dbo].[Module] where ModuleSystemName like 'Search%' gives me:

ModuleID ModuleSystemName ModuleName ModuleAccess ModuleStandard ModuleScript ModuleTypeID ModuleSort ModuleParagraph ModuleDatabase ModuleTable ModuleFieldID ModuleFieldName ModuleWhere ModuleSearch ModuleControlPanel ModuleHiddenMode ModuleSearchIn ModuleDescription ModuleEcomNotInstalledAccess ModuleEcomStandardAccess ModuleEcomExtendedAccess ModuleIsBeta ModuleEcomLightAccess ModuleLightMicro15Access ModuleLightMicro30Access ModuleParagraphEditPath ModuleDefaultPermissions ModuleLightExpressAccess ModuleLightFreeAccess ModuleDeprecated
156 Searchv1 Søg, vægtet 1 0 NULL 0 0 1 NULL NULL NULL NULL NULL 0 NULL 0 NULL Ønsker en bruger, at finde et specifikt område på din webside, kan de med Søg let finde det ønskede. NULL 0 0 0 0 NULL NULL NULL NULL NULL NULL 0  

Now this is ugly :-)

 
Jeroen Elias
Posted on 14/04/2015 11:49:19
Reply

This issue is solved.
It seemed all had to do with misconfigured 404 handling, both in IIS and in DW.
There was no 404 page defined in the backend and no 404 page created in the website.

 
Nicolai Høeg Pedersen
Posted on 14/04/2015 11:51:13
Reply

Hm, seems right.

You need to make the solution available online so we can debug it....

Thanks, Nicolai

 
Nicolai Høeg Pedersen
Posted on 14/04/2015 11:51:41
Reply

Ah, ok - glad you solved it!

 
Jeroen Elias
Posted on 14/04/2015 14:25:38
Reply

It appears to be fixed by editing a list-template of a Global Element and saving it (without even changing anything inside).
This happened also in the Extranet/Intranet (Extended) module.

 

 
Nicolai Høeg Pedersen
Posted on 14/04/2015 14:37:59
Reply

Could be files that are not UTF-8 or something. Editing them will convert to UTF-8 i Think...

 
Jeroen Elias
Posted on 14/04/2015 14:44:05
Reply

This sounds like I have to do this to all the templates?

 

You must be logged in to post in the forum