Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8014B10875 for ; Fri, 26 Jul 2013 08:29:47 +0000 (UTC) Received: (qmail 12358 invoked by uid 500); 26 Jul 2013 08:29:47 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 11503 invoked by uid 500); 26 Jul 2013 08:29:40 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 11484 invoked by uid 99); 26 Jul 2013 08:29:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jul 2013 08:29:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of daddywri@gmail.com designates 209.85.128.182 as permitted sender) Received: from [209.85.128.182] (HELO mail-ve0-f182.google.com) (209.85.128.182) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Jul 2013 08:29:32 +0000 Received: by mail-ve0-f182.google.com with SMTP id m1so648104ves.41 for ; Fri, 26 Jul 2013 01:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ulpzpcfyYgJpfMxVKe9BSShHVSAJpvjYJlra9e2J6M8=; b=XcYzu+H2WKdnF3BT+FF4tkwIYCjoKatoFpPk9Ik1bok/qGdIt+vv/CuGXi25bf5ywG 1DGJiLzUMI/LpyteeDrja8822sn99WtHc2T96q4294t3LTdkETIeLGuAtRDol7Q9tUD+ f8CtLf581crXnAXH9AXFpP6bD2yvNKD4csVCBxcs/nKHEO1gDxEuZYC28JStN6kkOTum geKc7Tiqlgj5oQOjbkeWH1Bc9KJLeBswSTyHia9fvdsThEk4xafuE2wbKoWunKZjVUKC CWcGGNAMA/VNmtxN9CF/8unY9qewMT/NEfgI5cdOvhlzwW2Ghlz1wY/opuJ9ljn38Vkr kk2Q== MIME-Version: 1.0 X-Received: by 10.58.96.76 with SMTP id dq12mr19838195veb.91.1374827351093; Fri, 26 Jul 2013 01:29:11 -0700 (PDT) Received: by 10.58.225.73 with HTTP; Fri, 26 Jul 2013 01:29:10 -0700 (PDT) In-Reply-To: References: <7470e3ee92e344ef98c2fbddba8de24a@DBXPR03MB063.eurprd03.prod.outlook.com> Date: Fri, 26 Jul 2013 04:29:10 -0400 Message-ID: Subject: Re: Sharepoint claim space authentication From: Karl Wright To: "user@manifoldcf.apache.org" Content-Type: multipart/alternative; boundary=089e012942eae3b91404e265ef85 X-Virus-Checked: Checked by ClamAV on apache.org --089e012942eae3b91404e265ef85 Content-Type: text/plain; charset=ISO-8859-1 Hi Will, Did this work for you? I'd like to integrate the code into trunk if so. Karl On Tue, Jul 23, 2013 at 9:13 PM, Karl Wright wrote: > Hi Will, > > I made the logging change. Can you try it out? This is how: > > (1) Check out the branch onto your Windows development system: > > svn co > https://svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/branches/CONNECTORS-758 > > (2) Read the README.txt file, and make sure you have all the necessary > dependencies installed appropriately, especially the sharepoint assembly. > > (3) Build, using "ant build". > > (4) Install your newly-built MCPermissions web service (using the > dist\update.bat script) > > Then, try it out, and please let me know if it logs anything to the trace > log, etc. > > Thanks! > Karl > > > > On Tue, Jul 23, 2013 at 7:31 PM, Will Parkinson wrote: > >> Hi Karl, >> >> I was talking to the Sharepoint administrator last night and he would >> also prefer the logs entries to be written to the trace logs. If you had >> the time to build a Sharepoint plugin for 2010 that would be fantastic. >> >> Cheers, >> >> Will >> >> >> On Tue, Jul 23, 2013 at 10:04 PM, Karl Wright wrote: >> >>> Using the trace log may well work for us. I've created a ticket for >>> this work: CONNECTORS-758. Will, do you have anything further to report on >>> logging research? Should I build a trial SharePoint 2010 plugin for you to >>> explore in your environment? >>> >>> Karl >>> >>> >>> On Sun, Jul 21, 2013 at 9:21 PM, Karl Wright wrote: >>> >>>> The link provided looks pretty helpful. But it is also tricky enough >>>> that I would not want to be changing the log output with a SharePoint >>>> system available to try it all out on. Specifically, you need to write a >>>> feature handler to register the appropriate log category; I'm not sure how >>>> to integrate that with the current package properly. >>>> >>>> Karl >>>> >>>> >>>> >>>> On Thu, Jul 18, 2013 at 3:45 AM, Christian M. Rieck < >>>> christian.rieck@comperiosearch.com> wrote: >>>> >>>>> > There may be a SharePoint application log we could use instead - >>>>> but I have no idea how to access such a thing. I'll see if Google >>>>> can tell me.**** >>>>> >>>>> ** ** >>>>> >>>>> In SharePoint 2010 it is common to write to the ULS logs*. This also >>>>> lets you control the log-level through central admin. Check out >>>>> http://www.parago.de/2011/01/how-to-implement-a-custom-sharepoint-2010-logging-service-for-uls-and-windows-event-log/and >>>>> http://dbremes.wordpress.com/2010/09/02/using-sharepoint-2010s-logging-infrastructure-part-2/, they should explain it. I skipped the Event-log and registry parts for my >>>>> implementation, only writing to ULS (what they call trace log)**** >>>>> >>>>> ** ** >>>>> >>>>> (Note that I have no knowledge of the plugin being discussed here and >>>>> may give an answer to a question nobody really asked..)**** >>>>> >>>>> ** ** >>>>> >>>>> Christian.**** >>>>> >>>>> ** ** >>>>> >>>>> *From:* Karl Wright [mailto:daddywri@gmail.com] >>>>> *Sent:* 17. juli 2013 14:22 >>>>> *To:* user@manifoldcf.apache.org >>>>> *Subject:* Re: Sharepoint claim space authentication**** >>>>> >>>>> ** ** >>>>> >>>>> Hi Will, >>>>> >>>>> I'm not an expert on writing SharePoint plugins. The plugin we have >>>>> just uses the standard C# EventLog class, which knows where the Windows >>>>> event log is on whatever system the plugin is running on. Having the >>>>> plugin create and manage its own log is fraught with permission problems, >>>>> which is why we send error notifications of this kind to the event log. >>>>> **** >>>>> >>>>> There may be a SharePoint application log we could use instead - but I >>>>> have no idea how to access such a thing. I'll see if Google can tell me. >>>>> >>>>> Karl**** >>>>> >>>>> ** ** >>>>> >>>>> On Wed, Jul 17, 2013 at 8:17 AM, Will Parkinson < >>>>> parkinson.will@gmail.com> wrote:**** >>>>> >>>>> Hi Karl,**** >>>>> >>>>> Thanks for creating that ticket.**** >>>>> >>>>> ** ** >>>>> >>>>> The sharepoint version is 2010. I will obtain the build number from >>>>> the Sharepoint administrator**** >>>>> >>>>> I would assume the WSP file file would obtain the event log file path >>>>> and name from the sharepoint installation. I am only new to manifoldCF so >>>>> that might be completely incorrect. Would it be infeasible to have the >>>>> plugin create its own log file?**** >>>>> >>>>> Cheers,**** >>>>> >>>>> Will**** >>>>> >>>>> ** ** >>>>> >>>>> On Wed, Jul 17, 2013 at 8:49 PM, Karl Wright >>>>> wrote:**** >>>>> >>>>> I've created the ticket: >>>>> https://issues.apache.org/jira/browse/CONNECTORS-754 . Some of the >>>>> information may be incorrect, but at least it is a starting point.**** >>>>> >>>>> I will be taking steps immediately on trunk to harden the connector >>>>> against the array index issues, but I strongly suspect that the underlying >>>>> problem is that there are at least a few sorts of entities in this >>>>> situation that are causing the plugin to not work as expected. Getting >>>>> logging working there is essential to correcting that problem.**** >>>>> >>>>> Karl**** >>>>> >>>>> ** ** >>>>> >>>>> On Wed, Jul 17, 2013 at 6:18 AM, Karl Wright >>>>> wrote:**** >>>>> >>>>> Hi Will,**** >>>>> >>>>> These issues may very well be related. >>>>> ** >>>>> ****** >>>>> >>>>> The logic that is giving you the "index out of range" error is >>>>> manipulating supposed relative paths it is getting from the SharePoint list >>>>> files method. Those paths are not showing up in a form the connector is >>>>> expecting, which is "library/folder_path". It is possible that claim space >>>>> paths are coming out differently and the connector would have to change to >>>>> accommodate that. The problem with Microsoft products in general is that >>>>> there are so many ways to configure them there is practically no chance of >>>>> adequately testing across the entire configuration space in advance.** >>>>> ** >>>>> >>>>> What I think we should do is create a ticket (and a branch) to do >>>>> diagnostics and development for this sharepoint variant. Could you provide >>>>> me with:**** >>>>> >>>>> - which SharePoint version this is, including the build number**** >>>>> >>>>> - how you think the logging for the MCPermissions.asmx should be done* >>>>> *** >>>>> >>>>> I'll create the ticket once I have that info. >>>>> >>>>> Karl**** >>>>> >>>>> ** ** >>>>> >>>>> On Wed, Jul 17, 2013 at 5:31 AM, Will Parkinson < >>>>> parkinson.will@gmail.com> wrote:**** >>>>> >>>>> Hi Karl,**** >>>>> >>>>> We have now tried a user with full access on that server and the error >>>>> still occurs. We have logged in as this user via RDP and tested that the >>>>> user could write to the log files and there was no problem.**** >>>>> >>>>> One this we did notice is that the log files for the sharepoint >>>>> installation are not in the default location. Would this possibly be the >>>>> issue?**** >>>>> >>>>> It also seems that we can ingest files from sharepoint despite the >>>>> "cannot open log source issue" but the logs are full of errors like this >>>>> >>>>> FATAL 2013-07-17 19:24:57,927 (Worker thread '46') - Error tossed: >>>>> String index out of range: 19 >>>>> java.lang.StringIndexOutOfBoundsException: String index out of range: >>>>> 19 >>>>> at java.lang.String.substring(String.java:1955) >>>>> at >>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository$FileStream.addFile(SharePointRepository.java:1890) >>>>> at >>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:655) >>>>> 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) >>>>> FATAL 2013-07-17 19:24:57,964 (Worker thread '5') - Error tossed: >>>>> String index out of range: 21 >>>>> java.lang.StringIndexOutOfBoundsException: String index out of range: >>>>> 21 >>>>> at java.lang.String.substring(String.java:1955) >>>>> at >>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository$FileStream.addFile(SharePointRepository.java:1890) >>>>> at >>>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.getChildren(SPSProxyHelper.java:655) >>>>> 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) >>>>> **** >>>>> >>>>> Would these issues be related? >>>>> >>>>> Cheers, >>>>> >>>>> Will**** >>>>> >>>>> ** ** >>>>> >>>>> On Mon, Jul 15, 2013 at 10:03 PM, Karl Wright >>>>> wrote:**** >>>>> >>>>> Hi Will, >>>>> >>>>> Here's an example of the code that attempts to access the log: >>>>> >>>>> EventLog.WriteEntry("MCPermissions.asmx", "Error: >>>>> "+ex.Message+"; SPContext.Current.Web.Url='"+SPContext.Current.Web.Url+"'"); >>>>> **** >>>>> >>>>> So I believe it will be trying to access the event log, and it is >>>>> failing to do that. Once that issue is resolved, the fact is that it does >>>>> not even attempt to log anything unless an earlier error occurred. So >>>>> there is more than one error involved. >>>>> >>>>> Karl**** >>>>> >>>>> ** ** >>>>> >>>>> On Mon, Jul 15, 2013 at 7:57 AM, Will Parkinson < >>>>> parkinson.will@gmail.com> wrote:**** >>>>> >>>>> Hi Karl, thanks for the quick response.**** >>>>> >>>>> I thought this might be the case initially, and have asked the >>>>> Sharepoint administrator about the user permissions used to install the >>>>> plugin and he assures me that the permissions are sufficient. Do you know >>>>> which log (location, file name) that the plugin tries to write to?**** >>>>> >>>>> **** >>>>> >>>>> ** ** >>>>> >>>>> On Mon, Jul 15, 2013 at 9:15 PM, Karl Wright >>>>> wrote:**** >>>>> >>>>> Hi Will, >>>>> >>>>> The issue seems to be around the ability of the MCPermissions plugin >>>>> to write to the log. As it was installed, it does not have the ability to >>>>> do that on your claim-space system.**** >>>>> >>>>> Usually, we recommend that the plugin be installed by a user that has >>>>> sufficient permissions to do everything the plugin needs to do. It does >>>>> not sound like that is the case here. >>>>> >>>>> Thanks, >>>>> Karl**** >>>>> >>>>> ** ** >>>>> >>>>> On Mon, Jul 15, 2013 at 6:37 AM, Will Parkinson < >>>>> parkinson.will@gmail.com> wrote:**** >>>>> >>>>> Hello,**** >>>>> >>>>> I have installed ManifoldCF and have added 2 Sharepoint repositories - >>>>> one Sharepoint site uses claim space authentication and the other one does >>>>> not.**** >>>>> >>>>> manifold seems to have no issue connecting to the non claim space >>>>> authenticated Sharepoint site but generates this error when trying to >>>>> connect to the claim space authenticated Sharepoint site:**** >>>>> >>>>> Connection status: Unknown SharePoint server error accessing site - >>>>> axis fault = Server, detail = Server was unable to process request. ---> >>>>> Cannot open log for source 'MCPermissions.asmx'. You may not have write >>>>> access. ---> Access is denied**** >>>>> >>>>> Has anybody experienced a similar problem with claim space >>>>> authenticated Sharepoint sites?**** >>>>> >>>>> Any help is much appreciated.**** >>>>> >>>>> - Will**** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>> >>>> >>> >> > --089e012942eae3b91404e265ef85 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Will,

