Invalid Packets MOD009CEV

Access

Information

This module contains all invalid migration packets.
Invalid migration packets are packets that are saved in the database but can no longer be found under the saved path. The path must either be corrected or the packets must be deleted.

Legend

indicates that the migration packet has not been run yet.
indicates that a migration packet has run successfully.
indicates that this migration packet is still open and waits for another migrationpacket to reach a particular status before it can be run.
indicates that this migration packet is not relevant for the current update type due to version dependencies.
indicates that the migration packet has failed. The failure of a migration packet may have several reasons:
- Before they are run, many migration packets check whether the customizing on which the fix is based, has changed.
  - If this is the case, the packet will not be run and is considered failed.
    - In this case, the customizing has to be checked in order to find out whether the modification in question can be carried out.
    - If the modification was carried out or the modification is not necessary, the packet may be set to completed manually by activating the Completed checkbox.
    - As a result, it is moved from the Failed/open packets area to the Completed Packets module.

Many help packets check the customizing for problems.
- If they fail, this means that there is work to do for the customizer.
- As a result, the positions listed in the logfile have to be checked and modified.
- If the cause for the failure has been fixed, the migration packet can be run again by clicking on the Run packet button in the Overview of all Previous Runs module.