search cancel

"Invalid response received from federated search server" error with the Sharepoint Search.


Article ID: 38952


Updated On:


SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service CA Service Desk Manager CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager



The following error appears when it tries to run the Sharepoint Search.

"Invalid response received from federated search server. Please contact your system administrator."



SDM r12.9

SDM r14.1



This error message is a generic message. There are several possible causes regarding the configuration.?The federated search will update the log to the $NX_ROOT\log\jfedsearch.log. In order to check the detail of this error, it is necessary to review the jfedsearch.log first.

*)?$NX_ROOT is SDM's installation directory.



When a similar logs with the below are updated in the jfedsearch.log... :

Case 1)?

05/09 15:22:26.743 [http-bio-8040-exec-2] ERROR SearchService 291 Timeout occurred for adapters([[email protected]4b3719]) on uri(http://<hostname>:8040/cafedsearch/sdm/search?q=server&source=sharepoint&userid=ServiceDesk&index=1&size=10&_type=json)
05/09 15:22:28.615 [pool-11-thread-1] INFO  HTTPSender 196 Unable to sendViaPost to url[http://<hostname>:80/_vti_bin/search.asmx] Read timed out
Case 1 Resolution)
1. Check the DNS between the SDM server of the federated search and Sharepoint server. Even if the ping reaches bi-directionally, DNS server or each hosts file does not have the DNS information, there is the above situation. Try to set the DNS during them.

2. The sharepoint server may not return the response to the SDM by the timeout value. The SDM will wait for the Sharepoint response for 10 seconds as a default. It is possible to align the timeout settings in the $NX_ROOT\bopcfg\www\CATALINA_BASE_FS\webapps\cafedsearch\WEB-INF\web.xml.The below part is the settings for that.
            <!-- Timeout (in seconds) for client search requests -->
After modifying the above settings, it is necessary to recycle the tomcat service.
Case 2)

07/01 03:26:15.027 [pool-11-thread-4] INFO  HTTPSender 196 Unable to sendViaPost to url[http://<hostname>:80/_vti_bin/search.asmx] Connection timed out: connect ?
Case 2 Resolution)
1. There is a possibility that the tomcat for federated search may have a problem.  The tomcat service recycling may solve the problem.

2. Windows Personal Firewall may be enabled. After disabling the personal firewall, recycle the tomcat service. It may solve the problem.


Case 3)

10/12 16:20:22.679 [http-bio-8040-exec-8] ERROR SearchService 327 Timeout occurred for adapters([[email protected]99439c]) on uri(http://<hostname>:8040/cafedsearch/sdm/search?q=test&source=sharepoint&userid=ServiceDesk&bopsid=2096234014&roleId=10002&index=1&size=10&_type=json)
10/12 16:20:22.739 [pool-11-thread-1] INFO  HTTPSender 196 Unable to sendViaPost to url[http://<hostname>:80/_vti_bin/search.asmx]
org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 10000 ms
Case 3 Resolution)
Check if the hostname settings in the sharepoint.xml is correct.
Case 4)
01/19 14:42:05.587 [http-bio-8040-exec-6] ERROR SearchService 305 Timeout occurred for adapters([[email protected]48e733]) on uri(http://<hostname>:8040/cafedsearch/sdm/search?q=test&source=sharepoint&userid=ServiceDesk&bopsid=789582557&index=1&size=10&_type=json)

01/19 14:42:08.982 [pool-11-thread-2] INFO  HTTPSender 196 Unable to sendViaPost to url[http://<hostname>:8040/_vti_bin/search.asmx] Connection refused: connect

Case 4 Resolution)

Check if the portNumber settings in the sharepoint.xml is correct.

Additional Information:

The way for recycling the tomcat for the federated search is to run the following commands on the command prompt.

pdm_tomcat_nxd -c stop -t FS
pdm_tomcat_nxd -c start -t FS


Release: SDMU0M99000-14.1-Service Desk Manager-Full License