Skip to content

Legacy Sync Service

Legacy database is not synchronized

Problem

The security legacy database is not synchronized when changes are done in Security API

Solution

There are different potential issues that could cause this problem:

  • Security API is not publishing messages to the service bus. Please review configuration, and state of message bus (up and running)
  • Legacy Sync Windows Service fails during start-up. Check log file generated in the same folder where the service is deployed.
  • Legacy Sync Windows Service logs: during start-up the log is done in file and as soon as connectivity to Core.Logging is ready the logging is moving there. Please, ensure logging connection string and settings are right
  • Legacy Sync Windows Service is not consuming messages from the service bus. Ensure the connection to the bus is right and pointed to the same message bus and virtual host than the associated Security API.
  • Legacy Sync Windows Service doesn't have access to the legacy database; ensure the connection string to the legacy security host application (Claims or Origin databases) are properly configured.