Did this work for you?=A0 I'd lik= e to integrate the code into trunk if so.

Karl



On Tue, Jul 23,= 2013 at 9:13 PM, Karl Wright <daddywri@gmail.com> wrote:
Hi Will,

I made the logging change.=A0 Can y= ou try it out?=A0 This is how:

(1) Check out the branch onto your Windows development syst= em:

svn co https:/= /svn.apache.org/repos/asf/manifoldcf/integration/sharepoint-2010/branches/C= ONNECTORS-758

(2) Read the README.txt file, and make sure you have all the nece= ssary dependencies installed appropriately, especially the sharepoint assem= bly.

(3) Build, using "ant build".

(4) Install your newly-built MCPermissions web service (using the dis= t\update.bat script)

Then, try it out, and please let me know = if it logs anything to the trace log, etc.

Thanks!
Karl



On Tue, Jul 23, 2013 at 7:31= PM, Will Parkinson <parkinson.will@gmail.com> wrote:=
Hi Karl,

I was talki= ng to the Sharepoint administrator last night and he would also prefer the logs entries to be written to the trace=20 logs.=A0 If you had the time to build a Sharepoint plugin for 2010 that=20 would be fantastic.

Cheers,

Will


<= div class=3D"gmail_quote">On Tue, Jul 23, 2013 at 10:04 PM, Karl Wright <= daddywri@gmail.com> wrote:
Using the trace log may wel= l work for us.=A0 I've created a ticket for this work: CONNECTORS-758.= =A0 Will, do you have anything further to report on logging research?=A0 Sh= ould I build a trial SharePoint 2010 plugin for you to explore in your envi= ronment?

