EngageOne 4.3 and 4.3.1: Defect - SOAP deliverDocument fails when active-drive path contains a space character

Product Feature: Web Service (API)


In EngageOne 4.3 and 4.3.1, when using SOAPUI to submit a deliverDocument web service request, we always get a "failed delivery message" error on the SOAP response returned.


This is a known bug in EngageOne version 4.3 / 4.3.1 where deliverDocument web service request requires active-drive path to NOT contain any white space character.
In earlier version of EngageOne (3.x), active-drive path path does contain white space character in default install e.g. C:\Program Files\PBBI CCM\EngageOne\active-drive, and same issue is not present in this version.


UPDATED: February 12, 2019
Workaround is to use active-drive path with no space characters in EngageOne version 4.3 and 4.3.1.

Development work to fix this defect is ongoing. Please contact Pitney Bowes Software Support team ( and quote defect ticket CES-35511 should you wish to know the exact versions of EngageOne containing the fix for this defect.