VERIFIED SOLUTION i

EngageOne: Template import in EngageOne Admin fails with ‘com.g1.ocm.api.DeliveryException’


 

Issue

Template import in the EngageOne fails with "com.g1.ocm.api.DeliveryException" error message.Refer following screenshot.

Delivery Exception

At the time of import 'java.io.FileNotFoundException' is also observed in the Application Server (over which EngageOne application is deployed) log.
 

Cause

This could be caused due to one or more file(s) missing (moved or deleted) from active drive.
 

Resolution

UPDATED: March 29, 2017
Restoring file(s) in the respective sub-directories of active drive should resolve the issue. Complete name and path of missing file is registered with 
'java.io.FileNotFoundException'. Refer following Application Server log entry.

Caused by: java.io.FileNotFoundException: \\<Host>\<Active-Drive>\2016-11-10\132.hip (The system cannot find the path specified)