Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

CMIS connector fails to save documents with Bad Request error

SA-71972

Summary



During 'Fax to Case' creation, the Intake case is created. However, an exception occurs when the Content Management Interoperability Services (CMIS) connector is invoked and multiple documents are saved in SharePoint in succession.
The application must save documents in SharePoint instead of in the PegaRULES database. During 'Fax to Case' creation by the listener, the system saves all incoming emails (.eml files) in SharePoint and during processing, the system displays a Bad Request error.


Error Messages



[<IP>:<PORT>-88] [TABTHREAD1] [ ] [pperEndUser:03.01.50] (connect.cmis.CMISConnector) ERROR servername.com|<IP>|Rule-Connect-CMIS.CMIS-ServiceData.Sharepoint_abc usrname - [Rule-Connect-CMIS: Sharepoint_abc] CMIS error code: CMIS_INVALID_ARGUMENT_EXCEPTION. Bad Request
org.apache.chemistry.opencmis.commons.exceptions.CmisInvalidArgumentException: Bad Request 
at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.convertStatusCode(AbstractAtomPubService.java:466) 
at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.read(AbstractAtomPubService.java:634)
  
...
[<IP>:<PORT>-10] [TABTHREAD3] [ ] [pperEndUser:03.04.01] (connect.cmis.CMISConnector) DEBUG servername.com|<IP>|Rule-Connect-CMIS.CMIS-ServiceData.Sharepoint_repo_name - Unauthorized
org.apache.chemistry.opencmis.commons.exceptions.CmisUnauthorizedException: Unauthorized
at org.apache.chemistry.opencmis.client.bindings.spi.atompub.AbstractAtomPubService.convertStatusCode(AbstractAtomPubService.java:468)



Steps to Reproduce

  1. Compose an email and add an attachment to that email. 
  2. Send the email to the correct Fax system which the Listener uses to consume Fax for Intake Case creation.


Root Cause



A defect or configuration issue in the operating environment.


Resolution



Perform the following local-change:
  1. Use Basic authentication instead of NT LAN Manager (NTLM).
  2. Make the end point secure using single sign-on (SSL).
  3. Use the domain name in the Realm field.
  4. Check the Preemptive checkbox in the Authentication profile. 

 

Suggest Edit

Published February 20, 2019 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us