For future reference, it may also be caused if your package is set as 'server'. Unmark this setting on SE80, in the properties of your package and try again.
We faced this issue after a package migration.
Best,
For future reference, it may also be caused if your package is set as 'server'. Unmark this setting on SE80, in the properties of your package and try again.
We faced this issue after a package migration.
Best,