[DM_FULLTEXT_E_SEARCH_FT_ENGINE_INTERNAL_ERROR]

renemann

Hello,

we are having trouble while using the search and advanced search.

The returned error is:

Query execution error for (Docbase_name): [DM_FULLTEXT_E_SEARCH_FT_ENGINE_INTERNAL_ERROR]error

"QRserver Error (1004): No such dataset, Error from QRserver"

Can someone please tell me what this means and what we can do about it.

Kind regards

Rene t Mannetje

Find more posts tagged with

Comments

mszurap

Hi,

If your fulltext web server "admin console" is running, try this url: http://your_ft_server:16000/admin/collections/

On this page there is an overview of the running components of the fulltext server, you can even startup them (maybe one component is not running)

Mike

renemann

Hi Mike,

thanks voor your info , it was helpfull but didn't help us to resolve the problem.

After starting all the processes and restarting the FT-server we still cannot perform an search.

The error given now is:

[DM_FULLTEXT_E_SEARCH_NEW_FAIL]error: "dmFTSearchNew failed with error: Failed to create search engine object: Could not resolve configuration service with name 'fds/configservice':Exception resolving, API Failed, error code:-2"

Rene

XdctmX

Check the below support note -

https://solutions.emc.com/emcsolutionview.asp?id=esg43361

Receive "DM_FULLTEXT_E_SEARCH_NEW_FAIL" when performing a Fulltext search.

SOLUTION Sample of full error message:
DM_FULLTEXT_E_SEARCH_NEW_FAIL error: "dmFTSearchNew failed with error: Failed to create search engine object: Got no response from search engine. Url: http://192.168.1.86:15100/cgi-bin/view2?query=filter(meta.collection:documentum)&resultview=view2&language=en&offset=0&hits=200&filter=+meta.collection:documentum , Error message: HTTP_CLIENT_UNABLE_TO_CONNECT_TO_HOST (10061); apicallfailed, error code: -2"

You may also receive errors in the dmi_queue_item list through DA when trying to index objects. This error can occur if there's a network configuration problem on the Index Server machine.

To resolve this please ensure the following:
1. From the command line on each of the machines where Index Server is installed run the command in A) once towards each machines part of the installation.

A) nslookup <host name or FQDN>

Use the IP address returned (only the first one if several IP addresses are listed) for a reverse lookup for the same machines:

nslookup <IP address retrieved above>

If everything is OK you should end up with getting the same host name or FQDN in the as you entered in A).

2. If the test in 1 did not turn out successfully, then please correct the network setup so that it complies with the reverse nslookup installation prerequisite.

This can be taken care of by updating ALL the DNS server used by the machines part of the installation and/or by editing the host file on each machine.

On Windows one must in addition to updating the host file also set the "binding order" to make sure that the right IP address is listed first if the machine has more then one network card.
This is done by:

1. Open "Network and Dial-up Connections"
2. Advanced-->Advanced Settings
3. Make sure the interface you want to be designated and associated with the hostname is the top one in the "Connections" area.

4. If the test in 1 was successful, try to ping the machine where the Index Server is running to ensure it responds to the ping request and that the IP address responding is the one defined in the dm_ftengine_config object.

5. If Index Server is running on VMware, this is not supported.

renemann

Hi Rijo,

thanks for your suggestions but it still isn't the solution we're looking for. Still we cannot perform an search an still receiving the error message.

I performed every step as in the post but still nothing.

All the processes in the FastInstream are green and running.

we've rebooted the FT-server but this isn't the solution.

Anymore tips are very welcome.

Kind regards,

Rene

renemann

the given error did not appear anymore since a few restarts of the FTI-server.?!