This technical note outlines an issue found with the nightly Strategy license compliance check where it invalidates subscriptions and removes contacts in the metadata but leaves the contact's addresses.
In some scenarios, end users will notice undesirable behavior when duplicating a project on one day and then duplicating another project the following day. This can include errors with further project duplications related to violation of primary key constraints, missing subscriptions and contacts for users and user errors in the project duplication log file.
At midnight, Strategy Intelligence Server runs a compliance check to make sure the enabled users are not consuming more licenses than allowed.
During this process, users may notice that certain contact objects disappear from the metadata after a duplication and the nightly compliance check.
In order for the issue to reproduce, a project must be carried over with project-related users, and two user objects must exist across the source and destination environments for the duplication with different object IDs but the same Trusted Authentication ID or login. Both trusted authentication ID and user login must be unique in an environment as that is the only user facing unique identification for users.
STEPS TO REPRODUCE
This is a known issue in Strategy Intelligence Server 9.x. Subscriptions are invalidated and contacts are removed, however the addresses tied to those contacts remain in the metadata. This can cause issues in subsequent project duplications.
Contact Strategy Technical Support for updates on this issue.
The Strategy internal reference number for the issue described in this technical note is 982125.