Karl

On Sun, Jul 21, 2013 at 9:21 PM, Karl Wright <= span dir=3D"ltr"><daddywri@gmail.com> wrote:
The link provided looks pre= tty helpful.=A0 But it is also tricky enough that I would not want to be ch= anging the log output with a SharePoint system available to try it all out = on.=A0 Specifically, you need to write a feature handler to register the ap= propriate log category; I'm not sure how to integrate that with the cur= rent package properly.

Karl


On Thu, Jul 18, 2013 at 3:45 AM, Christian= M. Rieck <christian.rieck@comperiosearch.com> wrote:

> There may be a SharePoint application log we co= uld use instead - but I have no idea how to access such a thing.=A0 I'll see if Google can tell me.

=A0

In SharePoint 2010 it is = common to write to the ULS logs*. This also lets you control the log-level = through central admin. Check out http://www.parago.de/2011/01/how-to-implement-a-custom-sharepoint-2010-logg= ing-service-for-uls-and-windows-event-log/ and http://dbremes.wordpress.com/2010/09/02/using-sharepoint-2010s-logging-infr= astructure-part-2/ , they should explain it. I skipped the Event-log an= d registry parts for my implementation, only writing to ULS (what they call= trace log)

=A0

(Note that I have no knowledge = of the plugin being discussed here and may give an answer to a question nob= ody really asked..)

