manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <daddy...@gmail.com>
Subject Re: Getting a 401 Unauthorized on a SharePoint 2010 crawl request, with MCPermissions.asmx installed
Date Tue, 10 Sep 2013 13:32:25 GMT
Sorry, my fault, the logic for setting one of the flags was incorrect.
I've checked in a fix to the branch.  Please rebuild and try again.

Karl



On Tue, Sep 10, 2013 at 9:26 AM, Dmitry Goldenberg
<dgoldenberg@kmwllc.com>wrote:

> Karl,
>
> I'm now getting the following error (please see below). I'm wondering if
> all these discrepancies are caused by the fact that we're running in Amz or
> is this perhaps something due to a specific build of the SP server and/or
> installation choices?...
>
> This error is after: reinstalling the new MCPermissions, svn update of the
> branch, rebuild, retry. I have modified the repo connection to use the
> newly added Amz dropdown pick; I have not modified the connection or the
> job in any other way.
>
>
>
> DEBUG 2013-09-10 09:20:20,253 (Worker thread '2') - SharePoint: Got an
> unknown remote exception getting child documents for site /ABCD guid
> {2DE19696-36D8-4519-9DF8-942E58BA0D5B} - axis fault = Client.Dsp.Syntax,
> detail = Request is empty. - retrying
> 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.
>
>  at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>  at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>  at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>  at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
>  at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
>  at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
>  at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>  at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> Source)
>  at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>  at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>  at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>  at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>  at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>  at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>  at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>  at org.apache.axis.client.Call.invoke(Call.java:2767)
>  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.dsp.StsAdapterSoapStub.query(StsAdapterSoapStub.java:317)
>  at
> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:546)
>  at
> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1414)
>
>  at
> org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
>  at
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
>  {http://xml.apache.org/axis/}hostname:DG-PC
> Request is empty.
>
>  at
> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>  at
> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>  at
> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>  at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
>  at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
> Source)
>  at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
> Source)
>  at
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
> Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>  at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> Source)
>  at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>  at
> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>  at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>  at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>  at
> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>  at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>  at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>  at org.apache.axis.client.Call.invoke(Call.java:2767)
>  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.dsp.StsAdapterSoapStub.query(StsAdapterSoapStub.java:317)
>  at
> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:546)
>  at
> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1414)
>
>  at
> org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
>  at
> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
>  WARN 2013-09-10 09:20:20,285 (Worker thread '2') - Service interruption
> reported for job 1378756749019 connection 'ABCD SP Connection': Remote
> procedure exception: Request is empty.
>
>
> On Tue, Sep 10, 2013 at 6:54 AM, Karl Wright <daddywri@gmail.com> wrote:
>
>> I've now updated the branch to allow you to select the Amazon version of
>> SharePoint 2010 from the pulldown.  If you svn update, you will need to
>> change your selection in the connection to this choice in order for the
>> change to continue to work.
>>
>> Thanks,
>> Karl
>>
>>
>>
>> On Mon, Sep 9, 2013 at 5:22 PM, Karl Wright <daddywri@gmail.com> wrote:
>>
>>> Hi Dmitry,
>>>
>>> Please download and install the wsp file at:
>>>
>>>
>>> http://people.apache.org/~kwright/MetaCarta.SharePoint.MCPermissionsService.wsp
>>>
>>> Once you've done that, check to see if you no longer get errors on the
>>> crawl.
>>>
>>> Thanks,
>>> Karl
>>>
>>>
>>>
>>> On Mon, Sep 9, 2013 at 5:11 PM, Karl Wright <daddywri@gmail.com> wrote:
>>>
>>>> I have a feeling that the way I'm getting the base SharePoint instance
>>>> handle in the plugin for the listing functionality is not coexisting well
>>>> with Amazon.
>>>>
>>>> I will put together a new version of the plugin for you to try; let's
>>>> see if that fixes it.  Stay tuned.
>>>>
>>>> Karl
>>>>
>>>>
>>>>
>>>> On Mon, Sep 9, 2013 at 4:55 PM, Dmitry Goldenberg <
>>>> dgoldenberg@kmwllc.com> wrote:
>>>>
>>>>> Hi Karl,
>>>>>
>>>>> Definitely some progress here.  No more exceptions from SPS proxy
>>>>> helper..
>>>>>
>>>>> It seems that the default for extraction is to include nothing (?)
>>>>>
>>>>> I went ahead and included all libraries and lists for one specific
>>>>> subsite. I also included metadata for all of those libraries and lists. I
>>>>> was not able to check off "include all" so 'all metadata' ended up being
>>>>> false on all rules.
>>>>>
>>>>> A bigger issue is that nothing is getting saved into the output
>>>>> folder. The log contains one error which seems to be halting everything, as
>>>>> below.  I have checked again the access to MCPermissions via the browser
>>>>> and it appears to be fine. The actual SP URL mentioned in the error message
>>>>> is fine too.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>>
>>>>>
>>>>> DEBUG 2013-09-09 16:44:06,250 (Worker thread '23') - SharePoint: Got
>>>>> an unknown remote exception getting child documents for site /ABCD guid
>>>>> {2DE19696-36D8-4519-9DF8-942E58BA0D5B} - axis fault = Client, detail = The
>>>>> Web application at
>>>>> http://*********.amazonaws.com could not be found. Verify that you
>>>>> have typed the URL correctly. If the URL should be serving
>>>>> existing content, the system administrator may need to add a new
>>>>> request URL mapping to the intended application. - retrying
>>>>> AxisFault
>>>>>  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client
>>>>>  faultSubcode:
>>>>>  faultString: The Web application at http://**********.amazonaws.comcould not be found. Verify that you have typed the URL correctly.
>>>>> If the URL should be serving existing content, the system
>>>>> administrator may need to add a new request URL mapping to the intended
>>>>> application.
>>>>>  faultActor: http://**********.
>>>>> amazonaws.com/_vti_bin/MCPermissions.asmx
>>>>>  faultNode:
>>>>>  faultDetail:
>>>>>  {}Error:<ErrorNumber>1010</ErrorNumber><ErrorMessage>The Web
>>>>> application at http://**********.amazonaws.com could not be found.
>>>>>  Verify that you have typed the URL correctly. If the URL should be
>>>>> serving existing content, the system administrator may
>>>>>  need to add a new request URL mapping to the intended
>>>>> application.</ErrorMessage><ErrorSource>Microsoft.SharePoint</ErrorSource>
>>>>> The Web application at http://**********.amazonaws.com could not be
>>>>> found. Verify that you have typed the URL correctly.
>>>>> If the URL should be serving existing content, the system
>>>>> administrator may need to add a new request URL mapping to the intended
>>>>> application.
>>>>>
>>>>>  at
>>>>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>>>>  at
>>>>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>>>>  at
>>>>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>>>>  at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
>>>>> Source)
>>>>>  at
>>>>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
>>>>> Source)
>>>>>  at
>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>>>> Source)
>>>>>  at
>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>>>> Source)
>>>>>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>>>>  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
>>>>>  at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
>>>>>  at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
>>>>>  at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>>>>> Source)
>>>>>  at org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown Source)
>>>>>  at
>>>>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>>>>  at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>>>>>  at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>>>>>  at
>>>>> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>>>>>  at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>>>>>  at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>>>>  at org.apache.axis.client.Call.invoke(Call.java:2767)
>>>>>  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.sharepoint.webpartpages.PermissionsSoapStub.getListItems(PermissionsSoapStub.java:234)
>>>>>  at
>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:621)
>>>>>  at
>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.processDocuments(SharePointRepository.java:1411)
>>>>>  at
>>>>> org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnector.processDocuments(BaseRepositoryConnector.java:423)
>>>>>  at
>>>>> org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerThread.java:559)
>>>>>  WARN 2013-09-09 16:44:06,255 (Worker thread '23') - Service
>>>>> interruption reported for job 1378756749019 connection 'TEST SP Connection':
>>>>>  Remote procedure exception: The Web application at http://**********.
>>>>> amazonaws.com could not be found.
>>>>>  Verify that you have typed the URL correctly. If the URL should be
>>>>> serving existing content, the system administrator may need to
>>>>>  add a new request URL mapping to the intended application.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Sep 9, 2013 at 1:29 PM, Karl Wright <daddywri@gmail.com>wrote:
>>>>>
>>>>>> Hi Dmitry,
>>>>>>
>>>>>> I've created a branch (
>>>>>> https://svn.apache.org/repos/asf/manifoldcf/branches/CONNECTORS-772)
>>>>>> which has the change I believe will work for your instance.  I'd like you
>>>>>> to check this out and build it with ant (using the instructions on the
>>>>>> how-to-build-and-deploy page).  Then see if it works.  Please let me know
>>>>>> either way.
>>>>>>
>>>>>> Should it work, then I think we'll need to research how exactly the
>>>>>> Amazon system was configured that changed the format of the Lists results.
>>>>>>
>>>>>> Karl
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Sep 9, 2013 at 1:19 PM, Dmitry Goldenberg <
>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>
>>>>>>> Thanks, Karl, really appreciate your responsiveness. Please let me
>>>>>>> know if there's anything I can try on my end and/or help you test or
>>>>>>> troubleshoot further.
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Sep 9, 2013 at 1:15 PM, Karl Wright <daddywri@gmail.com>wrote:
>>>>>>>
>>>>>>>> Hi Dmitry,
>>>>>>>>
>>>>>>>> I don't recommend commenting out the substring extractions; they
>>>>>>>> are actually doing things.  This is how ManifoldCF discovers lists in
>>>>>>>> subsites.  The method call you are debugging is doing this in order to
>>>>>>>> display a pulldown which should allow you to select from a list of Lists in
>>>>>>>> the UI that correspond to the subsite you've already selected.
>>>>>>>>
>>>>>>>> The problem is that this code works fine in other installations of
>>>>>>>> SharePoint 2010, but not for your SharePoint instance.  It is not clear
>>>>>>>> what the actual issue is, but I need to compare/contrast with the other
>>>>>>>> implementations in order to find out how the connector can determine which
>>>>>>>> way the path is actually assembled.  I've opened a ticket (CONNECTORS-772)
>>>>>>>> and will very shortly be creating a corresponding branch where we can
>>>>>>>> experiment with the code.
>>>>>>>>
>>>>>>>> Karl
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Sep 9, 2013 at 1:02 PM, Dmitry Goldenberg <
>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>
>>>>>>>>> Karl,
>>>>>>>>>
>>>>>>>>> Abcd = Site1.
>>>>>>>>>
>>>>>>>>> Are you recommending that I just comment out those
>>>>>>>>> checks/substring extractions?  Have considered it but am not sure if that'd
>>>>>>>>> break something down the line in the code.  Let me know, thanks.
>>>>>>>>>
>>>>>>>>> - Dmitry
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Sep 9, 2013 at 1:00 PM, Karl Wright <daddywri@gmail.com>wrote:
>>>>>>>>>
>>>>>>>>>> And, what is "/Abcd" in your example above?
>>>>>>>>>>
>>>>>>>>>> The code thinks it is part of the site path.  Is it a subsite
>>>>>>>>>> name?
>>>>>>>>>>
>>>>>>>>>> If so, the SharePoint build used by Amazon is not including the
>>>>>>>>>> subsite path in the view urls being returned by the Lists service.  If you
>>>>>>>>>> can confirm this picture, I think the right thing to do is create a branch
>>>>>>>>>> which works properly with your Amazon instance, and then we can see what
>>>>>>>>>> the diffs are, and I can have people with non-Amazon instances try out the
>>>>>>>>>> same things with the new code and see what they do in their environments.
>>>>>>>>>>
>>>>>>>>>> Karl
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Sep 9, 2013 at 12:39 PM, Dmitry Goldenberg <
>>>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Karl,
>>>>>>>>>>>
>>>>>>>>>>> The structure of the instance is as follows:
>>>>>>>>>>>
>>>>>>>>>>> root: http://<hostname>/SitePages/Home.aspx
>>>>>>>>>>> 3 subsites: http://<hostname>/Site1/SitePages/Home.aspx, http://<hostname>/Site2/SitePages/Home.aspx,
>>>>>>>>>>> http://<hostname>/Site3/SitePages/Home.aspx
>>>>>>>>>>>
>>>>>>>>>>> The repo connection is configured as follows:
>>>>>>>>>>> * Server SharePoint version: SharePoint Services 4.0 (2010)
>>>>>>>>>>> * Server protocol: http
>>>>>>>>>>> * Server name: <hostname>
>>>>>>>>>>> * Server port: <empty>
>>>>>>>>>>> * Site path: <empty>
>>>>>>>>>>> * Username: <domain-name>\administrator
>>>>>>>>>>> * Password: <password>
>>>>>>>>>>>
>>>>>>>>>>> Connection type is set to SharePoint.  Authority is none
>>>>>>>>>>> (globalAuthority). Didn't set anything into the Throttling tab.
>>>>>>>>>>>
>>>>>>>>>>> - Dmitry
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Mon, Sep 9, 2013 at 12:24 PM, Karl Wright <daddywri@gmail.com
>>>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>>> It looks like, in your case, the code is expecting:
>>>>>>>>>>>>
>>>>>>>>>>>> /Abcd/Lists/Announcements/AllItems.aspx
>>>>>>>>>>>>
>>>>>>>>>>>> ... but you are seeing:
>>>>>>>>>>>>
>>>>>>>>>>>> /Lists/Announcements/AllItems.aspx
>>>>>>>>>>>>
>>>>>>>>>>>> This is definitely different from what we see on other
>>>>>>>>>>>> traditionally-installed SharePoint instances.  This can mean that the
>>>>>>>>>>>> SharePoint connection is misconfigured; path misalignments will generally
>>>>>>>>>>>> occur when you point the SharePoint connection to something other than the
>>>>>>>>>>>> SharePoint site root.
>>>>>>>>>>>>
>>>>>>>>>>>> Can you describe specifically how your SharePoint connection is
>>>>>>>>>>>> configured?  Start by going to the root site and logging in.  What is the
>>>>>>>>>>>> URL you see in the browser?  Feel free to redact the actual system name as
>>>>>>>>>>>> desired.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Mon, Sep 9, 2013 at 11:58 AM, Dmitry Goldenberg <
>>>>>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> Karl,
>>>>>>>>>>>>>
>>>>>>>>>>>>> Some good news and new questions.
>>>>>>>>>>>>>
>>>>>>>>>>>>> I think my 'services not found' issue is resolved AFAIK, I
>>>>>>>>>>>>> just had to update the service port address locations in the WSDL's to
>>>>>>>>>>>>> point to our test server, then rebuild/redeploy. Perhaps it's worth adding
>>>>>>>>>>>>> this to the doc for forgetful people like me :))
>>>>>>>>>>>>>
>>>>>>>>>>>>> I'm also realizing that by default, the connection won't pull
>>>>>>>>>>>>> any data unless at least one rule is added -- is that correct? I had
>>>>>>>>>>>>> assumed it'd pull *all* data by default but it seems that the default is
>>>>>>>>>>>>> not to pull anything unless some rules are in place. (May be a good doc
>>>>>>>>>>>>> addition too :))
>>>>>>>>>>>>>
>>>>>>>>>>>>> The good news is I am in fact getting a 'Connection working'.
>>>>>>>>>>>>>
>>>>>>>>>>>>> However, I've run into another snag, which is that, as I'm
>>>>>>>>>>>>> defining a rule to pull in a specific site, I'm getting the following error
>>>>>>>>>>>>> (stack trace below).
>>>>>>>>>>>>>
>>>>>>>>>>>>> I've debugged it a bit and I have the local variable state as
>>>>>>>>>>>>> follows:
>>>>>>>>>>>>>
>>>>>>>>>>>>> >> decodedServerLocation: []
>>>>>>>>>>>>> >> decodedServerLocation: [/Abcd]
>>>>>>>>>>>>> >> chuckIndex: 5
>>>>>>>>>>>>> >> urlPath: [/Lists/Announcements/AllItems.aspx]
>>>>>>>>>>>>> >> urlPath at chuckIndex: [s/Announcements/AllItems.aspx]
>>>>>>>>>>>>>
>>>>>>>>>>>>> That's what the following modified portion of the getLists
>>>>>>>>>>>>> method emits at runtime before bombing at that last line (below).
>>>>>>>>>>>>>
>>>>>>>>>>>>> Any ideas as to how to fix this cleanly or work around it?
>>>>>>>>>>>>> The code seems to presume a very specific URL structure which the returned
>>>>>>>>>>>>> urlPath's are not adhering to.  Does this have something to do with the
>>>>>>>>>>>>> fact that I have no "Site path" defined in my connection? Our test sites
>>>>>>>>>>>>> are right under the root site, basically just
>>>>>>>>>>>>> http://server/Abcd etc.etc.
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> ====================================================================================
>>>>>>>>>>>>> System.out.println(">> decodedServerLocation: [" +
>>>>>>>>>>>>> decodedServerLocation + "]");
>>>>>>>>>>>>> System.out.println(">> decodedServerLocation: [" +
>>>>>>>>>>>>> parentSiteDecoded + "]");
>>>>>>>>>>>>>
>>>>>>>>>>>>>       int chuckIndex = decodedServerLocation.length() +
>>>>>>>>>>>>> parentSiteDecoded.length();
>>>>>>>>>>>>> System.out.println(">> chuckIndex: " + chuckIndex);
>>>>>>>>>>>>>
>>>>>>>>>>>>>       int i = 0;
>>>>>>>>>>>>>       while (i < nodeList.size())
>>>>>>>>>>>>>       {
>>>>>>>>>>>>>         Object o = nodeList.get( i++ );
>>>>>>>>>>>>>         String baseType = doc.getValue( o, "BaseType");
>>>>>>>>>>>>>         if ( baseType.equals( "0" ) )
>>>>>>>>>>>>>         {
>>>>>>>>>>>>>           // We think it's a list
>>>>>>>>>>>>>           // This is how we display it, so this has the right
>>>>>>>>>>>>> path extension
>>>>>>>>>>>>>           String urlPath = doc.getValue( o, "DefaultViewUrl" );
>>>>>>>>>>>>>           // This is the pretty name
>>>>>>>>>>>>>           String title = doc.getValue( o, "Title" );
>>>>>>>>>>>>> System.out.println(">> urlPath: [" + urlPath + "]");
>>>>>>>>>>>>>
>>>>>>>>>>>>>           // Leave this in for the moment
>>>>>>>>>>>>>           if (Logging.connectors.isDebugEnabled())
>>>>>>>>>>>>>             Logging.connectors.debug("SharePoint: List:
>>>>>>>>>>>>> '"+urlPath+"', '"+title+"'");
>>>>>>>>>>>>>           // If it has no view url, we don't have any idea
>>>>>>>>>>>>> what to do with it
>>>>>>>>>>>>>           if (urlPath != null && urlPath.length() > 0)
>>>>>>>>>>>>>           {
>>>>>>>>>>>>>             if (urlPath.length() < chuckIndex)
>>>>>>>>>>>>>               throw new ManifoldCFException("List view url is
>>>>>>>>>>>>> not in the expected form: '"+urlPath+"'");
>>>>>>>>>>>>>             urlPath = urlPath.substring(chuckIndex);
>>>>>>>>>>>>>
>>>>>>>>>>>>> System.out.println(">> urlPath at chuckIndex: [" + urlPath +
>>>>>>>>>>>>> "]");
>>>>>>>>>>>>>
>>>>>>>>>>>>>             if (!urlPath.startsWith("/"))
>>>>>>>>>>>>>               throw new ManifoldCFException("List view url
>>>>>>>>>>>>> without site is not in the expected form: '"+urlPath+"'");
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> =============================================================================
>>>>>>>>>>>>> List view url without site is not in the expected form:
>>>>>>>>>>>>> 's/Announcements/AllItems.aspx'
>>>>>>>>>>>>> org.apache.manifoldcf.core.interfaces.ManifoldCFException:
>>>>>>>>>>>>> List view url without site is not in the expected form:
>>>>>>>>>>>>> 's/Announcements/AllItems.aspx'
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getLists(SPSProxyHelper.java:2287)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.getListsBySite(SharePointRepository.java:5045)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.outputSpecificationBody(SharePointRepository.java:2861)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.jsp.editjob_jsp._jspService(editjob_jsp.java:2182)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
>>>>>>>>>>>>> at
>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 10:32 AM, Karl Wright <
>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> You might want to look at CONNECTORS-470; the developer in
>>>>>>>>>>>>>> that case had a similar problem.  It appeared initially that he had some of
>>>>>>>>>>>>>> his web services disabled.  You need seven of them to be enabled before the
>>>>>>>>>>>>>> SharePoint repository connector can work:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Permissions.asmx
>>>>>>>>>>>>>> webs.asmx
>>>>>>>>>>>>>> usergroup.asmx
>>>>>>>>>>>>>> versions.asmx
>>>>>>>>>>>>>> DspSts.asmx
>>>>>>>>>>>>>> Lists.asmx
>>>>>>>>>>>>>> MCPermissions.asmx
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> All of these must be in the _vti_bin web path underneath your
>>>>>>>>>>>>>> specified root + virtual directory, and executable by the crawl user.  You
>>>>>>>>>>>>>> should also set up your connection so that the root is NOT a SharePoint
>>>>>>>>>>>>>> subsite, but the actual root site, and the virtual site path is really a
>>>>>>>>>>>>>> virtual site path and not a subsite path.  You exclude or include documents
>>>>>>>>>>>>>> using the rules, not the configuration.  When you view your connection, you
>>>>>>>>>>>>>> should definitely get back "Connection working".  If you continue to get
>>>>>>>>>>>>>> back missing service issues, let me know; you may need to download newer
>>>>>>>>>>>>>> versions of the wsdls from your SharePoint 2010 site and put them in the
>>>>>>>>>>>>>> connectors/sharepoint/wsdl directory and rebuild in order to make things
>>>>>>>>>>>>>> work properly.  (We haven't needed to do that before but it is potentially
>>>>>>>>>>>>>> possible.)
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> In order not to confuse things, I also recommend that before
>>>>>>>>>>>>>> you run your job, you view the corresponding output connection and click
>>>>>>>>>>>>>> the "Reingest all documents" link.  That will force ManifoldCF to forget
>>>>>>>>>>>>>> what it has already processed.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> For further diagnosis, I suggest the following:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> - Restore logging.ini to its initial state, to reduce noise
>>>>>>>>>>>>>> - Turn on connector debugging, by setting property
>>>>>>>>>>>>>> "org.apache.manifoldcf.connectors" to "DEBUG" in properties.xml
>>>>>>>>>>>>>> - Run your job
>>>>>>>>>>>>>> - Look at the log; it should contain notes about all the
>>>>>>>>>>>>>> decisions the connector is making.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 9:45 AM, Dmitry Goldenberg <
>>>>>>>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Karl,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> When I fire off the crawl, it appears to do nothing at all.
>>>>>>>>>>>>>>> The only things I see in the log is messages like the following
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> [2013-09-04 09:42:58,051]-[Idle cleanup thread]-[DEBUG]
>>>>>>>>>>>>>>> org.apache.http.impl.conn.PoolingClientConnectionManager  - Closing
>>>>>>>>>>>>>>> connections idle longer than 60000 MILLISECONDS
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> The job is configured to use my repo connection to the SP
>>>>>>>>>>>>>>> 2010 server, the output is set to a file output.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Any ideas?
>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 9:26 AM, Karl Wright <
>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> This may be nothing.  We've seen this before.  I'll look at
>>>>>>>>>>>>>>>> the log first chance I get, but if the crawl succeeds it may be a non-issue.
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 9:23 AM, Dmitry Goldenberg <
>>>>>>>>>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Hi Karl,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks for such a quick turnaround! I have just tested
>>>>>>>>>>>>>>>>> this new service. I believe we've gone past the 401/Unauthorized error from
>>>>>>>>>>>>>>>>> MCPermissions. This is great news.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> However, I'm seeing quite a few errors like the ones below:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> org.apache.axis.ConfigurationException: No service named
>>>>>>>>>>>>>>>>> ListsSoap is available
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> org.apache.axis.ConfigurationException: No service named
>>>>>>>>>>>>>>>>> http://schemas.microsoft.com/sharepoint/soap/GetListCollectionis available
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> org.apache.axis.ConfigurationException: No service named
>>>>>>>>>>>>>>>>> PermissionsSoap is available
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Is this perhaps a build snag on my part, do I need to
>>>>>>>>>>>>>>>>> place the wsdl's someplace? Any ideas?  I'm attaching a new logfile with
>>>>>>>>>>>>>>>>> these errors in it.
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 5:15 AM, Karl Wright <
>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> FWIW, you can download the revised plugin from
>>>>>>>>>>>>>>>>>> http://people.apache.org/~kwright/MetaCarta.SharePoint.MCPermissionsService.wsp.
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 4:18 AM, Karl Wright <
>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> I've looked into how difficult it would be to do a
>>>>>>>>>>>>>>>>>>> native implementation of the site, library, and list functionality provided
>>>>>>>>>>>>>>>>>>> by Permissions.asmx, and I conclude that it is fairly straightforward to do
>>>>>>>>>>>>>>>>>>> this.  If you are interested, I'd be willing to create a new version of
>>>>>>>>>>>>>>>>>>> MCPermissions that works in this way.  In order to confirm that it really
>>>>>>>>>>>>>>>>>>> works, though, I'd need support from you or others to try out the code and
>>>>>>>>>>>>>>>>>>> confirm it really does what I think it should be doing.  Would you be
>>>>>>>>>>>>>>>>>>> willing to help in this manner?
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> Thanks in advance!
>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 3:56 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Sorry, gmail hiccup.  Here's the url:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> http://msdn.microsoft.com/en-us/library/permissions.permissions.getpermissioncollection%28v=office.12%29.aspx
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 3:56 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> Dmitry: You may also want to read this MSDN article,
>>>>>>>>>>>>>>>>>>>>> because apparently your user needs "Full control" in order to access the
>>>>>>>>>>>>>>>>>>>>> method in Permissions.asmx we need.
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Wed, Sep 4, 2013 at 3:50 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> I have pinged one other user who set this up
>>>>>>>>>>>>>>>>>>>>>> successfully in Amazon.  He did not report any difficulties with
>>>>>>>>>>>>>>>>>>>>>> MCPermissions talking with Permissions in that setup, but he certainly can
>>>>>>>>>>>>>>>>>>>>>> give you a run down of how he configured the instance, and how he
>>>>>>>>>>>>>>>>>>>>>> configured the connection.  But he usually takes his time in responding and
>>>>>>>>>>>>>>>>>>>>>> I haven't heard back from him yet.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> In the long run, since you ARE able to reach
>>>>>>>>>>>>>>>>>>>>>> MCPermissions and the difficulty is in actually trying to reach Permissions
>>>>>>>>>>>>>>>>>>>>>> from MCPermissions, a problem which arises on SharePoint 2010 as I said
>>>>>>>>>>>>>>>>>>>>>> whenever there is a redirection, we could entertain the notion of trying to
>>>>>>>>>>>>>>>>>>>>>> not rely on the Microsoft Permissions service at all.  We'd need to extend
>>>>>>>>>>>>>>>>>>>>>> the plugin to write a native C# implementation of the functionality in the
>>>>>>>>>>>>>>>>>>>>>> Permissions service we use to obtain acls for sites and libraries.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 10:44 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> "What about the rowLimit query parameter on the
>>>>>>>>>>>>>>>>>>>>>>> options for the GetListItems call?  It can be set to be a very large number
>>>>>>>>>>>>>>>>>>>>>>> thereby allowing you to get more than the Microsoft default (1000 items, I
>>>>>>>>>>>>>>>>>>>>>>> believe)."
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Believe me, we don't lightly put functionality in
>>>>>>>>>>>>>>>>>>>>>>> the plugin.  You can set whatever you want for the rowLimit, but Microsoft
>>>>>>>>>>>>>>>>>>>>>>> enforces a hard limit.  And the hard limit applies even if you try to do
>>>>>>>>>>>>>>>>>>>>>>> paging.  Not well documented and you have to experiment to see it.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Workarounds:  I will ping other people I know who
>>>>>>>>>>>>>>>>>>>>>>> have successfully gotten connected to SharePoint on Amazon and get back to
>>>>>>>>>>>>>>>>>>>>>>> you.
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 10:39 AM, Dmitry Goldenberg <
>>>>>>>>>>>>>>>>>>>>>>> dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Karl,
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> I just hit <base>/_vti_bin/Permissions.asmx and it
>>>>>>>>>>>>>>>>>>>>>>>> is fine and accessible. So that is probably not an issue.
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> "When the plugin attempts to connect to the
>>>>>>>>>>>>>>>>>>>>>>>> Permissions web service, it retrieves the credentials to use from the
>>>>>>>>>>>>>>>>>>>>>>>> Microsoft credential cache. But other aspects of the connection (such as
>>>>>>>>>>>>>>>>>>>>>>>> the URL) come from whatever SharePoint or ASP has provided in the
>>>>>>>>>>>>>>>>>>>>>>>> environment of the plugin. So if those don't match up, it can't get in."
>>>>>>>>>>>>>>>>>>>>>>>> --  is there any way or technique for establishing whether this is what's
>>>>>>>>>>>>>>>>>>>>>>>> happening?  And what would be the workaround?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Also, any workaround you could recommend
>>>>>>>>>>>>>>>>>>>>>>>> generally?  I'm pretty hosed for now...
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> "For SharePoint 2010, there is a restriction on the
>>>>>>>>>>>>>>>>>>>>>>>> number of documents you can list in any one library. The size is variable
>>>>>>>>>>>>>>>>>>>>>>>> and unpredictable, and there is no way to reach or list documents beyond
>>>>>>>>>>>>>>>>>>>>>>>> the limit using Microsoft web services."  --  What about the rowLimit query
>>>>>>>>>>>>>>>>>>>>>>>> parameter on the options for the GetListItems call?  It can be set to be a
>>>>>>>>>>>>>>>>>>>>>>>> very large number thereby allowing you to get more than the Microsoft
>>>>>>>>>>>>>>>>>>>>>>>> default (1000 items, I believe).  Was the issue the concern that there
>>>>>>>>>>>>>>>>>>>>>>>> still may be more than that "very large number" of items in lists in
>>>>>>>>>>>>>>>>>>>>>>>> certain installations?
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 10:16 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Since this is an amazon instance, there's quite a
>>>>>>>>>>>>>>>>>>>>>>>>> good chance that a redirection is indeed taking place.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> When the plugin attempts to connect to the
>>>>>>>>>>>>>>>>>>>>>>>>> Permissions web service, it retrieves the credentials to use from the
>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft credential cache.  But other aspects of the connection (such as
>>>>>>>>>>>>>>>>>>>>>>>>> the URL) come from whatever SharePoint or ASP has provided in the
>>>>>>>>>>>>>>>>>>>>>>>>> environment of the plugin.  So if those don't match up, it can't get in.
>>>>>>>>>>>>>>>>>>>>>>>>> It's also possible that on Amazon instances, the SharePoints have the
>>>>>>>>>>>>>>>>>>>>>>>>> Permissions web service actually disabled, so they would return a 401 no
>>>>>>>>>>>>>>>>>>>>>>>>> matter who accesses them.  You can confirm that by trying to get to the
>>>>>>>>>>>>>>>>>>>>>>>>> permissions service directly in a browser - http://<base>/_vti_bin/Permissions.asmx
>>>>>>>>>>>>>>>>>>>>>>>>> -
>>>>>>>>>>>>>>>>>>>>>>>>> and see if you get a reasonable response, or an
>>>>>>>>>>>>>>>>>>>>>>>>> "unauthorized" one.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> As for why the plugin is needed:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> (1) For SharePoint 2007 and after, it is possible
>>>>>>>>>>>>>>>>>>>>>>>>> to set permissions on files and folders.  But there is no way to retrieve
>>>>>>>>>>>>>>>>>>>>>>>>> those permissions through web services without a custom plugin; the
>>>>>>>>>>>>>>>>>>>>>>>>> permissions are available only for sites and libraries.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> (2) For SharePoint 2010, there is a restriction on
>>>>>>>>>>>>>>>>>>>>>>>>> the number of documents you can list in any one library.  The size is
>>>>>>>>>>>>>>>>>>>>>>>>> variable and unpredictable, and there is no way to reach or list documents
>>>>>>>>>>>>>>>>>>>>>>>>> beyond the limit using Microsoft web services.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> I believe others have used MCF on SharePoint in
>>>>>>>>>>>>>>>>>>>>>>>>> amazon successfully - I hope they chime in and give you some useful advice.
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 10:05 AM, Dmitry Goldenberg
>>>>>>>>>>>>>>>>>>>>>>>>> <dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Karl,
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> I've looked through all the categories of Windows
>>>>>>>>>>>>>>>>>>>>>>>>>> events.  The Security log doesn't have any errors, just success messages
>>>>>>>>>>>>>>>>>>>>>>>>>> for:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:04 PM      Credential Validation --
>>>>>>>>>>>>>>>>>>>>>>>>>>    logon account: administrator, source workstation (my comp)
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:04 PM      Special Login -- for the
>>>>>>>>>>>>>>>>>>>>>>>>>>    Administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:04 PM      Logon -- for Administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Credential Validation --
>>>>>>>>>>>>>>>>>>>>>>>>>>    logon account: administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Special Login --
>>>>>>>>>>>>>>>>>>>>>>>>>>    Administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Logon -- Administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Logoff -- Administrator
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Logon -- ANONYMOUS LOGON
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM      Logoff -- ANONYMOUS LOGON
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> The Application log has:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:04 PM      Warning - SharePoint
>>>>>>>>>>>>>>>>>>>>>>>>>>    Foundation -- Configuration -- Alternate
>>>>>>>>>>>>>>>>>>>>>>>>>>    access mappings have not been configured. Users or services are accessing
>>>>>>>>>>>>>>>>>>>>>>>>>>    the site http://amazona-1monjv9 with the URL
>>>>>>>>>>>>>>>>>>>>>>>>>>    http://ec2-23-20-55-72.compute-1.amazonaws.com.
>>>>>>>>>>>>>>>>>>>>>>>>>>    This may cause incorrect links to be stored or returned to users. If this
>>>>>>>>>>>>>>>>>>>>>>>>>>    is expected, add the URL
>>>>>>>>>>>>>>>>>>>>>>>>>>    http://ec2-23-20-55-72.compute-1.amazonaws.comas an AAM response URL. For more information, see:
>>>>>>>>>>>>>>>>>>>>>>>>>>    http://go.microsoft.com/fwlink/?LinkId=114854
>>>>>>>>>>>>>>>>>>>>>>>>>>    "/>
>>>>>>>>>>>>>>>>>>>>>>>>>>    - 1:47:05 PM       Information --
>>>>>>>>>>>>>>>>>>>>>>>>>>    MCPermissions.asmx -- The request failed with
>>>>>>>>>>>>>>>>>>>>>>>>>>    HTTP status 401: Unauthorized.
>>>>>>>>>>>>>>>>>>>>>>>>>>    - A couple more of those warnings about
>>>>>>>>>>>>>>>>>>>>>>>>>>    alternate access mappings.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Does that give us any more clues?  I'm a little
>>>>>>>>>>>>>>>>>>>>>>>>>> worried about the time coincidence of the "Anonymous logon", however that's
>>>>>>>>>>>>>>>>>>>>>>>>>> coming about, with the 401 being generated. Is it possible that somehow the
>>>>>>>>>>>>>>>>>>>>>>>>>> request drops the original Admin creds and flips into this anonymous state?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Beyond that, can you think of a workaround we
>>>>>>>>>>>>>>>>>>>>>>>>>> could use?  I.e., have the MC service be there but use a different version
>>>>>>>>>>>>>>>>>>>>>>>>>> in the repo connection config (I think I've tried that); or uninstall the
>>>>>>>>>>>>>>>>>>>>>>>>>> service and then try some config against that?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Could you also tell me why the MCPermissions
>>>>>>>>>>>>>>>>>>>>>>>>>> service is needed? The doc doesn't seem to be quite clear about that.  Why
>>>>>>>>>>>>>>>>>>>>>>>>>> are the two methods for lists and permissions needed for SP 2010?
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 9:07 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On a straight SharePoint system with no funky
>>>>>>>>>>>>>>>>>>>>>>>>>>> options, I just log in with administrator credentials and run setup.bat.
>>>>>>>>>>>>>>>>>>>>>>>>>>> That usually works.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Reasons why it might not work in general involve
>>>>>>>>>>>>>>>>>>>>>>>>>>> redirections.  If you get into the MCPermissions.asmx via a redirection,
>>>>>>>>>>>>>>>>>>>>>>>>>>> for instance, then when MCPermissions tries to talk to Permissions it seems
>>>>>>>>>>>>>>>>>>>>>>>>>>> to be coming from the wrong place and wont permit it.  But I didn't see
>>>>>>>>>>>>>>>>>>>>>>>>>>> anything in the log that indicated a redirection was taking place, although
>>>>>>>>>>>>>>>>>>>>>>>>>>> I didn't look in detail.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> In the end you may need to look in the
>>>>>>>>>>>>>>>>>>>>>>>>>>> SharePoint and Windows event logs to see what is wrong.
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 8:57 AM, Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>> Goldenberg <dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Karl,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Could you elaborate on this point: "installed
>>>>>>>>>>>>>>>>>>>>>>>>>>>> by a user with full admin privs" ?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm logged into the server box with the same
>>>>>>>>>>>>>>>>>>>>>>>>>>>> credentials as the ones I use to connect using the ManifoldCF job.  That
>>>>>>>>>>>>>>>>>>>>>>>>>>>> user is a Farm Administrator, he's also a Site Collection Administrator.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> From the Windows standpoint, this user is
>>>>>>>>>>>>>>>>>>>>>>>>>>>> marked as Administrator and Password-protected. The only other user in the
>>>>>>>>>>>>>>>>>>>>>>>>>>>> system is Guest. This is an EC2 box and is of type Windows Server 2008 R2
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Datacenter, Service Pack 1.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Is there anything you think I should check or
>>>>>>>>>>>>>>>>>>>>>>>>>>>> try?  I think this is a "full admin" but let me know if there's something
>>>>>>>>>>>>>>>>>>>>>>>>>>>> missing.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> (Hmm, one idea I just had.. should the
>>>>>>>>>>>>>>>>>>>>>>>>>>>> setup.bat be run via a right-click -> Run as administrator in Windows?)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 2:20 AM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> From your logs, you are successfully
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> interacting with the lists service.  Then, it tries to talk with the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> MCPermissions service and authenticates properly, but:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,530]-[Thread-1666]-[DEBUG] org.apache.http.wire  - << "HTTP/1.1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 500 Internal Server Error[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,531]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Cache-Control: private[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,531]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Content-Type: text/xml; charset=utf-8[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,532]-[Thread-1666]-[DEBUG] org.apache.http.wire  - << "Server:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft-IIS/7.5[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,533]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "X-AspNet-Version: 2.0.50727[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,534]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Persistent-Auth: true[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,534]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "X-Powered-By: ASP.NET[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,535]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "MicrosoftSharePointTeamServices: 14.0.0.4762[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,536]-[Thread-1666]-[DEBUG] org.apache.http.wire  - << "Date: Tue,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 03 Sep 2013 04:13:37 GMT[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,536]-[Thread-1666]-[DEBUG] org.apache.http.wire  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Content-Length: 677[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,537]-[Thread-1666]-[DEBUG] org.apache.http.wire  - << "[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,537]-[Thread-1666]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.conn.DefaultClientConnection  - Receiving response:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HTTP/1.1 500 Internal Server Error
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,538]-[Thread-1666]-[DEBUG] org.apache.http.headers  - << HTTP/1.1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 500 Internal Server Error
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,538]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cache-Control: private
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,538]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Content-Type: text/xml; charset=utf-8
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,539]-[Thread-1666]-[DEBUG] org.apache.http.headers  - << Server:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft-IIS/7.5
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,539]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> X-AspNet-Version: 2.0.50727
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,540]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Persistent-Auth: true
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,540]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> X-Powered-By: ASP.NET
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,541]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> MicrosoftSharePointTeamServices: 14.0.0.4762
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,541]-[Thread-1666]-[DEBUG] org.apache.http.headers  - << Date:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Tue, 03 Sep 2013 04:13:37 GMT
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,541]-[Thread-1666]-[DEBUG] org.apache.http.headers  - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Content-Length: 677
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,542]-[Thread-1666]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient  - Connection can be kept
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> alive indefinitely
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,543]-[Thread-1666]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient  - Authentication succeeded
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-03
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 00:13:41,543]-[Thread-1666]-[DEBUG] org.apache.http.wire  - << "<?xml
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://schemas.xmlsoap.org/soap/envelope/"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> xmlns:xsi="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema"><soap:Body><soap:Fault><faultcode>soap:Client</faultcode><faultstring>The
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> request failed with HTTP status 401: Unauthorized.</faultstring><faultactor>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://ec2-23-20-55-72.compute-1.amazonaws.com/_vti_bin/MCPermissions.asmx</faultactor><detail><Error><ErrorNumber>1000</ErrorNumber><ErrorMessage>The
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> request failed with HTTP status 401:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized.</ErrorMessage><ErrorSource>System.Web.Services</ErrorSource></Error></detail></soap:Fault></soap:Body></soap:Envelope>"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> AxisFault
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultCode: {
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://schemas.xmlsoap.org/soap/envelope/}Client
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultSubcode:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultString: The request failed with HTTP
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> status 401: Unauthorized.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultActor:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://ec2-23-20-55-72.compute-1.amazonaws.com/_vti_bin/MCPermissions.asmx
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultNode:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultDetail:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> {}Error:<ErrorNumber>1000</ErrorNumber><ErrorMessage>The request failed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> with HTTP status 401:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized.</ErrorMessage><ErrorSource>System.Web.Services</ErrorSource>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <<<<<<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The "error 1000" you are seeing comes from the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> plugin; it is trying to communicate locally with the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /_vti_bin/Permissions.asmx service, and failing with a 401 error.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The most common reason for this failure is
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> that the user you used to install MCPermissions.asmx does not have
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> permissions to talk to Permissions.asmx.  I usually recommend that this
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> service be installed by a user with full admin privs.  Other people have
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> reported that when you use Claim Space Authentication in conjunction with
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Kerberos, there is also a problem related to the Microsoft credential
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> cache.  We're still trying to figure out what to do about that problem, so
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I hope that's not what you are attempting. ;-)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Sep 3, 2013 at 12:30 AM, Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Goldenberg <dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Karl,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm attaching everything that got written to
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the log file. This is what happens when I click Save in the Repository
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Connection definition page w/o actually changing anything, so it's working
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> off saved data.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Strangely, when switching to the Status and
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Job Management view, when I click the Start button on my SP crawl job,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> seemingly nothing happens, I get no extra output in the logs. I have
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> managed previously to actually kick a job off and it'd fail with that
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> different error, not a 401 I believe but the service not found.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm also attaching my logging.ini, I'm pretty
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sure it's clean but maybe I'm somehow short-circuiting some of the log
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> generation.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I'm attaching my properties.xml file as well.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Is there anything that needs to be done for WSDD or WSDL's there?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Mainly, the log you requested is attached,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> hopefully it contains some good clues.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Sep 2, 2013 at 7:33 PM, Karl Wright <
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dmitry,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The debug output you provided did not show
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the NTLM handshake, just the first part of the transaction (the NTLM
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Authenticate header), so it is incomplete.  I'd like to see the full wire
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> transaction, with NTLM enabled on the server, that shows the ListsSoap
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> service not found error.  Then I can decide if the MCPermissions service
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> has been reached and what its full response is.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Sep 2, 2013 at 7:21 PM, Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Goldenberg <dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Karl,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks so much for your prompt and detailed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> response.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On the first issue, we do not actually need
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the support for Basic auth; we were just experimenting to get any of the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> auth modes to work with the ManifoldCF's SharePoint plugin.  As of right
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> now, NTLM doesn't work either (I included the HTTP client debug info + the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> stack trace, those were generated with the auth provider set to NTLM).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On the second issue, here's the breakdown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> of the versions:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 1. The server version is: SP 2010, the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft.SharePoint.dll version is:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 14.0.4762.1000. Configuration database
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> version: 14.0.4762.1000.  Which I believe
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> is known as SharePoint 2010, RTM / Farm Build Version.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 2. The repository configuration is using
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "4.0" in the version pulldown.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3. The SharePoint plugin is SP 2010. It's
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> from the sharepoint-2010 directory, with the 12 kb size of the MC wsp file
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> (rather than 11 kb in the SP 2010 subdirectory).
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 4. The build of ManifoldCF is 1.3.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 5. The system was built from sources using
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the following commands: ant make-core-deps, then ant build.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 6. The system was started by: cd
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> dist/example; java -jar start.jar.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Please also note that we've tried the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Derby-based persistence first and then the Postgres-based persistence.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The results appear to be the same although
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the symptoms seem to fluctuate between the 401 error and the service not
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> found error. I believe this is most likely due to difference in gestures in
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the UI; re-saving the repository config seems to generate different errors
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> than firing off a crawl.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Given all this, do you have any ideas on
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> what might be causing the failures and/or any additional ways of
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> troubleshooting? I can generate fuller logs for specific UI gestures, if
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> need be.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> - Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Sep 2, 2013 at 5:36 PM, Karl Wright
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> <daddywri@gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Hi Dimitry,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The SharePoint connector does not support
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> basic auth at this time.  It's so rare that heretofore we've never
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> encountered it.  NTLM is what everyone seems to use.  However, it is
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> straightforward to add this logic.  If you want it, please create a Jira
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ticket for it.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> As for the "ListsSoap not found" error,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> there may be a mismatch between the version of SharePoint you have and the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> MCPermissions service version you installed.  There is a SharePoint 2007
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> version, which only is appropriate for SharePoint 2007, and when you select
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 3.0 (2007) in the version pullldown. There is also a 2010 plugin, which is
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> different, which is used when you select 4.0 (2010) in the version pulldown.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Thanks,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Karl
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Sep 2, 2013 at 5:18 PM, Dmitry
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Goldenberg <dgoldenberg@kmwllc.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I get the attached stack trace on a GetListCollection
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> request as below.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I have configured a 4.0 SP repository
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> connection. The username is <domain>\<user> and it's got a valid password;
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I am able to login to the SP instance with those (admin) credentials.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I've verified that I have the
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> MCPermissionsService installed.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> I noticed that one time I was able to
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> seemingly go past this error after switching from Basic auth to NTLM.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> However, then I started getting a different error -- No
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> service named ListsSoap is available.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> If I uninstall the MC service and try to
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> use the 2.0 or 3.0 type of connection, I'm getting errors also.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Any help or insights or troubleshooting
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> tips would be appreciated.  The http client DEBUG dump is also included
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> below as the second part of the attached info. Thanks.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ============================================================================
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>  faultString: The request failed with
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HTTP status 401:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> faultActor:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://ec2-23-20-55-72.compute-1.amazonaws.com/_vti_bin/MCPermissions.asmx
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> faultNode:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> faultDetail:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> {}Error:<ErrorNumber>1000</ErrorNumber><ErrorMessage>The request failed
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> with HTTP status 401:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized.</ErrorMessage><ErrorSource>System.Web.Services</ErrorSource>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> The request failed with HTTP status 401:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                               at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                       at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)             at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                   at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                                   at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.parsers.XML11Configuration.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                                   at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.parsers.XMLParser.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                                            at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                                    at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                             at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.xerces.jaxp.SAXParserImpl.parse(Unknown
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Source)                                                           at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.axis.client.Call.invoke(Call.java:2767)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 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.sharepoint.webpartpages.PermissionsSoapStub.getPermissionCollection(PermissionsSoapStub.java:200)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.checkConnection(SPSProxyHelper.java:1466)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.check(SharePointRepository.java:377)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jsp.viewconnection_jsp._jspService(viewconnection_jsp.java:268)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:288)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.Dispatcher.forward(Dispatcher.java:115)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:709)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:680)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jsp.execute_jsp._jspService(execute_jsp.java:328)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:388)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:480)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:520)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.Server.handle(Server.java:349)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:936)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:801)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:224)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:51)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:586)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:44)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> at
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533)
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ======================================================================================
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,986]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient - Attempt 1 to execute request
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,986]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.conn.DefaultClientConnection - Sending request: POST
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /_vti_bin/MCPermissions.asmx HTTP/1.1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,987]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "POST
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /_vti_bin/MCPermissions.asmx HTTP/1.1[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,987]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Content-Type:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> text/xml; charset=utf-8[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,987]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Accept:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> */*[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,988]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "SOAPAction: "
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://microsoft.com/sharepoint/webpartpages/GetPermissionCollection
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,988]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "User-Agent:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Axis/1.4[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,988]-[Thread-609]-[DEBUG] org.apache.http.wire - >>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Content-Length: 420[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,988]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Host:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ec2-23-20-55-72.compute-1.amazonaws.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,989]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Connection:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Keep-Alive[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,989]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Cookie:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WSS_KeepSessionAuthenticated={5ecf7334-276b-471a-ae98-8591c7280476}[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,989]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "Cookie2:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> $Version=1[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,989]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,989]-[Thread-609]-[DEBUG] org.apache.http.headers - >> POST
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /_vti_bin/MCPermissions.asmx HTTP/1.1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,990]-[Thread-609]-[DEBUG] org.apache.http.headers - >>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Content-Type: text/xml; charset=utf-8
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,990]-[Thread-609]-[DEBUG] org.apache.http.headers - >> Accept: */*
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,990]-[Thread-609]-[DEBUG] org.apache.http.headers - >> SOAPAction:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://microsoft.com/sharepoint/webpartpages/GetPermissionCollection
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,990]-[Thread-609]-[DEBUG] org.apache.http.headers - >> User-Agent:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Axis/1.4
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,991]-[Thread-609]-[DEBUG] org.apache.http.headers - >>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Content-Length: 420
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,991]-[Thread-609]-[DEBUG] org.apache.http.headers - >> Host:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ec2-23-20-55-72.compute-1.amazonaws.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,991]-[Thread-609]-[DEBUG] org.apache.http.headers - >> Connection:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Keep-Alive
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,991]-[Thread-609]-[DEBUG] org.apache.http.headers - >> Cookie:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WSS_KeepSessionAuthenticated={5ecf7334-276b-471a-ae98-8591c7280476}
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,992]-[Thread-609]-[DEBUG] org.apache.http.headers - >> Cookie2:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> $Version=1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,992]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:07,993]-[Thread-609]-[DEBUG] org.apache.http.wire - >> "<?xml
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://schemas.xmlsoap.org/soap/envelope/"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> xmlns:xsd="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> xmlns:xsi="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body><GetPermissionCollection
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> xmlns="
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> http://microsoft.com/sharepoint/webpartpages/
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "><objectName>/</objectName><objectType>Web</objectType></GetPermissionCollection></soapenv:Body></soapenv:Envelope>"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,023]-[Thread-609]-[DEBUG] org.apache.http.wire - << "HTTP/1.1 401
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Unauthorized[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,023]-[Thread-609]-[DEBUG] org.apache.http.wire - << "Server:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft-IIS/7.5[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,023]-[Thread-609]-[DEBUG] org.apache.http.wire - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "SPRequestGuid: 65ed9f96-b358-4a17-9d65-b58f55d19b17[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,024]-[Thread-609]-[DEBUG] org.apache.http.wire - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "WWW-Authenticate: NTLM[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,024]-[Thread-609]-[DEBUG] org.apache.http.wire - << "X-Powered-By:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ASP.NET[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,024]-[Thread-609]-[DEBUG] org.apache.http.wire - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "MicrosoftSharePointTeamServices: 14.0.0.4762[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,024]-[Thread-609]-[DEBUG] org.apache.http.wire - << "Date: Mon, 02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sep 2013 20:58:04 GMT[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,025]-[Thread-609]-[DEBUG] org.apache.http.wire - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> "Content-Length: 0[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,025]-[Thread-609]-[DEBUG] org.apache.http.wire - << "[\r][\n]"
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,026]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.conn.DefaultClientConnection - Receiving response:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> HTTP/1.1 401 Unauthorized
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,026]-[Thread-609]-[DEBUG] org.apache.http.headers - << HTTP/1.1
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 401 Unauthorized
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,026]-[Thread-609]-[DEBUG] org.apache.http.headers - << Server:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Microsoft-IIS/7.5
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,026]-[Thread-609]-[DEBUG] org.apache.http.headers - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SPRequestGuid: 65ed9f96-b358-4a17-9d65-b58f55d19b17
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,027]-[Thread-609]-[DEBUG] org.apache.http.headers - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> WWW-Authenticate: NTLM
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,027]-[Thread-609]-[DEBUG] org.apache.http.headers - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> X-Powered-By: ASP.NET
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,027]-[Thread-609]-[DEBUG] org.apache.http.headers - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> MicrosoftSharePointTeamServices: 14.0.0.4762
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,028]-[Thread-609]-[DEBUG] org.apache.http.headers - << Date: Mon,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 02 Sep 2013 20:58:04 GMT
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,028]-[Thread-609]-[DEBUG] org.apache.http.headers - <<
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Content-Length: 0
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,028]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient - Connection can be kept
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> alive indefinitely
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,029]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient - Authentication required
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,029]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient -
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ec2-23-20-55-72.compute-1.amazonaws.com:80requested authentication
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,029]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.TargetAuthenticationStrategy - Authentication
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> schemes in the order of preference: [negotiate, Kerberos, NTLM, Digest,
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Basic]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,030]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> negotiate authentication scheme not available
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,030]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Kerberos authentication scheme not available
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,030]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Digest authentication scheme not available
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,031]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.TargetAuthenticationStrategy - Challenge for
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Basic authentication scheme not available
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,032]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.impl.client.DefaultHttpClient - Selected authentication
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> options: [NTLM]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,032]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,033]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,033]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,033]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,033]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,033]-[Thread-609]-[DEBUG] org.apache.axis.SOAPPart - Enter:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SOAPPart::saveChanges
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,034]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestAddCookies - CookieSpec selected:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> best-match
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,034]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestAddCookies - Cookie [version:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 0][name: WSS_KeepSessionAuthenticated][value:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> {5ecf7334-276b-471a-ae98-8591c7280476}][domain:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ec2-23-20-55-72.compute-1.amazonaws.com][path:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> /][expiry: null] match [
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ec2-23-20-55-72.compute-1.amazonaws.com:80/_vti_bin/MCPermissions.asmx
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,035]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestAuthCache - Auth cache not set in
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> the context
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,035]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestTargetAuthentication - Target auth
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> state: CHALLENGED
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,035]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestTargetAuthentication - Generating
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> response to an authentication challenge using ntlm scheme
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2013-09-02
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 16:58:08,036]-[Thread-609]-[DEBUG]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> org.apache.http.client.protocol.RequestProxyAuthentication - Proxy auth
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> state: UNCHALLENGED
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Mime
View raw message