“No valid proxy can be found” when publishing content type in SharePoint 2010

I found a number of posts with possible fixes for this problem, many of them relating to the Content Type hub URL in the Managed Metadata Service    e.g.

http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/d9efe46c-7d55-4f51-9e09-c41ff4d40bda

http://charliedigital.com/2010/01/06/sharepoint-2010-content-type-publishing-setup/

However, I received this error and the Content Type Hub url in the Managed Metadata Service appeared to be fine. It turned out that a new host header for the content type hub site had been created in IIS and an alternate access mapping added in SharePoint. If I accessed the content type hub site using the original host header (this was the one specified as the Content Type Hub in the managed Metadata Service) and tried to publish a content type everything worked fine. But doing the same thing using the newer host header resulted in the “No valid proxy can be found” message.

So if you get the”No valid proxy can be found” message and the Content Type Hub url in the Managed Metadata Service looks OK, take a look at your host headers in IIS and alternate access mappings in SharePoint.

Ian Docking – Senior Technical Consultant

LdapMembershipProvider not available in SharePoint 2010 Foundation

Despite there being a number of TechNet articles covering how to configure forms-based authentication using the LdapMembershipProvider for a claims-based web application in SharePoint Foundation 2010, it turns out that the LDAP provider isn’t part of Foundation. The only way round it (and it’s not really a way round it as such) is to right your own LDAP provider.

If you closely follow all the config instructions on TechNet (e.g. http://technet.microsoft.com/en-us/library/ee806882.aspx) you’ll still end up with errors in the event log like this…..

Event id: 1310

Exception information:

Exception type: ConfigurationErrorsException

Exception message: Could not load type ‘Microsoft.Office.Server.Security.LdapRoleProvider’ from assembly ‘Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’. (C:\inetpub\wwwroot\wss\VirtualDirectories\…………..\web.config line 334)

Microsoft tell me that a documentation bug has been raised on the TechNet site.

Ian Docking – Senior Technical Consultant

Access denied, HTTP 401 error crawling a SharePoint site on another farm

I had two SharePoint 2010 farms (both on the same domain), one running Enterprise Edition and the other SharePoint Foundation. When trying to crawl a site on the Foundation farm from the Enterprise farm all I got was a single error in the crawl log along the lines of ‘Access denied’ and ‘HTTP 401 Unauthorized’.

I confirmed that the content access account had all the rights it needed to crawl the site, so that wasn’t the problem.

It turned out to be related to the entry for the site’s host header in the hosts file on the Foundation server. It had been added using the local host IP of 127.0.0.1.   Changing it to use the actual IP address of the server sorted things out and the Enterprise server was able to crawl the site on the Foundation server successfully.

Ian Docking – Senior Technical Consultant