=A0

Christian.

=A0=

From: Karl Wright [mailto:daddywri@gmail.com]
Sent: 17. juli 2013 14:22
To: = user@manifoldcf.apache.org
Subject: Re: Sharepoint claim space authentication

=A0

Hi Will,

I'm not an expert on writing SharePoint plugins.=A0 The plugin we have = just uses the standard C# EventLog class, which knows where the Windows eve= nt log is on whatever system the plugin is running on.=A0 Having the plugin= create and manage its own log is fraught with permission problems, which is why we send error notifications of this= kind to the event log.

There may be a = SharePoint application log we could use instead - but I have no idea how to= access such a thing.=A0 I'll see if Google can tell me.

Karl

=A0

On Wed, Jul 17, 2013 at 8:17 AM, Will Parkinso= n <= parkinson.will@gmail.com> wrote:

Hi Karl,=

Thanks for creating that ticket.=

=A0

The sharepoint = version is 2010.=A0 I will obtain the build number from the Sharepoint admi= nistrator

I would assume = the WSP file file would obtain the event log file path and name from the sh= arepoint installation.=A0 I am only new to manifoldCF so that might be comp= letely incorrect.=A0 Would it be infeasible to have the plugin create its own log= file?

Cheers,<= u>

Will

=A0

On Wed, Jul 17, 2013 at 8:49 PM, Karl Wright &= lt;dad= dywri@gmail.com> wrote:

