This item could not be crawled because the crawler could not connect to the repository

This item could not be crawled because the crawler could not connect to the repository

                              

After I configured the Search service application and creation of content source, when I do a full crawl. I see the error below.

Issue: This item could not be crawled because the crawler could not connect to the repository.(searched=D0824DCB-4460-4D46-ABDC-85631CC07809)

Description: The issue could be of many reasons, I explained in detailed in other articles. The below could be one of the main reason.

Solution: Creation of Host Headers: If you’re using a multi server farm, having the below servers in farm.

1.   Server A  - Application server

2.   Server B – WFE

3.   Server C- Crawl server

We need to create the Host headers in All the WFE, Crawl servers to crawl the Content. Go to below path and create the headers. Refer below Article

http://expertsharepoint.blogspot.de/2013/10/path-for-host-file.html

 

In the Headers,

1.   For WFE servers- Need to put the Server IP of the local server

2.   For Crawl Server- Need to put the Server IP of the WFE server

If you have multiple WFE, Crawl servers. You need to choose one of WFE server IP and put the same IP in all WFE,crawl servers also.

Once Entry of host headers done, Crawl the content again and check for the results.

Check the Search under post categories, You definitely find the solution for your search issues.

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

Could not load file or assembly 'RSSharePointSoapProxy

Could not load file or assembly 'RSSharePointSoapProxy

                       

Initially, when I start the Central administration page, I welcomed with the error” the page can’t found”. After I enabled the Call stack and custom errors mode to see the Exact error. The error should be below.

Issue: Could not load file or assembly 'RSSharePointSoapProxy, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'RSSharePointSoapProxy, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Cause: The issue happens because of missing or corrupted RSSharePointSoapProxy dll due to un-installation of Reporting Services Add-In.

Solution: To get resolve the issue, we need to re-install the missing RSS files. 

Download the Microsoft® SQL Server® 2008 R2 Reporting Services Add-in and install in the server.

Link: http://www.microsoft.com/en-us/download/confirmation.aspx?id=622

Note:No need to reboot server or Restart of any service after installation of RSS Add on.

 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

SharePoint Farm ID

SharePoint Farm ID

This is every time SharePoint administrators need to check when they need to apply License to farm. In this article I am giving the steps How to check that.

Step1:we can check the Farm ID by using the below Power shell commands.

1.   Go to->SharePoint management shell

2.   Run                     $SPFarm = Get-spfarm

$SPFarm.ID

Step2:  Farm ID could be also found in Configuration database by running the following SQL query:

SELECT * From Objects where ClassId = ’674DA553-EA77-44A3-B9F8-3F70D786DE6A’

The '674DA553-EA77-44A3-B9F8-3F70D786DE6A' GUID is always a ClassID for Farm object 

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!

How to Migrate SharePoint content databases

How to Migrate SharePoint content databases

This is the task that every SharePoint administrator that should perform on regular. In this article I am providing the detailed steps how to do that.

Steps:

1.    Take backup of the DB which the site is using from SQL server management studio.

2.    Now go to Central Admin Website -> Application Management ->SharePoint Web Application Management -> Content Databases.

3.    Select the appropriate web application. It will display the content DB(s) used by that application.

4.    Now click on the content DB which opens Manage Content Database Settings page.

5.    Note down all the details in this page, since we require this later.

6.    Select Remove content Database & click OK & again OK.

7.    Now we have to detach our database. To do so go to SQL Management studio & right click on the database and select Take Offline. Once the process is done again right click & select Detach.

8.    Now go to “drive name:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data” and files where the DB is already located.

9.    Copy the mdf & ldf file and place it in a new drive in same location “drive name:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data”

10. Now go to SQL Management studio right click on the “Databases” in object explorer and click Attach.

11. Click on Add, browse to the mdf file you copied & click OK.

12. Now do follow step 2 & 3. In this case we will not see any content DB’s associated with the application.

13. Click on Attach Content Database & fill in the details which we got in step 5.

14. Note the DB name should be same as the previous one we detached.

15. That’s all & your DB is migrated.

  

Please Comment if you need Any Help.Your Feed back is always Welcome.I Am Happy to Help !!!!!