You have been issued a replacement Enrollment bundle, and it appeared to have enrolled successfully.
However, after a service restart, the following event appears on the Enforce Server:
Release : 15.x-16.x
The Detector was not unbound from the old Enforce Server.
Even if Enforce has been decommissioned or experienced a hard failure, the Cloud Detector remains bound and prevents new Enforce Server from connecting to the service.
Normally, Support follows steps to "unbind" a Detector before re-issuing an Enrollment bundle:
However, in some cases (e.g., hard fail or crash of old Enforce) it's actually not possible to perform step #1.
And as a result, sometimes step #2 gets skipped, and no unbind is performed, and a new bundle gets issued and used to re-enroll the Detector (step #3).
In such instances, Enforce will usually produce the error in this KB.
In this case, if all circumstances match:
Support teams can perform the Unbind operation AFTERWARD.
The usual result will be that the Detector will be unbound from the old Enforce, and await a call from the new one.
Note: The unbind operation needs to be performed on EACH Detector that was previously bound or enrolled to the old Enforce.
If the MonitorController is restarted afterward, the connection and bind result should occur right away.
But even if it isn't, the MC will usually have a reason to "reach out" - daily disconnect and reconnect, EDM indexing updates, etc., and the Detector will then bind to the new Enforce.