Migrating Communities claim to be 'successful' but fails in EngageOne Server

Product Affected: EngageOne Server

Product Feature: Upgrade/Migration

Operating System: Windows/Linux



When running the Groovy script to perform the community migration the script appears to run to completion but upon closer inspection of the log file it shows it failed with an error:

[INFO ] Setting up log file for command 'migrate-community'
[INFO ] Log file location: C:\EngageOne_Server\install\logs\migrate-community-XXXX-XX-XX-XXXXXX.log
[INFO ] Migrating communities
[INFO ] Arguments: -p C:\EngageOne_Server\install\ community 
[INFO ] Validating configuration properties
[INFO ] executing ""c:\progra~1\java\jdk1.8.0_144\jre\bin\java.exe" -Dviewpoint.config.externalPropertyFilePath=C:\EngageOne\core\conf\ -Dlogback.configurationFile= -DadminServices.jackrabbit.configuration=file:C:\Users\USER\AppData\Local\Temp\13\4684118124032974616\repository-mssql.xml -DadminServices.jackrabbit.homeDir=C:\Users\USER\AppData\Local\Temp\13\4684118124032974616 -Djcr.url=jdbc:sqlserver://SD-DIRSQL02:1433;databaseName=EngageOneUpgrade;user=USER;password=******** -jar "C:\EngageOne_Server\install\..\upgrade\migration\communities-migrator\communities-migrator-4.4.4.Release.jar""
[INFO ] Community migration> [2019-04-12 13:15:36,942 | ERROR | org.apache.jackrabbit.core.cluster.ClusterNode] Unable to deliver node type operation: {}component already exists locally
[INFO ] Community migration> [2019-04-12 13:15:41,279 | WARN  | com.pb.viewpoint.migration.admin.communities.CommunitiesMigrator] Checking if community 'EngageOne' is correctly imported
[INFO ] Community migration>     ... 6 common frames omitted
[INFO ] Communities have been successfully migrated
[INFO ] Details of 'community' target's results in log file C:\EngageOne_Server\install\logs\migrate-community-XXXX-XX-XX-XXXXXX.log
[INFO ] ------------------------------
[INFO ] migrate 'community' - SUCCESS
[INFO ] ------------------------------


A defect in the migration script causes the error but it is not caught by the script to show at the end that the error has happened and action needs to be taken to correct the error.


UPDATED: June 19, 2019
This issue will be resolved in EnageOne Server SP10 due for release end of 2019.
Please contact Technical Support by sending an email to to request a copy of this release.