Skip to main content

SharePoint 2010 Search Issue - FQDN Crawl

I have recently set up a standalone SharePoint 2010 environment.

The Web application was created with host header and the site collection is accessible from the client machines, but not internally. That was because of using FQDN to access the Web site.

The error when I tried to access site internally was similar to the one described here:

You receive error 401.1 when you browse a Web site that uses Integrated Authentication and is hosted on IIS 5.1 or a later version

And the search returned the following error in the Event Log:

"The start address  cannot be crawled.

Context: Application 'Search_Service_Application', Catalog 'Portal_Content'

Details: This item could not be crawled because the crawler could not connect to the repository."

One of the suggestions was to disable the loopback check, but that would compromise the Web server.

So what I have done was:

1. Added a binding to my IIS Web site for a different port. Let's say my Web server name is win-v7mez4966tk and the port number is 10001:



2. Restarted Web site

3. Added Alternate Access Mapping to the Web application:



4. Replaced http://sharepoint.domain.com with http://win-v7mez4966tk:10001 for Content Source settings:



5. Added Server Name Mappings to replace http://win-v7mez4966tk:10001 with http://sharepoint.domain.com for search results:







6. ???!!????

7. ENJOY :) Now I can browse my Web site internally using the custom binding and my search results are available for users.

Stay tuned for more articles from Wylde Solutions

If you need help configuring search in your Intranet using SharePoint 2007 or 2010 contact Wylde Solutions now.
Labels:

Comments

  1. ProximusDecember 22, 2011 at 11:33 PM

    Slava, many thanks! You save my friday:)) Excellent solution!

    ReplyDelete
  2. WillWDecember 23, 2011 at 1:17 AM

    No problem Proximus Mania. I am glad it helped. :)

    ReplyDelete
  3. Mikes SharePointFebruary 1, 2012 at 7:12 AM

    You are the man! This saved me so much time yesterday.
    Now I have another tool in my toolbox...

    ReplyDelete
  4. WillWFebruary 1, 2012 at 2:16 PM

    Good to hear Mikes SharePoint :) Thanks for kind words

    ReplyDelete

Post a Comment

Popular posts from this blog

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...
37 comments
Read more

Document Sets - SharePoint 2010 - Part 1

Hi again, in this post I am going to demonstrate how set up and start using Document Sets in SharePoint 2010. In Beta version there was a little problem when working with Document Sets. You could see the discussion around it here: Document Set content type issue . Now it is fixed and I will show you how to set up Document Sets properly to also use Keywords. 1. Activate two site collection features - Document Sets and Document ID Service: 2. Select a document library settings where you want to implement Document Sets. In my case it is Shared Documents. When you have selected the settings go to Advanced settings and then allow content types management: 3. Add an existing content type called Document Set: 4. Now I want to create a new Document Set. I have a sales opportunity and I have two documents related to this sales opportunity. So first I select New Document -> Document Set command, then provide name and description and there it is: 5. To check if our Document ID...
15 comments
Read more

Version control in Office 365

When working with documents in SharePoint or Office 365, quite often files are named like "Project-Budget-Report-v1.55", "Project-Budget-Report-v1.56", "Project-Budget-Report-v2.0" etc. and stored in the same folder or library. This is to achieve version control from the user perspective. This is not a good idea for the following reasons: Storing redundant information Confusion which version to use when Browsing though many documents to see what information/metadata changed if required Version numbering should be automated, no time spent by the document author There is a better way to manage versions of documents and to use tools already available to us in Office 365. File name should not contain the version number in it. Every time you upload a document with the same name the SharePoint will increment the version number for you automatically in the current set up of our Office 365 site we use for customer documentation. Then to manage the...
Post a Comment
Read more