This content has been marked as final. Show 1 reply
We are happy to hear that this issue has been resolved by the customer after restarting Tracking Server. Without more details, we can't know exactly what the problem was, but some configuration changes are known to take effect only after a restart of Tracking Server (changing port numbers, changing policy server configuration, etc.). If the customer was changing the configuration, that could explain why things began working only after a restart.