Hi Mark, Can you send the complete exception being thrown, and a screen shot of the view page for your connection, as well as the view page for your job?
404 errors are never good; something is clearly wrong when the connector can't find the pages that should be there. Karl Sent from my Windows Phone ------------------------------ From: Mark Libucha Sent: 10/11/2013 6:26 PM To: [email protected] Subject: Re: Crawling SharePoint Lists trunk is no better. When I turn on debug logging, I see the SharePoint processDocument() calls all end in exceptions that look something like this: org.apache.axis.ConfigurationException: No service named http://schemas.microsoft.com/sharepoint/soap/directory/GetUserCollectionFromGroupis available Those URLs 404, but does that matter? Any other suggestions? Thanks, Mark On Thu, Oct 10, 2013 at 1:22 PM, Mark Libucha <[email protected]> wrote: > Thanks, guys. I'll give these both a try and let you know what I discover. > Appreciate the help. > > > On Thu, Oct 10, 2013 at 10:04 AM, Karl Wright <[email protected]> wrote: > >> Hi Mark, >> >> >> >> There are some issues with list crawling that we found in 1.3. I >> suggest that you try trunk; it will likely work better for you. >> >> >> >> Karl >> >> >> >> >> On Thu, Oct 10, 2013 at 12:04 PM, Mark Libucha <[email protected]>wrote: >> >>> I have successfully crawled documents with my SharePoint >>> RepositoryConnector (MCF 1.3), so I know that things are set up correctly. >>> >>> But I can't crawl a list. >>> >>> I'm using a Filesystem output connector, and the job appears to run >>> successfully (2 of 2 documents), but I see nothing in output directory when >>> the job is finished. In fact, the output directory is not even created. >>> >>> As far as I can determine, I followed the instructions under >>> >>> *Example: How to index SharePoint 2010 Lists >>> >>> * >>> exactly. And I am using SharePoint 2010. >>> >>> My "Greg" list shows up in the MCF UI under Lists, I and choose it. >>> >>> My job looks like this: >>> Path rules: Path match Rule type Action /Greg list include Metadata: >>> Path >>> match Action All metadata? Fields /Greg/* include true >>> >>> Suggestions? >>> >>> Thanks, >>> >>> Mark >>> ------------------------------ >>> >>> ** >>> >> >> >
