SharePoint Search Error “Access is Denied”

If you are like me and did a single box farm installation of SharePoint 2010, you might get to an error whenever you have configured your search.

I configured the search to crawl my local SharePoint Sites and when it did a full crawl it gave me the following error:

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.


This error is caused by the local loopback check.

You can disable the loopback check by setting the DisableLoopbackCheckregistry key. To set the DisableLoopbackCheck registry key, follow these steps

Click Start,
click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
Quit Registry Editor, and then restart your computer.
You can now also browse your site on your local server

People search not working in sharepoint 2010

I found the problem and everything is fine now. Since we are running Http://mysite.company.com I had to also crawl sps3://mysite.company.com. Then did a full crawl and worked like a charm. Thanks for all the help though!!

Time to go back to Central Administration, and first look at your Search service application's management page. Click the Content Sources link on the left hand side, and open/edit your Local SharePoint Sites content source. In the Start Addresses section, you will see a box with entries similar to those below:

Notice the sps3: line. This is the protocol SharePoint uses to read profiles. (Note: It isn't a "protocol", per se. It just instructs SharePoint to call a specific web service hosted at that address.) If you ran the wizard to configure your service applications, it will be pointing at the original web application created by it. You'll need to change it to reflect your new profile web application, then save the changes to your content source definition. Also, if you deleted the original wizard-created web application (or aborted its creation), you'll need to delete the regular http: line referencing it.

Property doesn't exist or is used in a manner inconsistent with schema settings in sharepoint 2010

While performing people search in SharePoint 2010 we encounter following error

Property doesn't exist or is used in a manner inconsistent with schema settings

Resolution:
-----------------

1. Browse the Search Center Site and perform people search which should take us to peopleresults.aspx page
2. Click on Site Actions à Edit Page
3. Edit People Search Core Web part
4. Expand Display properties and check the box against Use Local Virtualization
5. Click on Save and Close on the Ribbon

Try to perform people search again and you should get results back.

webparts that have title issue after Migrating to 2010

If pages is checked out before migration, the webparts on that pages will migrate without titles.

Solution: Do the check in the home pages before/after migration.

Try to find a checked out pages with sql query to find in teh content DB.

Attachment not working for Edit Custom List form

Actually this is possible, but there is a procedure to following to make it
work. I had the same issue (working through it right now with MS support).
Here is a summary of the procedure...

Your Sharepoint environment must be at SP2 (actually infrasture update after SP1
is all you need, but SP2 is a better plan IMO), also you must upgrade to
Sharepoint Designer SP2.

In Designer open the NewForm.aspx of the list. Next, right-click on the
ListFormWebPart and select Web Part Properties. Select to Hide and Close the
web part.Under the closed ListFormWebPart, create some space and add a custom List Form.
Make your customizations to the Custom list Form.

Apparently the DataFormWebPart, which is the "Custom List Form" does not add
everything to the page to support attachments. But by closing and hiding the
ListFormWebPart, whatever scripting that is needed by the attachment field is
added to the page and is available to the Custom List Form.

I have not found a good tutorial about this on the web, maybe someone can put
that together...