That message is due to a flaw in the EnvInject plugin. Steps to resolve it are available in this community post.