VERIFIED SOLUTION i

Installation fails when the system user name contains colons in EngageOne Server 4.4

Product Affected: EngageOne Server

Product Feature: Installation / Upgrade

Operating System: Windows/Linux/AIX


 

Issue

When running the installation Groovy script for EngageOne® Server 4.4 (eos.groovy), the validation stage will return an error stating that the system.user.username value set in the Deploy.Properties file is not valid.

Cause

The use of a colon in the username such as 'test:test' is not accepted by the EngageOne Server installation and will not work. 

 

Resolution

UPDATED: June 6, 2019
This is currently a limitation of EngageOne Server 4.4 SP1 to SP9 and the only way to proceed with these versions is to change the username 'system.user.username' so that it does not contain a colon. It is possible to still have normal users with a colon in the name but  the user set up as the system user must not. This is due to the way internal calls are made (using HTTP) and the colon is a reserved character. The defect has been documented as a known limitation in EngageOne Server 4.4 SP9. An enhancement is in place for a fix to be included in a future release. Please contact Software support by email (software.support@pb.com) for the latest version of EngageOne Server.