Search works in Dev but not in QA

[Former Member]

Hi,

I created a Search iView in our Development System and it worked fine there. However, it does not work in our QA system. I did transport the Search Component and Options Set. I checked the configurations and they seem to be the same in both Dev and QA. The Dev. and QA systems are running on the same versions. Does anyone have any suggestions? Thanks for your valuable time.

Sincerely,

Sri

[Former Member · Accepted solution]

Hi Sri,

did you check the log file for any error messages ?

regards,

Martin

[Former Member · Accepted solution]

Hi Martin,

Thanks a lot for your prompt reply. This is what the log shows:

Error 10/18/05 2:04:40 AM IndexmanagementService AbstractTrexIndex: indexing some of the resources failed

Error 10/18/05 2:04:40 AM IndexmanagementService Indexing document failed. message not found (Errorcode 14015)

Error 10/18/05 1:49:17 AM IndexmanagementService AbstractTrexIndex: indexing some of the resources failed

Error 10/18/05 1:49:16 AM IndexmanagementService Indexing document failed. Filter: No embedded object found in document (Errorcode 14037)

Error 10/18/05 12:47:54 AM IndexmanagementService AbstractTrexIndex: indexing some of the resources failed

Error 10/18/05 12:47:53 AM IndexmanagementService Indexing document failed. Filter: Child process terminated (OS generated error) (Errorcode 14128)

Thanks,

Sri

[Former Member · Accepted solution]

Hi Sri,

is the hostname of the URLGenerator configured correctly?

[Former Member · Accepted solution]

Hi!

Sounds like trouble on the TREX: a crash of a filter process. Do you use the same TREX in dev and QA?

How did you recognize the problem:

- the search doesn't find anything?

- the crawler reports providing errors?

Or does this error only occur for some documents?

Kind regards, Dirk

[Former Member · Accepted solution]

Hi Dirk,

Thanks for your prompt reply. In our Dev box, the TRex version is 6.1.09 while in our QA system, the version is 6.1.13. However, there was another search which I built in our Dev box and that worked fine after we moved to QA. It's just this one which does not seem to work. What happens is that the first time I do a Search nothing gets returned. However, the next time I do a Search results do get returned. However, the search is being done on all the repositories and not on the specific one which I am searching. I also checked the Crawler monitor and it does not show any errors. Thanks for your valuable time and help.

Sincerely,

Sri

[Former Member · Accepted solution]

Hi Dirk,

Just wanted to mention that when I checked the Indexing Monitor, it does show 45 errors. Could that be related to the Search not returning any results?

Thanks,

Sri

[Former Member · Accepted solution]

Hi!

What about the TREX-Monitor? Are there some documents in ok?

Kind regards, Dirk

[Former Member · Accepted solution]

Hi Dirk,

Thanks again for the prompt reply. I went to Display Queues in TRex Monitor. Is that the correct place where you wanted me to go? In there, there are a lot of documents in OK for my index.

Thanks,

Sri

[Former Member · Accepted solution]

Hi!

Yep, it is the right place. If you do a search for * you should see results then (since you get anything what is in ok).

If I understood you right, the search always fails the first time after portal startup and then works?

Or does it fail one time for every new search term and works then?

The errors from the log you posted are not related to the search, but to the process of indexing documents.

Are there additional entries in the log concerning the search?

Kind regards, Dirk

[Former Member · Accepted solution]

Hi Dirk,

Thanks again. Yes, you are right. If I do a search for *, then I see all results. Also, it fails one time for every search term and then it does return results but from all the KM folders (just not the specific one from where I want it to). Also, I again checked the Application Log under "Monitoring" > "KM". ( Again, is that the right place to look into? ) and I did not see any additional information. Thanks for all your help.

Sincerely,

Sri

[Former Member · Accepted solution]

Hi!

As far as I know you can restrict the search by indexes, not by folders (but I don't know everything

Concerning the logs you could have a look into the defaultTrace files on the server.

Kind regards, Dirk

[Former Member · Accepted solution]

Hi,

There is a way to do by folders. There is a property in the Search Options set where you can specify the folders you want to include. It should be entered in csv format but before that the search scope should be set to FOLDER.

The property is called "Root folders for search (Scope = FOLDER) (csv)"

Regards

Prakash

[Former Member · Accepted solution]

Hi Prakash,

Thanks for the reply. Yes, for "Default Search Scope" I did mention FOLDER and for "Root folders for search", I mentioned the path to my folder. Still, can't seem to get it to work. Do you have any suggestions? Thanks for your valuable time.

Sincerely,

Sri

[D021954 · Accepted solution]

Hi Sri,

what is the error message (in UI?) when search fails?

Does the folder belong to the index?

Do you require the folder via UI or vie the Search Option Set?

Regards Matthias

[Former Member · Accepted solution]

Hi Matthias,

Thanks a lot for the reply. When I do a search, the error message which shows up is "No matches have been found". Also, the folder does belong to an index. In my Search Options Set, I have specified the index in "Search Index IDs" and the folder path in "Root folders for Search". Thanks again for your help.

Sincerely,

Sri

[D021954 · Accepted solution]

Hi Sri,

the specificaton of the index isn't necessary but shouldn't matter either.

Did you ever find a document of this specific folder when searching eg on your ndex?

Do you specify any other condiitions?

Regards Matthias

[Former Member · Accepted solution]

Hello Everyone,

Thanks for all the replies. The issue has been resolved. Apparently, the Index was'nt replicated in QA. It seems that automatic replication should have been turned on, which in this case was'nt. So, once the index was replicated, the search iview was able to return the results. Thanks to all of you for all your valuable time and help.

Sincerely,

Sri

P.S. I have awarded points to everyone.