Customizing

Invalid Packets MOD009CEV





Access

For 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

  • LampeWeiss.png signalizes that this migration packet has not yet been executed.

  • LampeGruen.png signalizes that the migration packet has run successfully.

  • LampeGelb.png signalizes that this migration packet is still pending and waits for another migration packet to reach a certain status before it can be executed.

  • LampeGrau.png signalizes that this migration packet is not relevant for the current update type due to version dependencies.

  • LampeRot.png signalizes that the migration packet has failed. There may be several causes for a packet to fail:

    • Many migration packages check whether the customizing on which the fix is based has changed before they are executed.

      • If this is the case, the change to the package is not made and the package is deemed to have failed.

        • In such a case, you have to check in the customizing whether and how the respective change can be made.

        • If the change has been made or if the change is not necessary, the package can be manually set to completed by activating the Completed checkbox.

        • This will move it from the Failed/pending packets area to the Completed Packets module.