Hi Babita,

Can you describe the actual symptoms?  Perhaps you are using example, and
need to be using example-proprietary?

Karl



On Wed, May 21, 2014 at 7:07 AM, Babita Bansal <[email protected]>wrote:

> but it was working till yesterday, no changes have been made by me. any
> clue?
>
>
> On Wed, May 21, 2014 at 11:47 AM, Wright, Karl <[email protected]>wrote:
>
>>  That exception merely means that it can't find a specific language pack
>> for your locale.  It is harmless.
>>
>> Karl
>>
>> Sent from my Windows Phone
>>  ------------------------------
>> From: Babita Bansal
>> Sent: 5/21/2014 6:42 AM
>> To: Karl Wright
>> Cc: [email protected]
>> Subject: Re: Manifoldcf sharepoint connecyor
>>
>>  hi Karl
>>
>>  It seems windows share connector broke now. While configuring job for
>> windows share and click on path tab i get following error:
>>
>>  ERROR 2014-05-21 11:39:18,056 (http-bio-8080-exec-6) - Missing resource
>> bundle 'org.apache.manifoldcf.crawler.connectors.sharedrive.common' for
>> locale 'en': Can't find bundle for base name
>> org.apache.manifoldcf.crawler.connectors.sharedrive.common, locale en;
>> trying en_US
>> java.util.MissingResourceException: Can't find bundle for base name
>> org.apache.manifoldcf.crawler.connectors.sharedrive.common, locale en
>> at java.util.ResourceBundle.throwMissingResourceException(Unknown Source)
>> at java.util.ResourceBundle.getBundleImpl(Unknown Source)
>> at java.util.ResourceBundle.getBundle(Unknown Source)
>> at
>> org.apache.manifoldcf.core.i18n.Messages.getResourceBundle(Messages.java:142)
>> at org.apache.manifoldcf.core.i18n.Messages.getMessage(Messages.java:178)
>> at org.apache.manifoldcf.core.i18n.Messages.getString(Messages.java:216)
>> at
>> org.apache.manifoldcf.crawler.connectors.sharedrive.Messages.getString(Messages.java:91)
>> at
>> org.apache.manifoldcf.crawler.connectors.sharedrive.Messages.getString(Messages.java:39)
>> at
>> org.apache.manifoldcf.crawler.connectors.sharedrive.SharedDriveConnector.outputSpecificationHeader(SharedDriveConnector.java:2824)
>> at org.apache.jsp.editjob_jsp._jspService(editjob_jsp.java:650)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:748)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:486)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:411)
>> at
>> org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:338)
>> at
>> org.apache.jasper.runtime.PageContextImpl.doForward(PageContextImpl.java:750)
>> at
>> org.apache.jasper.runtime.PageContextImpl.forward(PageContextImpl.java:720)
>> at org.apache.jsp.execute_jsp._jspService(execute_jsp.java:1607)
>> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432)
>> at
>> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390)
>> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
>> at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
>> at
>> org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
>> at
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
>> at
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.lang.Thread.run(Unknown Source)
>>
>>
>>
>>  It was working previously,
>>
>>  thanks
>> Babita Bansal
>>
>>
>> On Tue, May 20, 2014 at 4:39 PM, Karl Wright <[email protected]> wrote:
>>
>>>   Hi Babita,
>>>
>>>  Here is the pertinent stack trace:
>>>
>>> >>>>>>
>>> SEVERE: Servlet.service() for servlet jsp threw exception
>>> org.apache.commons.discovery.DiscoveryException: Class
>>> org.apache.commons.logging.impl.SLF4JLogFactory does not implement
>>> org.apache.commons.logging.LogFactory
>>>     at
>>> org.apache.commons.discovery.tools.ClassUtils.verifyAncestory(ClassUtils.java:178)
>>>     at
>>> org.apache.commons.discovery.tools.SPInterface.verifyAncestory(SPInterface.java:258)
>>>     at
>>> org.apache.commons.discovery.tools.SPInterface.newInstance(SPInterface.java:246)
>>>     at
>>> org.apache.commons.discovery.tools.DiscoverClass.newInstance(DiscoverClass.java:520)
>>>     at
>>> org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:370)
>>>     at
>>> org.apache.commons.discovery.tools.DiscoverSingleton.find(DiscoverSingleton.java:328)
>>>     at
>>> org.apache.axis.components.logger.LogFactory$1.run(LogFactory.java:45)
>>>     at java.security.AccessController.doPrivileged(Native Method)
>>>     at
>>> org.apache.axis.components.logger.LogFactory.getLogFactory(LogFactory.java:41)
>>>     at
>>> org.apache.axis.components.logger.LogFactory.<clinit>(LogFactory.java:33)
>>>     at
>>> org.apache.axis.handlers.BasicHandler.<clinit>(BasicHandler.java:43)
>>>     at org.apache.axis.client.Service.getAxisClient(Service.java:104)
>>>     at org.apache.axis.client.Service.<init>(Service.java:144)
>>>     at
>>> com.microsoft.schemas.sharepoint.soap.ListsLocator.<init>(ListsLocator.java:17)
>>>     at
>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper$ListsWS.<init>(SPSProxyHelper.java:2838)
>>>     at
>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SPSProxyHelper.checkConnection(SPSProxyHelper.java:1483)
>>>     at
>>> org.apache.manifoldcf.crawler.connectors.sharepoint.SharePointRepository.check(SharePointRepository.java:399)
>>>     at
>>> org.apache.jsp.viewconnection_jsp._jspService(viewconnection_jsp.java:296)
>>> <<<<<<
>>>
>>>  It basically looks like something is broken with how logging is being
>>> resolved in this environment.  I'll have to look into what is happening; it
>>> may be that something recently added to the war is conflicting with Tomcat.
>>>
>>>  Karl
>>>
>>>
>>>
>>> On Tue, May 20, 2014 at 10:36 AM, Babita Bansal <[email protected]
>>> > wrote:
>>>
>>>> Hi Karl
>>>>
>>>>  I did the way which you have mentioned, getting same issue, after
>>>> click on save page doesn't displayed anything just a blank screen.
>>>>
>>>>  attached log files of tomcat and properties.xml file.
>>>>
>>>>  Thanks
>>>>  Babita Bansal
>>>>
>>>>
>>>> On Tue, May 20, 2014 at 1:38 PM, Karl Wright <[email protected]>wrote:
>>>>
>>>>>   HI Babita,
>>>>>
>>>>> I would recommend keeping it as simple as possible.  I therefore
>>>>> recommend using the single-process combined war model.  The name of the 
>>>>> war
>>>>> is mcf-combined-service.war, and here are the steps you will need to 
>>>>> deploy
>>>>> a system using it:
>>>>>
>>>>>  (0) First, remove all the mcf web applications you've currently
>>>>> deployed in your tomcat instance, or start with a fresh tomcat instance
>>>>>  (1) cd dist/example
>>>>>  (2) Modify properties.xml to point to your postgresql instance.  Do
>>>>> not make any other changes.
>>>>> (3) Modify the Tomcat startup script, or use the Tomcat service
>>>>> administration client, to set a Java "-Dorg.apache.manifoldcf.configfile"
>>>>> switch to point to the example's properties.xml file.  Use an absolute 
>>>>> file
>>>>> path.
>>>>>  (4) Start tomcat.
>>>>> (5) Deploy and start the mcf-combined-service web application,
>>>>> preferably using the Tomcat administration client.  The war is in
>>>>> dist/web/war.
>>>>>
>>>>>  That should be all you need to do.
>>>>>
>>>>> Karl
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 20, 2014 at 8:29 AM, Babita Bansal <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Hi Karl
>>>>>>
>>>>>>  Thanks for the update. What i am looking to achieve
>>>>>>
>>>>>>  1 manifoldCF setup on tomcat 7
>>>>>> 2. manifoldCF setup for postgres database
>>>>>> 3. manifold setup for solr
>>>>>> 4. Alfresco connector
>>>>>> 5. windows share
>>>>>> 6. share point connector
>>>>>>
>>>>>>
>>>>>>  Could you please let me know the best package to deploy and use
>>>>>> here? would appreciate if you could share some links.
>>>>>>
>>>>>>
>>>>>>  If i talked about is working mean, if i start manifold using
>>>>>> start.jar...what jar has be be deployed on tomcat and could you please 
>>>>>> help
>>>>>> me in setting up logger for manifold.
>>>>>>
>>>>>>  Thanks
>>>>>>  Babita Bansal
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, May 20, 2014 at 12:45 PM, Karl Wright <[email protected]>wrote:
>>>>>>
>>>>>>>  Hi Babita,
>>>>>>>
>>>>>>>  A correction:  You do NOT need to make sure tomcat and agents
>>>>>>> process share the same working directory.  Just make sure they share the
>>>>>>> same properties.xml file.
>>>>>>>
>>>>>>>  Karl
>>>>>>>
>>>>>>>
>>>>>>> On Tue, May 20, 2014 at 7:29 AM, Karl Wright <[email protected]>wrote:
>>>>>>>
>>>>>>>>     Hi Babita,
>>>>>>>>
>>>>>>>>  If what you are doing is simply setting up ManifoldCF for the
>>>>>>>> first time, what I'd do is this:
>>>>>>>>
>>>>>>>>  (1) Pick a deployment model.  All models work with Postgresql, so
>>>>>>>> that is not a reason to pick one over the other.  Simpler is usually 
>>>>>>>> better
>>>>>>>> (easier to manage etc), so if you can get away with the single-process
>>>>>>>> model, that would be the easiest.
>>>>>>>>
>>>>>>>>  This is the roughly the order of complexity, less complexity to
>>>>>>>> more complexity:
>>>>>>>>  (a) Single process
>>>>>>>>  (b) Combined war
>>>>>>>>  (c) Multiprocess setup with zookeeper synchronization (agents
>>>>>>>> process, mcf-authority-service war, mcf-crawler-ui war, 
>>>>>>>> mcf-api-service war)
>>>>>>>>  (d) Multiprocess setup with filesystem synchronization
>>>>>>>>
>>>>>>>>    (2) Configure MCF based strongly on the examples.  There is an
>>>>>>>> example for EVERY model above.  If you are using Tomcat rather than 
>>>>>>>> jetty,
>>>>>>>> you still do the same things.  But there are some differences:
>>>>>>>>
>>>>>>>> - make sure the -D switch is set to point to the appropriate
>>>>>>>> properties.xml
>>>>>>>>  - make sure your tomcat and your agents process share the same
>>>>>>>> working directory, or resolving relative paths in properties.xml will 
>>>>>>>> not
>>>>>>>> work properly
>>>>>>>>  - deploy the jars using the tomcat administrative web
>>>>>>>> application; don't mess with tomcat configuration information
>>>>>>>>
>>>>>>>>  Karl
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, May 20, 2014 at 6:37 AM, Babita Bansal <
>>>>>>>> [email protected]> wrote:
>>>>>>>>
>>>>>>>>> Hi Karl
>>>>>>>>>
>>>>>>>>>  Please see my response below:
>>>>>>>>>
>>>>>>>>>   (1) What version of MCF are you trying to debug?  Which MCF
>>>>>>>>> version did that screen shot come from? I refreshed my browser and 
>>>>>>>>> clear
>>>>>>>>> the cache now seeing new UI.
>>>>>>>>>
>>>>>>>>>  I am using manifold CF version 1.5.1 as mentioned downloaded
>>>>>>>>> code from 
>>>>>>>>> apache-manifoldcf-1.5.1-src.zip<http://archive.apache.org/dist/manifoldcf/apache-manifoldcf-1.5.1-src.zip>
>>>>>>>>>  from
>>>>>>>>> http://manifoldcf.apache.org/en_US/download.html#Apache+ManifoldCF+1.5.1%2C+2014+Feb+20
>>>>>>>>>
>>>>>>>>>  (2) How is MCF deployed on tomcat?  Is it the combined war you
>>>>>>>>> deployed, or individual service wars?
>>>>>>>>>
>>>>>>>>>  I have configured xml configuration of all war files in tomcat
>>>>>>>>> conf location ../tomcat/conf/Catalina/localhost/, sample like
>>>>>>>>>
>>>>>>>>> <?xml version="1.0" encoding="utf-8"?>
>>>>>>>>>
>>>>>>>>> <Context
>>>>>>>>> docBase="C:\IW\MCF\manifoldcf\dist\web\war\mcf-api-service.war" 
>>>>>>>>> debug="0"
>>>>>>>>> crossContext="true"> </Context>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  Did it for all 4 war simmilar way changing name of war and
>>>>>>>>> filename as per war. Which is successfully deploying and extracting on
>>>>>>>>> tomcat webapps folder.
>>>>>>>>>
>>>>>>>>>  (3) What kind of synchronization have you configured in
>>>>>>>>> properties.xml?
>>>>>>>>>
>>>>>>>>>  In properties file i have done following configuration to
>>>>>>>>> connect to postgres DB attached in mail.  And startup of tomcat use
>>>>>>>>> -Dorg.apache.manifoldcf.configfile=C:\IW\MCF\manifoldcf\dist\multiprocess-example\properties.xml
>>>>>>>>> to read the configuration of property file.
>>>>>>>>>
>>>>>>>>>  My tomcat version in 7 and postgres version is 9.1 and running
>>>>>>>>> on windows 2008.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  Please let me know if i missed anything.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>  Thanks
>>>>>>>>>  Babita Bansal
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Tue, May 20, 2014 at 11:16 AM, Karl Wright 
>>>>>>>>> <[email protected]>wrote:
>>>>>>>>>
>>>>>>>>>>    Hi Babita,
>>>>>>>>>>
>>>>>>>>>>  We have proven only that the SharePoint connector for 1.5.1
>>>>>>>>>> works properly against the SharePoint you are trying to crawl, so 
>>>>>>>>>> there is
>>>>>>>>>> no SharePoint connector bug.  What I had intended to do from this 
>>>>>>>>>> point was
>>>>>>>>>> to change one thing at a time between the 1.5.1 single-process 
>>>>>>>>>> example
>>>>>>>>>> running on Derby and whatever MCF version and configuration you are 
>>>>>>>>>> trying
>>>>>>>>>> to debug.  But since I don't know what version that is, and don't 
>>>>>>>>>> know how
>>>>>>>>>> it is configured, I cannot make this plan work without further 
>>>>>>>>>> information.
>>>>>>>>>>
>>>>>>>>>>  Before we go further, can you tell me:
>>>>>>>>>>
>>>>>>>>>>  (1) What version of MCF are you trying to debug?  Which MCF
>>>>>>>>>> version did that screen shot come from?
>>>>>>>>>>  (2) How is MCF deployed on tomcat?  Is it the combined war you
>>>>>>>>>> deployed, or individual service wars?
>>>>>>>>>>  (3) What kind of synchronization have you configured in
>>>>>>>>>> properties.xml?
>>>>>>>>>>
>>>>>>>>>>  Thanks,
>>>>>>>>>> Karl
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Tue, May 20, 2014 at 5:52 AM, Babita Bansal <
>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi Karl
>>>>>>>>>>>
>>>>>>>>>>>  I have downloaded source code zip
>>>>>>>>>>> apache-manifoldcf-1.5.1-src.zip<http://archive.apache.org/dist/manifoldcf/apache-manifoldcf-1.5.1-src.zip>
>>>>>>>>>>>  from
>>>>>>>>>>> http://manifoldcf.apache.org/en_US/download.html#Apache+ManifoldCF+1.5.1%2C+2014+Feb+20
>>>>>>>>>>>  and built using ant build.
>>>>>>>>>>>
>>>>>>>>>>>  What i mean here if i start manifold using start.jar, i could
>>>>>>>>>>> see the latest UI and share point connector is also working, will 
>>>>>>>>>>> share you
>>>>>>>>>>> the screen shot. Can you point me the exact source code which needs 
>>>>>>>>>>> to be
>>>>>>>>>>> use.
>>>>>>>>>>>
>>>>>>>>>>>  Thanks
>>>>>>>>>>> Babita Bansal
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>  thanks
>>>>>>>>>>> Babita Banal
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Tue, May 20, 2014 at 10:17 AM, Karl Wright <
>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>
>>>>>>>>>>>>  Also, your screen shot cannot be from mcf 1.5.1.  The style
>>>>>>>>>>>> sheet is completely different now.  What version of mcf are you 
>>>>>>>>>>>> really
>>>>>>>>>>>> using?
>>>>>>>>>>>>
>>>>>>>>>>>> Karl
>>>>>>>>>>>>
>>>>>>>>>>>> Sent from my Windows Phone
>>>>>>>>>>>>  ------------------------------
>>>>>>>>>>>> From: Karl Wright
>>>>>>>>>>>> Sent: 5/20/2014 5:13 AM
>>>>>>>>>>>> To: Babita Bansal; [email protected]
>>>>>>>>>>>> Subject: RE: Manifoldcf sharepoint connecyor
>>>>>>>>>>>>
>>>>>>>>>>>>   Hi Babita,
>>>>>>>>>>>>
>>>>>>>>>>>> Lets take one step at a time.
>>>>>>>>>>>>
>>>>>>>>>>>> If single process example works, then try modifying single
>>>>>>>>>>>> process properties.xml to point to your postgres database.  The
>>>>>>>>>>>> how-to-build-and-deploy page describes the parameters you need to 
>>>>>>>>>>>> do that.
>>>>>>>>>>>>
>>>>>>>>>>>> Initialize.bat is not needed for single process, so just try
>>>>>>>>>>>> this one change and tell me how it goes.
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks,
>>>>>>>>>>>> Karl
>>>>>>>>>>>>
>>>>>>>>>>>> Sent from my Windows Phone
>>>>>>>>>>>>  ------------------------------
>>>>>>>>>>>> From: Babita Bansal
>>>>>>>>>>>> Sent: 5/20/2014 4:23 AM
>>>>>>>>>>>> To: [email protected]
>>>>>>>>>>>> Subject: Re: Manifoldcf sharepoint connecyor
>>>>>>>>>>>>
>>>>>>>>>>>>  Hi
>>>>>>>>>>>>
>>>>>>>>>>>>  I have tried with default database and application, it
>>>>>>>>>>>> working fine there. I need to use postgres DB. What i did, 
>>>>>>>>>>>> downloaded the
>>>>>>>>>>>> source and built using ant. And in properties.xml file provided the
>>>>>>>>>>>> postgres db settings, and run the command initialize.bat to create 
>>>>>>>>>>>> the
>>>>>>>>>>>> postgres db. I can connect to windows share and alfresco easily. 
>>>>>>>>>>>> But when i
>>>>>>>>>>>> tried to configure share point it just blank page no error on log 
>>>>>>>>>>>> file.
>>>>>>>>>>>> Could you please let me know how to set debugging, as i don't see 
>>>>>>>>>>>> anything
>>>>>>>>>>>> in log file. Attached screen shot for configuration :
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>  Any ref guide or configuration details really appreciated.
>>>>>>>>>>>> Just to inform you guys i have not done any configuration on share 
>>>>>>>>>>>> point
>>>>>>>>>>>> side for share point connector.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>  If possible i can have screen share session with you.
>>>>>>>>>>>>
>>>>>>>>>>>>  Thanks
>>>>>>>>>>>> Babita Bansal
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, May 20, 2014 at 12:33 AM, Karl Wright <
>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>>    Hi Babita,
>>>>>>>>>>>>>
>>>>>>>>>>>>>  To rule out any database or app server misconfiguration, can
>>>>>>>>>>>>> you try running the single-process example, and setting up your 
>>>>>>>>>>>>> SharePoint
>>>>>>>>>>>>> connection there?
>>>>>>>>>>>>>
>>>>>>>>>>>>>  cd example
>>>>>>>>>>>>>  <java> -jar start.jar
>>>>>>>>>>>>>
>>>>>>>>>>>>>  <set up your connection in the UI>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Thanks!
>>>>>>>>>>>>>  Karl
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Mon, May 19, 2014 at 6:58 PM, Babita Bansal <
>>>>>>>>>>>>> [email protected]> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I am trying to connect sharepoint 2010 with manifoldcf
>>>>>>>>>>>>>> . but after clicking on save i just get blank page . when i
>>>>>>>>>>>>>> refresh page o get illegal parameter value. I am using postgres 
>>>>>>>>>>>>>> db with
>>>>>>>>>>>>>> tomcat 7. Version of manifold is 1.5.1 . alfresco n windows share
>>>>>>>>>>>>>> connectors are workimg fine
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Pls help to resolve any issue.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to