The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly
If you see this message in the Crawl log of a content source, make sure that the site(s) it is crawling are accessible from the index server. Often one of the following has happened:
- The web.config file of the crawled web application contains an error. Especially if the crawl was working yesterday and suddenly it stopped, check the web.config file on the Index server by loggin on to the index server, browse the site and check for errors. Remember to edit the web.config to show detailed error messages (search for ‘stack’ and turn the stack trace to ‘on’, next search for ‘errors’ and turn to ‘off’. Browse again. Sometimes there are solutions which change the web.config through either: web.config.merge.xml file as part of the solution (you will find them in the CONFIG folder) or through the object model. Like adding your own custom navigation provider entry and so on. Duplicates in the web.config file (like duplicate trust level entries) etc are not allowed.
- The target site collection contains a web part error for instance on the default.aspx. Although I did not encounter this myself I read a blog post that said the crawl error was solved by deleting the faulty web part from the site using SharePoint designer
- Also check the solution are not deployed correctly.Central Administration -> Solution Management (Manage Farm Solutions)
Comments
Post a Comment