Page 1 of 1

Search failed (7) Error communicating with the server

Posted: Sun Oct 20, 2013 12:04 pm
by Hamish
I am getting this. I have had it before but recently it has happened more often.

Is this something to do with the search servers? What does the number in brackets mean?

The message wording leads me to think that the problem is at my end. So I've reset the search configuration, turned off my firewall and virus checker but I still get it.

If this is a server problem then could you replace the message with something like "Search server(s) not responding" so it lets the user know it isn't their own configuration.

Cheers

Re: Search failed (7) Error communicating with the server

Posted: Tue Oct 22, 2013 12:57 am
by alex
do you see other numbers or it is always (7), if not what other numbers it shows?

i could check then if there is a correlation.

Re: Search failed (7) Error communicating with the server

Posted: Tue Oct 22, 2013 6:43 am
by Hamish
I've just done some searchers in succession. The numbers were: 9, 8, 5, 9, 5, 8, 6, 9, 6, 7

Are these the numbers of the search servers?

Re: Search failed (7) Error communicating with the server

Posted: Wed Oct 23, 2013 7:22 pm
by alex
It is one location but more than one computer, unlikely to be a search service computer issue. Try to reboot the router, check if there is any change. I've reset the search count to see if there is any significant difference between the locations.

Re: Search failed (7) Error communicating with the server

Posted: Mon Oct 28, 2013 2:11 pm
by Hamish
I've rebooted the router.

I get the same problem. Server numbers were: 9,9,6,9,9,5

Re: Search failed (7) Error communicating with the server

Posted: Wed Oct 30, 2013 3:43 am
by alex
I've checked, I reset counter 152 hours ago. The difference is 42, it might be you are the only one who is affected.

I'll send you pm how to ping, maybe you'll see occational timeouts.

Update: The problem was edit menu->properties->tasks, read xpat timeout which is employed by UE for search service as well was changed by the user from the default to only few seconds, so it was just timeout because of the too low setting.