• Frozen Job when Transporting to a new HistoryDB (9.2)

    We have installed a new History Database in our environment and let the first Transport start with the AutoSchedule.
    Before this HistoryDB, we had a HistoryDB that was installed but never used on v8.2.

    When the Job autostarts, it throws the following…