Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 39318DD5D for ; Tue, 6 Nov 2012 20:59:25 +0000 (UTC) Received: (qmail 38414 invoked by uid 500); 6 Nov 2012 20:59:25 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 38374 invoked by uid 500); 6 Nov 2012 20:59:25 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 38365 invoked by uid 99); 6 Nov 2012 20:59:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 20:59:25 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daddywri@gmail.com designates 209.85.210.178 as permitted sender) Received: from [209.85.210.178] (HELO mail-ia0-f178.google.com) (209.85.210.178) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Nov 2012 20:59:21 +0000 Received: by mail-ia0-f178.google.com with SMTP id y26so579807iab.9 for ; Tue, 06 Nov 2012 12:59:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Y3CF9Ob+998M4uC3KBsyGrQfBrmrc6uZcp7NNKNn35Y=; b=FCxa/3bLirHBWFprXwMbmn3HHT3fTwW0up3C01BgddZVmcQo0hSSEeUsekfikA263X vEiv1Lt2eI/i9FbEag2jLUeM5qbUmVk7E4/AAfNH6ghzLeNh8gmGtWXjaGqRSYD0sqty g/3pcmuDov2IaGW63ddmSTli+DHZOxMlHgq9TPXhgCUCr4egFugeV8qgALv78wgfyS3/ B0qpkneNHdgep+lg9nJ28gpuGqZT41tv06Ctyog7Fzuv0QGBzwPHic+5Kir3c3Do17xH 4GPZ9hmubp75iBvI2vhHS3W5gv2qZgSEsh18DZLfniJzVou8GHBUHQETWifWgGBwoYZW bZPw== MIME-Version: 1.0 Received: by 10.50.219.170 with SMTP id pp10mr2461840igc.53.1352235540582; Tue, 06 Nov 2012 12:59:00 -0800 (PST) Received: by 10.42.33.10 with HTTP; Tue, 6 Nov 2012 12:59:00 -0800 (PST) In-Reply-To: References: Date: Tue, 6 Nov 2012 15:59:00 -0500 Message-ID: Subject: Re: Cannot connect to SharePoint 2010 instance From: Karl Wright To: user@manifoldcf.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org If you want, we can create a ticket to cover SharePoint 2013 work. If you want to attempt a sanity check, if you email me (personally, to daddywri@gmail.com) the Microsoft.SharePoint.dll I can set up a ManifoldCF-Sharepoint-2013 plugin. If I can build that, then the next step would be just trying it all out and seeing where it fails. Karl On Tue, Nov 6, 2012 at 3:49 PM, Iannetti, Robert wrote: > Karl, > > That sounds reasonable. I am having my SP Admin set up the NTML SharePoin= t instance described below I will let you know how it works. > > BTW SP 2013 RTM has been released so we can cross #1 off the list :) > > Thanks > Bob > > -----Original Message----- > From: Karl Wright [mailto:daddywri@gmail.com] > Sent: Tuesday, November 06, 2012 3:47 PM > To: user@manifoldcf.apache.org > Subject: Re: Cannot connect to SharePoint 2010 instance > > Hi Bob, > > That depends very strongly on whether SharePoint 2013 continues the Micro= soft tradition of breaking web services that used to work. :-) > > Seriously, we need three things to develop a SharePoint 2013 solution: > (1) A stable release (a beta is not sufficient because Microsoft is famou= s for changing things in a major way between beta and release); > (2) a benevolent client with sufficient patience to try things out that w= e develop in their environment, and (3) enough time so that we're not on th= e bleeding edge and that other people have run into most of the sticky prob= lems first. We're volunteers here and we all have day jobs, so we mostly c= an't afford to be pounding away at brick walls on our own. > > It could be the case that everything just works, in which case the develo= pment is trivial. We'll have to see. > > Karl > > On Tue, Nov 6, 2012 at 3:37 PM, Iannetti, Robert wrote: >> Karl, >> >> On another topic is there a roadmap for supporting SharePoint 2013 ? >> We are in the process of migrating and were wondering when your Manifold= CF product would be available to support it. >> >> Thanks >> Bob >> >> >> -----Original Message----- >> From: Karl Wright [mailto:daddywri@gmail.com] >> Sent: Tuesday, November 06, 2012 3:34 PM >> To: user@manifoldcf.apache.org >> Subject: Re: Cannot connect to SharePoint 2010 instance >> >> Hi Bob, >> >> The only products I know have a similar limitations. The only one I kno= w is the SharePoint google appliance connector, which when I looked last ha= d exactly the same restriction. It also has other limitations, some severe= , such as limiting the number of documents you can crawl to no more than 50= 00 per library. >> >> We are willing to do a reasonable amount of work to upgrade ManifoldCF >> to be able to support Kerberos. Here's a link which describes the >> situation: >> >> http://old.nabble.com/Support-for-Kerberos-SPNEGO-td14564857.html >> >> We currently use a significantly-patched version of 3.1, which supplied = the NTLM implementation for 4.0 that is currently in use. >> Our issue is similar to the commons-httpclient team's, which is we have = no good way of testing all of this, and none of us are security protocol ex= perts. If you have (or know somebody with) such expertise, who would be wi= lling/able to donate their time, this problem could be tackled I think with= out too much pain. So at least httpclient, given the right tickets, would = be able to connect. >> >> The other issue with Kerberos auth is that I believe it will require a s= ignificant amount of work to allow anything using it to obtain the tickets = from the AD domain controller. This would obviously require UI work for al= l connectors that would support Kerberos. But that is something I am willi= ng to attempt if everything else is in place. >> >> Karl >> >> >> On Tue, Nov 6, 2012 at 3:11 PM, Iannetti, Robert wrote: >>> Karl, >>> >>> If this is not possible can you recommend any other products to crawl S= harePoint content and index it in Solr? >>> >>> Thanks >>> Bob >>> >>> >>> -----Original Message----- >>> From: Karl Wright [mailto:daddywri@gmail.com] >>> Sent: Tuesday, November 06, 2012 3:10 PM >>> To: user@manifoldcf.apache.org >>> Subject: Re: Cannot connect to SharePoint 2010 instance >>> >>> No, Kerberos is not supported. This is a limitation of the Apache comm= ons-httpclient library that we use for communicating with SharePoint. >>> >>> It is possible to set up IIS to serve a different port with different a= uthentication that goes to the same SharePoint instance but is NTLM protect= ed, not Kerberos protected. Perhaps you can do this and limit access to th= at port to only the ManifoldCF machine. >>> >>> Karl >>> >>> On Tue, Nov 6, 2012 at 3:03 PM, Iannetti, Robert wrote: >>>> Karl, >>>> >>>> Our SharePoint sites use Kerberos authentication is this supported in = ManifoldCF? >>>> >>>> Thanks >>>> Bob >>>> >>>> >>>> -----Original Message----- >>>> From: Karl Wright [mailto:daddywri@gmail.com] >>>> Sent: Tuesday, November 06, 2012 2:50 PM >>>> To: user@manifoldcf.apache.org >>>> Subject: Re: Cannot connect to SharePoint 2010 instance >>>> >>>> Yes, this can be somewhat tricky. There are a lot of potential config= urations that could affect this. >>>> >>>> First, you want to verify that your IIS is using NTLM authentication, = and that all the web services directories are "executable". This is critic= al. >>>> >>>> Second, the credentials, in the form of domain\user, may be sensitive = to whether you use a fully-qualified domain name or a shortcut domain name,= e.g. mydomain.novartis.com or just mydomain. I suggest you try some combi= nations. The other thing you may want to check is whether the machine you = are running ManifoldCF on is known by your domain controller; you may not b= e able to authenticate if it is not. >>>> >>>> If this doesn't help, and you want to eliminate ManifoldCF's NTLM impl= ementation from the list of possibilities, I suggest downloading the "curl"= utility, and trying to fetch a web service listing or wsdl using it (speci= fying NTLM of course as the authentication method). If that also doesn't w= ork, it's a server-side configuration problem of some kind. >>>> >>>> You can also refer to the server-side IIS logs for some additional inf= o. But I've found these are not very helpful for authentication issues. >>>> >>>> Let me know if you are still stuck after this; there are other diagnos= tics available but they start to get ugly. >>>> >>>> Kral >>>> >>>> On Tue, Nov 6, 2012 at 2:35 PM, Iannetti, Robert wrote: >>>>> Karl, >>>>> >>>>> I turned on the additional debugging and was able to resolve the 404 = issue. >>>>> >>>>> Now I am getting: >>>>> Crawl user did not authenticate properly, or has insufficient >>>>> permissions to access http://xxxx.xxx.xxx: (401)Unauthorized >>>>> >>>>> I can log into the SharePoint site from the browser using the same cr= edentials. >>>>> >>>>> >>>>> Any Thoughts? >>>>> >>>>> Thanks >>>>> Bob >>>>> >>>>> -----Original Message----- >>>>> From: Karl Wright [mailto:daddywri@gmail.com] >>>>> Sent: Tuesday, November 06, 2012 10:05 AM >>>>> To: user@manifoldcf.apache.org >>>>> Subject: Re: Cannot connect to SharePoint 2010 instance >>>>> >>>>> Well, you can turn on httpclient wire debugging, as I believe is desc= ribed in the article URL I sent you before, and then you can see precisely = what URL the connector is trying to reach when it accesses the MCPermission= s service. >>>>> >>>>> There's no magic here. If the connector gets a 404 error back from I= IS, either its URL is wrong, or IIS has decided it's not going to serve tha= t page to the client. >>>>> >>>>> Karl >>>>> >>>>> >>>>> On Tue, Nov 6, 2012 at 8:58 AM, Iannetti, Robert wrote: >>>>>> Yes, The URL and what I enter in the ManifoldCF interface are a matc= h. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Karl Wright [mailto:daddywri@gmail.com] >>>>>> Sent: Tuesday, November 06, 2012 8:52 AM >>>>>> To: user@manifoldcf.apache.org >>>>>> Subject: Re: Cannot connect to SharePoint 2010 instance >>>>>> >>>>>> I've seen situations where a SharePoint site is configured to perfor= m a redirection, and this is messing things up internally. Does the your c= onnection server name etc. match precisely the URL you see when you are in = the SharePoint user interface? >>>>>> >>>>>> Karl >>>>>> >>>>>> On Tue, Nov 6, 2012 at 8:47 AM, Iannetti, Robert wrote: >>>>>>> Karl, >>>>>>> >>>>>>> After further review it appears the MCpermissions.asmx was installe= d globally in SharePoint. I am able to access it from within my SharePoint = site as well as all other valid SharePoint sub-sites. >>>>>>> So this connection http:////_vti_bin works with a= ny valid site in including the previously mentioned _admin site. >>>>>>> >>>>>>> That said do you have any thoughts on why I would be getting the 40= 4 error? >>>>>>> >>>>>>> Thanks >>>>>>> Bob >>>>>>> >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Karl Wright [mailto:daddywri@gmail.com] >>>>>>> Sent: Monday, November 05, 2012 2:45 PM >>>>>>> To: user@manifoldcf.apache.org >>>>>>> Subject: Re: Cannot connect to SharePoint 2010 instance >>>>>>> >>>>>>> The 404 error indicates that your MCPermissions service is not prop= erly deployed. The "_admin" in your path is a clue that something might no= t be right. The place you want to see the MCPermissions.asmx is in the fol= lowing location: >>>>>>> >>>>>>> http[s]:////_vti_bin >>>>>>> >>>>>>> ... where the is your server name, and the is y= our site path. The best way to get this is to enter the SharePoint UI (NOT= the admin UI, but the SharePoint end-user UI), and log into the root site.= Then make note of the URL in your browser. >>>>>>> >>>>>>> If the MCPermissions.asmx service appears under that URL, look at y= our IIS settings and make sure that the MCPermissions.asmx service can be e= xecuted. >>>>>>> >>>>>>> Also, this may be of some help: >>>>>>> https://cwiki.apache.org/confluence/display/CONNECTORS/Debugging+ >>>>>>> C >>>>>>> o >>>>>>> n >>>>>>> n >>>>>>> e >>>>>>> ctions >>>>>>> >>>>>>> The end user documentation is also extremely helpful in describing = how to properly set up connections. >>>>>>> >>>>>>> You can uninstall the MCPermissions.asmx service using the .bat fil= es that are included with the plugin. When you re-install, please make sur= e that you are logged in as a user with full admin privileges, or the servi= ce will not work properly. >>>>>>> >>>>>>> Thanks, >>>>>>> Karl >>>>>>> >>>>>>> On Mon, Nov 5, 2012 at 2:33 PM, Iannetti, Robert wrote: >>>>>>>> Hello, >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I have installed apache-manifoldcf-1.0.1 on my Linux server and >>>>>>>> apache-manifoldcf-sharepoint-2010-plugin-0.1-bin on my >>>>>>>> SharePoint >>>>>>>> 2010 server. >>>>>>>> >>>>>>>> On my SharePoint server I can see the Permissions Page when I >>>>>>>> enter http://xxxxx:xxxxx/_admin/_vti_bin/MCPermissions.asmx in my = browser. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> When I try to make a "SharePoint Services 4.0 (2010)" connection >>>>>>>> to my SharePoint 2010 server in the ManifoldCF interface I get thi= s error. >>>>>>>> >>>>>>>> Got an unknown remote exception accessing site - axis fault =3D >>>>>>>> Client, detail =3D The request failed with HTTP status 404: Not Fo= und. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> I can connect using "SharePoint Services 2.0 (2003)" but when I >>>>>>>> try a crawl it does not work properly and aborts. >>>>>>>> >>>>>>>> The "SharePoint Services 3.0 (2007)" connection fails the same >>>>>>>> as the above >>>>>>>> 2010 connection. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Can you please give some direction on how best to resolve this iss= ue. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Thanks >>>>>>>> >>>>>>>> Bob >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Robert P. Iannetti >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Application Architect >>>>>>>> >>>>>>>> Novartis Institute for BioMedical Research >>>>>>>> >>>>>>>> 186 Massachusetts Avenue >>>>>>>> >>>>>>>> Cambridge, MA 02139 >>>>>>>> >>>>>>>> Phone: +1 (617) 871-5414 >>>>>>>> >>>>>>>> robert.iannetti@novartis.com >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>