-Re: Sharepoint connector - authentication failure
Karl Wright 2012-08-22, 17:34
Which version of ManifoldCF are you using? Did you select "SharePoint
2.0" from the pulldown? You will need to do this if you do not have
the SharePoint plugin installed.
For the record, in order to be able to crawl SharePoint 2010, you MUST
be using trunk (not ManifoldCF 0.6), and you MUST select "SharePoint
4.0 (2010)" from the pulldown. That will also mean you need to build
and deploy the SharePoint 2010 plug-in on the SharePoint server for
anything to work at all with SharePoint 2010. FWIW, all of this will
be released in about a month when MCF 0.7 goes out the door.
In the interim, you can check to see whether you have true connection
problems by doing the following:
- Select SharePoint 2.0 from the pulldown
- Save the connection
- If you still get the error, then we escalate to the next level of
debugging, which will include some or all of the following:
(1) See if you can get to the web services from IE. For example, if
the site's url is http://xxx.yyy.com, then try to get to
http://xxx.yyy.com/_vti_bin/Lists.asmx. If that fails, look into your
(2) Turn on "wire debugging", as described in the FAQ, and view your
connection again; it may give additional error details that could be
On Wed, Aug 22, 2012 at 1:22 PM, Michael Wilken <[EMAIL PROTECTED]> wrote:
> I'm running into authentication errors when trying to use ManifoldCF
> trunk against a Sharepoint2010 site.
> After creating a repository connection, I get the following message in
> 'Connection Status':
> Crawl user did not authenticate properly, or has insufficient
> permissions to access http://tunedin.disney.com: (401)Unauthorized
> The SP site is using NTLM for authentication. I've verified that the
> login info is correct: I can access the SP site via a web browser
> using the credentials, and can make SOAP calls with the credentials
> using soapUI.
> I have not installed the MCPermission service, as we don't have to
> worry about permissions at this time. Looking at the code, I'd expect
> to get a different error message if this was causing the problem.
> Any suggestions for further debugging to see what's going wrong?