org.apache.axis.ConfigurationException

No service named ListsSoap is available

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web10

  • via Unknown by Karl Wright,
  • via Unknown by Karl Wright,
  • via Unknown by Karl Wright,
  • Stack trace

    • org.apache.axis.ConfigurationException: No service named ListsSoap is available at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper$ResourceProvider.getService(SPSProxyHelper.java:2208) at org.apache.axis.AxisEngine.getService(AxisEngine.java:311) at org.apache.axis.MessageContext.setTargetService(MessageContext.java:756) at org.apache.axis.client.Call.invoke(Call.java:2690) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812) at com.microsoft.schemas.sharepoint.soap.ListsSoapStub.getListCollection(ListsSoapStub.java:1807) at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getDocLibID(SPSProxyHelper.java:699) at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:903) at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423) at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:561) at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper$ResourceProvider.getService(SPSProxyHelper.java:2208) at org.apache.axis.AxisEngine.getService(AxisEngine.java:311) at org.apache.axis.MessageContext.setTargetService(MessageContext.java:756) at org.apache.axis.client.Call.invoke(Call.java:2690) at org.apache.axis.client.Call.invoke(Call.java:2443) at org.apache.axis.client.Call.invoke(Call.java:2366) at org.apache.axis.client.Call.invoke(Call.java:1812)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.