I've create= d the ticket: https://issues.apache.org/jira/browse/CONNECTORS-754 . Some of the information may be incorrect, but at least it is a starting = point.

I will be takin= g steps immediately on trunk to harden the connector against the array inde= x issues, but I strongly suspect that the underlying problem is that there = are at least a few sorts of entities in this situation that are causing the pl= ugin to not work as expected.=A0 Getting logging working there is essential= to correcting that problem.

Karl

=A0

On Wed, Jul 17, 2013 at 6:18 AM, Karl Wright &= lt;dad= dywri@gmail.com> wrote:

Hi Will,=

These issues ma= y very well be related.

The logic that = is giving you the "index out of range" error is manipulating supp= osed relative paths it is getting from the SharePoint list files method.=A0= Those paths are not showing up in a form the connector is expecting, which is "li= brary/folder_path".=A0 It is possible that claim space paths are comin= g out differently and the connector would have to change to accommodate tha= t.=A0 The problem with Microsoft products in general is that there are so many ways to configure them there is practically no c= hance of adequately testing across the entire configuration space in advanc= e.

What I think we= should do is create a ticket (and a branch) to do diagnostics and developm= ent for this sharepoint variant.=A0 Could you provide me with:

- which SharePoint version this is, including = the build number

- how you think= the logging for the MCPermissions.asmx should be done=

I'll create= the ticket once I have that info.

Karl

=A0

On Wed, Jul 17, 2013 at 5:31 AM, Will Parkinso= n <= parkinson.will@gmail.com> wrote:

Hi Karl,=

We have now tri= ed a user with full access on that server and the error still occurs.=A0 We= have logged in as this user via RDP and tested that the user could write t= o the log files and there was no problem.

One this we did= notice is that the log files for the sharepoint installation are not in th= e default location.=A0 Would this possibly be the issue?

