Re: Not able to create sharepoint connection

[Karl Wright <da...@gmail.com>]

You might be interested to know that we now prebuild the SharePoint
MCPermissions web service, and will be including this as part of the
release for ManifoldCF 0.4-incubating.  You can pick it up on trunk
now; it's delivered (along with installation instructions and .bat
scripts) under dist/sharepoint-integration when you build.

Karl

On Wed, Jul 20, 2011 at 6:12 AM, Karl Wright <da...@gmail.com> wrote:
> Hi Pravin,
>
> The .NET piece of the SharePoint connector is necessary only if you
> select the sharepoint 3.0 radio button when you set up your SharePoint
> repository connection.  If you don't want to build and deploy the
> MCPermissions plugin on the server-side SharePoint, you can certainly
> avoid that by simply selecting the sharepoint 2.0 radio button
> instead.  However, if you choose to do it this way, then SharePoint's
> file and folder permissions will not be accessible to the connector.
> (These were added in 3.0 but Microsoft overlooked the web service
> methods that would allow external access to them.)
>
> It sounds like, with this change, you were probably successful in
> connecting to the second system you tried.  For the first system, can
> you tell me a bit more about it?  For example, what version of
> SharePoint was it?  And, did you follow the instructions and use your
> browser to determine the proper connection URL?
>
> I'm actually very interested to talk with someone who has access to a
> functioning SharePoint setup, since I lost access to my SharePoint
> testbed a while ago and would dearly love to bring that connector up
> to snuff for SharePoint 2010.  I'm hoping Microsoft actually corrected
> the missing feature that required the MCPermissions plugin, for
> instance.  Please let me know if you are willing to experiment a bit
> to help us with this connector.
>
> Thanks!
> Karl
>
>
> On Wed, Jul 20, 2011 at 5:20 AM, Pravin Agrawal
> <Pr...@persistent.co.in> wrote:
>> Hi All,
>>
>>
>>
>> I was trying out the sharepoint repository connector provided by manifold
>> CF, following are the steps that I carried out to get it up and running.
>>
>>
>>
>> For building and deploying the CF, I followed the procedure given at
>> http://incubator.apache.org/connectors/how-to-build-and-deploy.html
>>
>> I have build the connector on my linux machine and deployed the application
>> using quick start process.
>>
>>
>>
>> The question that came to me during the build process was – is .NET and MS
>> Visual studio absolutely necessary for building the sharepoint connector or
>> is it sufficient to provide only those 5 wsdl file mentioned in the guide
>> and does it works on windows only as I am able to see manifoldCF UI on to my
>> browser by simply deploying the quickstart version along with sharepoint
>> repository connection.
>>
>>
>>
>> I started to make the sharepoint repository connection to crawl one of the
>> sharepoint site and following are the problems I encountered while creating
>> it
>>
>> 1.       After creating the sharepoint repository connection, the status
>> shows me a message as follows
>>
>> Connection status: The site at
>> http://portal.mydomain.co.in/sites/Documents/Forms did not exist
>>
>> 2.       With a different sharepoint site, connection status shows me
>> following message
>>
>> Connection status: ManifoldCF's MCPermissions web service may not be
>> installed on the target SharePoint server. MCPermissions service is needed
>> for SharePoint repositories version 3.0 or higher, to allow access to
>> security information for files and folders. Consult your system
>> administrator.
>>
>>
>>
>> Can any when tell me whether I am missing some steps
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> -Regards,
>>
>> Pravin
>>
>>
>>
>> DISCLAIMER ========== This e-mail may contain privileged and confidential
>> information which is the property of Persistent Systems Ltd. It is intended
>> only for the use of the individual or entity to which it is addressed. If
>> you are not the intended recipient, you are not authorized to read, retain,
>> copy, print, distribute or use this message. If you have received this
>> communication in error, please notify the sender and delete all copies of
>> this message. Persistent Systems Ltd. does not accept any liability for
>> virus infected mails.
>