Go Back   TechArena Community > Software > Windows Software
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Error: "The crawler could not communicate with the server"

Windows Software


Reply
 
Thread Tools Search this Thread
  #1  
Old 05-02-2011
Member
 
Join Date: Nov 2008
Posts: 1,054
Error: "The crawler could not communicate with the server"
  

If, looking at the log produced by the indexing service to search for MOSS 2007 on one of the content source that you configured, you find an error like this:

"The crawler Could not communicate with the server. Check That the server is available and That the firewall access is configured Correctly."

Immediately checked the address that is specified as the source of the error trying to reach through the browser using the Remote Desktop connection on your machine that deal with indexing. You probably have a farm where one or more servers involved in providing part of the SharePoint front-end server and one or more of the indexing. And maybe you see the address as the source of the error, if reached by the client machines, you will surely works. But if you try to get from one machine indexing, you will see that you return a 5xx error type. So try to understand why that error 500 and, once corrected, restart indexing. In my case, the application pool had been stopped and simply restart. I hope it will be useful to someone.

Reply With Quote
  #2  
Old 05-02-2011
Member
 
Join Date: Nov 2008
Posts: 1,514
Re: Error: "The crawler could not communicate with the server"

Here I have provided the help for one more famous error that you may face on your Sharepoint. ie. The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired. If trying to open your "My Site" from any page of the SharePoint 2007 site collection, you are faced with this error (and you're sure to have a valid version of MOSS):

"The evaluation version of Microsoft Office SharePoint Server 2007 for this server has expired."

Your version of MOSS 2007 is not expired, but there is only a little bit wrong .. In fact, despite this error, you will find that you can still create new site collection, and new sites, give permissions, create lists, etc. .. as you have always been doing. To resolve this problem, which completely prevents the navigation in your "My Site" for all users, open the registry and change the permissions of the registry key "HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Office Server \ 12.0 "this way:
  • Reading group WSS_WPG
  • Full control group WSS_ADMIN_WPG
I hope it will be useful to someone.
Reply With Quote
  #3  
Old 05-02-2011
Member
 
Join Date: May 2008
Posts: 913
Re: Error: "The crawler could not communicate with the server"

Some time ago we saw how it is possible to move a SharePoint site or some of its main objects (lists, documents, items, etc. ..) from the program, using the API for migration and deployment of content exposed by SharePoint. The same moves, as we know, you can also use the backup and restore utility STSADM, those present in the Central Administration, rather than you can find in SharePoint Designer or (but only if you have MOSS 2007 and the publishing feature enabled at the site collection) via the management tools of SharePoint content, the tool "Site manager" (which you can reach by selecting "Site settings" - "Content and structure").
Reply With Quote
  #4  
Old 05-02-2011
Member
 
Join Date: May 2008
Posts: 860
Re: Error: "The crawler could not communicate with the server"

If you want to write a custom application that you make the move to a site within the same Site Collection SharePoint provides us with a further technique much easier to use what is called "reparent" (which, I must say truth, I do not know how you can translate in Italian). Using this technique, we can move a SharePoint site within the same site collection without any backup or restore. To use it, we do not have to do is enter in our application the following code (after adding the reference library Microsoft.SharePoint.dll):
Code:
  oldUrl string = "http://servername/DaSpostare/";

  newURL string = "Peppe / Moved";

  using (SPSite site = new SPSite (oldUrl))

  using (SPWeb web = site.OpenWeb ())

  {

  web.ServerRelativeUrl = newURL;

  web.Update ();

  }
Reply With Quote
  #5  
Old 06-02-2011
Member
 
Join Date: Jun 2009
Posts: 1,518
Re: Error: "The crawler could not communicate with the server"

In this example, the site moved from the address "http://servername/DaSpostare" at "http://servername/Peppe/Spostato. Then, simply arises to change the value of property "ServerRelativeUrl" an object of type SPWeb we can move the site within the same Site Collection maintaining their properties, permissions and content.

Clearly, the new address assigned to the site to be moved must be valid up to the name of the site once moved. For example, if I want to move the site "http://servername/daspostare" at: "http://servername/sito/peppe/test" sites "http://server/site" and "http : / / server / website / peppe "must exist! The same technique can be used by command line by using the STSADM utility like this:

Code:
  stsadm-o renameweb http://servername/daSpostare-url-newname Peppe
What moves the site to "http://servername/Peppe.
Reply With Quote
Reply

  TechArena Community > Software > Windows Software
Tags: , , , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Error: "The crawler could not communicate with the server""
Thread Thread Starter Forum Replies Last Post
msiexec.exe Application Error "The instruction at "0x00f33fe8" referenced memory at "0x00f33fe8". The memory could not be "written"." haritable Office Setup 3 10-01-2014 10:40 AM
Domain Controller "status"on new W2K8 server is "not available" Susan Bradley Active Directory 2 13-12-2011 03:03 PM
DNS Server Error: "Windows can't communicate with the device or resource" Delightful. Operating Systems 3 20-01-2011 07:51 PM
"Cannot communicate with Primary DNS Server" in Wireless Network Kyle1472 Networking & Security 5 15-05-2009 06:56 AM
"error" refefrenced memory at "0x00000001"; instructions "0x77e76f tynana Windows XP Support 1 11-08-2008 03:22 AM


All times are GMT +5.5. The time now is 04:18 AM.