It also seems t= hat we can ingest files from sharepoint despite the "cannot open log s= ource issue" but the logs are full of errors like this

FATAL 2013-07-17 19:24:57,927 (Worker thread '46') - Error tossed: = String index out of range: 19
java.lang.StringIndexOutOfBoundsException: String index out of range: 19 =A0=A0=A0 at java.lang.String.substring(String.java:1955)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePoint= Repository$FileStream.addFile(SharePointRepository.java:1890)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHe= lper.getChildren(SPSProxyHelper.java:655)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePoint= Repository.processDocuments(SharePointRepository.java:1411)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnect= or.processDocuments(BaseRepositoryConnector.java:423)
=A0=A0=A0 at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerTh= read.java:559)
FATAL 2013-07-17 19:24:57,964 (Worker thread '5') - Error tossed: S= tring index out of range: 21
java.lang.StringIndexOutOfBoundsException: String index out of range: 21 =A0=A0=A0 at java.lang.String.substring(String.java:1955)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePoint= Repository$FileStream.addFile(SharePointRepository.java:1890)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHe= lper.getChildren(SPSProxyHelper.java:655)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.sharepoint.SharePoint= Repository.processDocuments(SharePointRepository.java:1411)
=A0=A0=A0 at org.apache.manifoldcf.crawler.connectors.BaseRepositoryConnect= or.processDocuments(BaseRepositoryConnector.java:423)
=A0=A0=A0 at org.apache.manifoldcf.crawler.system.WorkerThread.run(WorkerTh= read.java:559)

Would these issues be related?

Cheers,

Will

=A0

On Mon, Jul 15, 2013 at 10:03 PM, Karl Wright = <da= ddywri@gmail.com> wrote:

Hi Will,

Here's an example of the code that attempts to access the log:

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 EventLog.WriteEntry("MCP= ermissions.asmx", "Error: "+ex.Message+"; SPContext.Cur= rent.Web.Url=3D'"+SPContext.Current.Web.Url+"'");=

So I believe it= will be trying to access the event log, and it is failing to do that.=A0 O= nce that issue is resolved, the fact is that it does not even attempt to lo= g anything unless an earlier error occurred.=A0 So there is more than one error invol= ved.

Karl

=A0

On Mon, Jul 15, 2013 at 7:57 AM, Will Parkinso= n <= parkinson.will@gmail.com> wrote:

Hi Karl, thanks= for the quick response.

I thought this might be the case initially, an= d have asked the Sharepoint administrator about the user permissions used t= o install the plugin and he assures me that the permissions are sufficient.= =A0 Do you know which log (location, file name) that the plugin tries to write= to?

=A0

On Mon, Jul 15, 2013 at 9:15 PM, Karl Wright &= lt;dad= dywri@gmail.com> wrote:

Hi Will,

The issue seems to be around the ability of the MCPermissions plugin to wri= te to the log.=A0 As it was installed, it does not have the ability to do t= hat on your claim-space system.

Usually, we rec= ommend that the plugin be installed by a user that has sufficient permissio= ns to do everything the plugin needs to do.=A0 It does not sound like that = is the case here.

Thanks,
Karl

=A0

On Mon, Jul 15, 2013 at 6:37 AM, Will Parkinso= n <= parkinson.will@gmail.com> wrote:

Hello,

I have installed ManifoldCF and have added 2 Sharepoint repositori= es - one Sharepoint site uses claim space authentication and the other one = does not.

manifold seems to have no issue connecting to the non claim space = authenticated Sharepoint site but generates this error when trying to conne= ct to the claim space authenticated Sharepoint site:

Connection status: Unknown SharePoint server error accessing site = - axis fault =3D Server, detail =3D Server was unable to process request. -= --> Cannot open log for source 'MCPermissions.asmx'. You may not= have write access. ---> Access is denied

Has anybody experienced a similar problem with claim space authent= icated Sharepoint sites?

Any help is much appreciated.

- Will

=A0

=A0

=A0

=A0

=A0

=A0

=A0

=A0

=A0






--089e012942eae3b91404e265ef85--