manifoldcf-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Karl Wright <>
Subject Re: Manifold fails with alfresco | pipeline exception
Date Sat, 24 Nov 2018 12:50:58 GMT
Hi Nikhilesh,

Where are you seeing these errors?  They sound like ElasticSearch errors to
me; it is complaining that an null or empty-string pipeline name is being
specified somehow.  Can you tell me what version of ElasticSearch you are

We have outstanding tickets for updating the ElasticSearch connector,
because the public API for ElasticSearch changes very rapidly and therefore
it may be out of date.  Please check the JIRA queue to find the status of
issues like this.


On Sat, Nov 24, 2018 at 7:45 AM Sivakoti, Nikhilesh <> wrote:

> Hi Team,
> We have been trying to use ManifoldCF with our Alfresco. We have
> customized the manifold alfresco connector and manifold elastic search
> connector as per our needs.
> We have added the authentication mechanism in elastic search connector to
> connect to the QA servers. But when we try to execute a job we are getting
> the below errors.
> HTTP code = 400, Response =
> {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"pipeline
> with id [null] does not
> exist"}],"type":"illegal_argument_exception","reason":"pipeline with id
> [null] does not exist"},"status":400}
> Could you please provide any support on thiss?
> Thanks,
> Nikhilesh
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.

View raw message