If this is SharePoint 2010, you need to select SharePoint 4.0 (2010)
in the pulldown. It looks like you have not done this, since your
seem to be trying to use the SharePoint dspsts service, which does not
work on SharePoint 2010.
I don't know if this is the cause of your Solr problem, but it would
certainly prevent progress on a SharePoint crawl.
Thanks,
Karl
On Tue, Oct 16, 2012 at 2:31 AM, Johan Persson <perzzon.jo...@gmail.com> wrote:
> Didn't get anything into solr. Also the job seem to end up in some
> kind of gridlock with solr. (Never terminating until the solr-process
> is )
>
> Read the Manifold log and found this at the bottom.
> Just thought that the reason for the strange behaviour was that a DTD
> or similar was not obtained.
>
> "DEBUG 2012-10-15 09:23:50,531 (Worker thread '1') - Mapping Exception
> to AxisFault
> AxisFault
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client.Dsp.Syntax
> faultSubcode:
> faultString: Request is empty.
> faultActor:
> faultNode:
> faultDetail:
> {http://xml.apache.org/axis/}stackTrace:Request is empty.
> ...
> ...
>
> WARN 2012-10-15 09:23:50,551 (Worker thread '1') - Service
> interruption reported for job 1350317841332 connection 'Sharepoint':
> Remote procedure exception: Request is empty.
> DEBUG 2012-10-15 09:23:58,499 (Idle cleanup thread) - Checking for
> connections, idleTimeout: 1350318178499
> "
